echo3.co@localhost:~/about/$

About

Why does this site look like 1986?

My first computer was a 16k ZX Spectrum, so the tech bug bit in the early 80s. Since then I've owned a run of now-iconic machines. I look back on those machines fondly, but this isn't a shrine to the past; I get the same buzz building solutions on today's incredible tech stacks as I did from a tape loading screen back then. The retro look here is shorthand: I like systems that are legible, that tell you exactly what they're doing.

I also didn't want to build another formulaic MSP (Managed Service Provider) website. You know the kind: generic corporate visuals, stock photos of people staring intently at screens, meaningless slogans like "we're committed to empowering your digital journey". Whether you love or hate the theme of my site, you'll remember it. I don't pretend to be bigger than I am, and I refuse to hide behind a marketing layer. That's how I try to run client relationships too.

Who I work with

  • [entrepreneurs]
  • [small teams]
  • [single point of contact]

Entrepreneurs and small teams who want a single, reliable point of contact for IT rather than a rotating cast of specialists. If that's you, the services page is the fastest way to see if we're a fit.

Turning complexity into simplicity

One of my greatest joys is turning complex, inefficient workflows into something beautifully simple. Like replacing an entire manual reporting process with a Google Sheet, some Apps Script and an HTML dashboard. Not because it's clever, but because it gives someone their afternoons back. More on how that works on the Bespoke Builds page.

$ cat career.log
SINCE      1999
FREELANCE  2011
ROLE       TECHNOLOGIST
UPTIME      hours
CAPACITY   ████████ 75% — room for morePixel art portrait of Jude Sudbury

The problem-solving technologist

I've never wanted to specialise. Part of me needs the next new problem, so I've stayed wide: a bespoke system one month, a client's cloud security tightened the next, an old website rebuilt so the client can run it themselves after that. What stays constant across all of it is speed: grasping the concept underneath a new problem quickly, then finding the shortest route to actually fixing it. There's no typical day.

I'd have automated myself out of a job by now if there were.

LOAD "FLOPPY DASH"_
SCORE: 0 :: DISTANCE: 0Kb BEST: 0
FLOPPIES: 0 :: SQUASHED: 0

floppy dash

High Scores