About Mark Ross | IT, Business & Creative Experience
// ABOUT MARK ROSS

Systems thinking, native web architecture, and creative leadership.

"Whether I'm building software from scratch, repairing something that isn't working, framing a photograph, choreographing a dance, or trying to reproduce a favourite food, the impulse is always the same: figure out how it works underneath, question why it was made that way, and try to build a better version."

What I Do

Build websites and software, solve awkward problems, teach people how things work, and lead creative projects.

Location Portsmouth, Hampshire, UK
Primary Focus Native web platforms, operational systems, technical translation, and creative leadership.
Operating Baseline Plain English, evidence over assertion, and zero hidden agendas.
Academic Foundation B.Sc. (Hons) Engineering Business Development (Bournemouth University)

How I Approach Problems

Systems Diagnostics & Pattern Matching

When faced with a system that isn't performing - whether it is a broken piece of custom software, a jammed mechanical assembly, or an inefficient group workflow - my immediate instinct is to look past the surface symptoms. I map the underlying mechanics until the exact breakdown point becomes clear.

When something genuinely interests me, I can become deeply absorbed in it for hours or days, working through complex, unstructured problems until a clean, resilient solution is built.

Technical Translation via Everyday Analogies

High technical capability is of limited value if you cannot explain it clearly to the people who need it. I naturally bridge the gap between complex technical logic and human understanding by translating abstract concepts into intuitive, real-world physical models.

If someone doesn't understand how a database query, an optical lens alignment, or a software framework operates, it usually isn't their fault - it means the person explaining it hasn't found the right analogy yet.

How I Became Mark

// Five stages of mechanical logic, human communication, and creative leadership.
01
c. 1984 — Early Years

Stage 1: Mechanical Logic & Early Curiosity

At ten years old, I was taking apart broken VHS tape decks on the carpet to figure out how they worked. It taught me that apparently complicated things often become much less mysterious once you understand the mechanism underneath.

By my teenage years, this curiosity turned into a habit of questioning default solutions. Instead of accepting "that's just how the product is made," I started designing custom blind-spot mirror attachments and home-brewed safety socket concepts. The reflex was already set: Why was it designed this way, and how could it work better?

02
Sales, Coaching & Hardware Support

Stage 2: Learning to Understand People as Well as Machines

As a child, I was intensely shy. Recognising that this was a limit, I systematically set out to overcome it by taking on face-to-face public canvassing in my late teens.

Treating public communication as a skill to be learnt rather than a fixed personality trait transformed how I interacted with people. I went on to become Top Canvassing Manager for Zenith Windows in the Solent region, managing sales teams and coaching staff on public engagement.

Later, while working in retail with Currys/Knowhow, this experience evolved into technical coaching - training both customers and colleagues on computing and hardware mechanics using clear, unpretentious analogies. Later, while working in retail with Currys/Knowhow, this experience evolved into technical coaching. I trained both customers and colleagues on computing and hardware mechanics using clear, unpretentious analogies, ultimately leading a branch from 13th to 1st in regional performance through targeted 1-to-1 mentoring.

Years of hands-on repairs, from fixing physical hardware to pulling lost data off failing drives, built my approach to tracking down faults. More importantly, it taught me how to calm people down when their tech failed them at the worst possible moment.

03
2011 — Photography & Optics

Stage 3: Visual Systems, Optics & Teaching

In 2011, I bought a Nikon D90 camera. Characteristically, I didn't just want to take pictures; I wanted to understand cameras, lenses, optics, light and what was actually happening when I changed the settings.

I joined a local camera club to test my work in judged competitions. I gravitated toward unusual, abstract macrophotography where the viewer had to work out what they were looking at. In September 2011, I took first place in a club competition with a macro shot of ice cubes inside a glass of Coca-Cola, lit to look like an alien landscape.

Learning photography also led me to Photoshop, which expanded my understanding of digital image manipulation and visual composition, skills that later became useful in web design. It also allowed me to deliver camera and DSLR training modules for others. It was another turn of the same pattern: learn the mechanics, master the execution, use it creatively, and teach it.

04
Cultural Leadership & Repertoire

Stage 4: Building Creative Systems & Communities

When I got involved in Border Morris dancing, I eventually stepped into creative leadership as Squire and Foreman for Mafficking Border Morris.

Leading a performing team required the same systems thinking as software engineering: building group synchronisation, choreographing original dances ("Swanky", "The Flux"), designing distinct visual kit, and keeping a community group motivated and aligned. To support the team, I designed and built their custom web engine and brand presence (maffickingborder.co.uk) from scratch.

05
Present Day

Stage 5: Where That Lands Today

Today, those separate threads converge into a single working style. Whether I am writing zero-framework PHP software engines (titanbuilds.co.uk), diagnosing broken operational systems, or conducting statutory research and policy audits, I approach the work with the same principles established over thirty years: get under the hood, understand the human element, build a clean solution, and explain it clearly.

My campaign and policy work is explored separately on /campaigns, where the emphasis is on the research, behavioural frameworks, and statutory analysis rather than biography.

How I Operate

Understanding over assertion

I would rather understand why someone disagrees with me than win an argument with them.

Evidence over rhetoric

I trust physical, documentary, statistical, and statutory evidence far more than polished claims or corporate slogans.

De-escalation over confrontation

I prefer to design systems and workflows that prevent friction in advance. When high-pressure friction does occur - whether managing front-of-house de-escalation across 120+ cover live events or resolving complex corporate customer disputes - I rely on calm, protocol-driven resolution rather than personal conflict.

Building over complaining

If an existing solution, software tool, or process is flawed, the most constructive response is to build a working alternative that demonstrates a better way.

Honest Boundaries & Limits

Calendar Saturation

I have a persistent tendency to take on too much. Because I am genuinely interested in solving problems and building things, my schedule fills up quickly, and I can sometimes underestimate my temporal capacity. I have to actively manage my calendar to make sure I don't overcommit.

Conflict & Stance

I am not naturally comfortable with personal confrontation. I will go out of my way to de-escalate arguments and find common ground. However, when clear evidence, data, or statutory logic backs a specific stance, I can be stubborn about changing course unless equivalent evidence is presented to the contrary.