Expect content that balances technical insight with measured reflection, seasoned with just the right amount of humour. These ideas and observations refused to stay quietly in mind, now shared to spark meaningful discussions and fresh perspectives.
The complete archive across all years—from hands-on infrastructure and tooling guides to opinionated takes on architecture, quality, and the forces reshaping the craft.
Platform teams start with a sensible promise: remove repeated toil so delivery teams can focus on customers. The trap appears when the platform grows its own roadmap, measures success by adoption, and becomes an internal product nobody is allowed to refuse.
Testing on localhost hides entire categories of bugs—cookie scope issues, CORS policies, authentication flows that behave differently on real domains. These problems surface after deployment, when fixing them costs hours instead of minutes. Dnsmasq eliminates this gap by making local development behave like production, turning any custom domain into localhost whilst preserving domain-based security policies.
Managing dozens of SSH connections means remembering complex hostnames, multiple keys, and elaborate commands you copy from text files. The .ssh/config file transforms this chaos into memorable aliases that map mental shortcuts to complete configurations, reducing cognitive load so you can focus on actual work rather than SSH incantations.
Working on someone else's machine feels like writing with their hands—common commands fail, shortcuts vanish, and everything feels wrong. Dotfiles transform this by capturing your accumulated workflow optimisation in version-controlled configuration files, turning any terminal into your terminal within minutes rather than days of manual reconfiguration.
Understanding the real-world implications of uptime percentages is paramount for businesses and consumers alike. What might seem like minor decimal differences in uptime guarantees can translate to significant variations in service availability, impacting operations, customer experience, and bottom lines.
Every rewrite pitch promises immaculate diagrams, fresh architecture, and no awkward compromises. Greenfield projects feel clean only because they have not met production yet, and the delusion starts when organisations mistake that early clarity for value and treat brownfield work as failure instead of stewardship.
curl offers around 257 command-line options, yet it is easy to use only a small handful of them in regular rotation. This article treats the familiar URL fetcher as a practical HTTP toolkit for debugging, scripting, and smoke tests.
Teams spend hours debating whether a story is a five or an eight, then watch the number become a roadmap date and a blame shield. Estimation theatre persists because organisations pretend uncertainty disappeared the moment a meeting produced a number.
Leap seconds are tiny corrections with large software consequences. This article explains why UTC occasionally gained an impossible second, how Linux, DNS, airline bookings, and distributed systems stumbled over it, and why standards bodies chose a different future.
Resume-driven architecture happens when teams choose technology for marketability rather than fit. It is not individual vanity so much as an incentive problem built by hiring, promotion, hype, and weak technical governance.
The average developer types the same handful of commands hundreds of times a day, with the same flags, in the same order. The shell has two small features for shortening that vocabulary without losing any of its expressiveness, and they take an afternoon to learn properly.
Documentation graveyards are not created by engineers who hate writing. They are created by organisations that treat knowledge as a one-off clean-up task instead of maintained product infrastructure.
Most developers meet jq as a pretty-printer and go no further. Underneath that single command is a filter language rich enough to reach into nested JSON, reshape an API response, and build request bodies, all composable with Unix pipes and all comfortable inside a one-liner.
A colleague asks for an urgent review whilst a refactor is halfway across the working tree. The usual ways to juggle parallel branches are all bad: a panicky git stash, a second clone that drifts out of sync, or a polite request to wait.