Category
11 articles
Somewhere in a British server rack, right now, there is a function called 'fixThisProperlyLater' that was written in 2014 and has processed four million transactions. Nobody remembers who wrote it. Nobody wants to find out. This is the story of the code we're all too mortified to mention — and why pretending it isn't there is making everything worse.
Somewhere in a data centre you'll never visit, a system written before most of your colleagues were born is processing transactions that keep the country running. The developer responsible for it hasn't had a proper holiday in four years. This is their story.
Manchester has the talent. Bristol has the energy. Edinburgh has the ideas. But London has the salaries, the investors, and an apparently magnetic force field that makes it almost impossible for regional tech hubs to hold onto their best people. Something is going wrong outside the M25, and the consequences are going to be felt for a long time.
While your dev team was busy debating framework choices, Janet in accounts quietly built a self-auditing, macro-driven financial model that's been running flawlessly since 2009. It's time engineers stopped laughing at spreadsheets and started taking notes.
Somewhere in Britain, a development team is six months into building a bespoke notification system. There is a SaaS tool that does exactly this for £49 a month. Nobody mentioned it because nobody asked, and asking would have felt like admitting defeat.
Your deployment pipeline has seventeen stages, four approval gates, a security scan that takes forty minutes, and a rollback procedure documented across three Confluence pages nobody has read. Congratulations — you have built a magnificent machine for not shipping software. It's time for a beermat reality check.
Somewhere between the third nested schema definition and the fourteenth footnote about authentication edge cases, your developer gave up and went to make a brew. Britain's tech teams have a peculiar gift for turning elegant APIs into impenetrable literature — and it's quietly costing everyone dearly.
When the nation's developers were sent home in 2020, the working assumption was that Britain's legendarily reserved tech workforce would crumble without the social scaffolding of the office. What actually happened was considerably stranger, more interesting, and in several documented cases, involved a suspicious amount of sourdough. Five years on, the story of remote work and the British developer is more complicated — and more human — than anyone predicted.
Britain is producing more computer science graduates than ever, yet hiring managers across the UK tech sector are tearing their hair out trying to find developers who can actually do the job. Something has gone badly wrong between the classroom and the codebase, and it's costing everyone — students, companies, and frankly the entire British economy — rather a lot.
The daily standup was supposed to keep teams aligned. Instead, it's become the centrepiece of a meeting culture that's quietly strangling productivity in UK software shops. It's time for smaller teams to stop performing agility and start practising it — and that begins with cancelling a lot of calendar invites.
While American tech firms race to hire thousands and burn through venture capital at breathtaking speed, a quietly confident cohort of British software companies is doing something radical: staying small, staying profitable, and — whisper it — actually enjoying themselves. This is an argument for the boutique, the niche, and the deliberately unglamorous business that turns a tidy profit without once appearing on a VC's radar.