I was reading through some Reddit threads the other day — you know the ones, where people ask “what do you wish you’d known at 25?” — and I found myself nodding along to a lot of it. There’s something oddly comforting about reading advice from people who actually lived through the decade you’re currently in. Not theorists, not podcasters, just regular folks who figured some stuff out the hard way. ...
I’ve been on enough contracts now that I’ve started noticing patterns. Some good, some not so good. This is a collection of the things I check before signing, and the things I wish someone had told me about earlier. Before you sign There are three administrative questions that can catch you out if you don’t sort them early. The first two are about checks — whether the client needs a BPSS or DBS check done, and whether they’re going to organise it. The third is about timing. Some start dates are real, others depend on the client actually getting you a laptop and sorting your access. If their setup process is slow, your start date slides whether they realise it or not. ...
Self-promotion gets a bad reputation because people confuse it with boasting. Done well, it’s just making sure the right people know what you’ve done. Use “I” when it’s your work If you led the project, say “I led the project.” Saving “we” for genuinely collaborative work means your individual contributions stand out when they matter. Performance reviews are your moment If your organisation does annual reviews, prepare a list of accomplishments before the meeting. Don’t rely on your manager to remember everything you did over twelve months. ...
Most people treat office politics as something to avoid. They’d rather focus on their work and hope it speaks for itself. But the truth is, everyone is already playing the game — whether they admit it or not. The difference is between people who understand how it works and people who get surprised by it. Here’s what I’ve learned about developing political awareness at work. Know where you’re going You can’t navigate an office if you don’t know what you’re looking for. What do you actually want? A promotion? A transfer to a different team? More influence over decisions? Be honest with yourself about it. ...
You learn more from your mistakes than anything else, and I have made my fair share. The trick is to actually learn from them rather than just suffer through the consequences and call it experience. I have watched developers push code to production on a Friday afternoon because the business was breathing down their necks. The deadline was immovable, the pressure was real, and the production environment was treated as an afterthought. I have seen it happen more times than I care to count, and each time the same thing goes wrong: someone breaks something, and nobody wants to own it. ...
I’ve been thinking about what to ask when someone offers you a job at a startup. The usual questions about salary and benefits matter, but there are deeper ones that tell you whether the place is actually going to survive long enough for you to care about that stock option package. Here are some questions I’d ask. How much cash do you have in the bank? Not how much you’re hoping to raise. Not how much you could borrow if things get tight. Actual cash, right now, in an account. ...
I was reading through some job listings recently and noticed a pattern. The same skills keep appearing, and the ones that were important five years ago are shifting. Not disappearing entirely, but moving around. Here’s what I think developers should be focusing on right now if they want to stay employable over the next few years. This isn’t exhaustive. There are plenty of specialisms and niches I’m ignoring deliberately. I’m thinking about mainstream development work, the kind most people do. ...