You wanted to track bugs. You got a bureaucracy engine with custom fields nobody remembers creating and workflows nobody dares to simplify. The Jira invoice, itemised.

In 1964, Douglas McIlroy wrote a memo about coupling programmes like garden hose. Nine years later, Ken Thompson implemented it overnight. One character changed computing.

Every Electron app ships its own copy of Chromium. Slack, Discord, Teams, VS Code. Four apps, four browsers, none displaying a web page. The Electron tax, itemised.

You wanted to provision a server. You got a proprietary language, a state file full of secrets in plain text, and a licence that changed overnight. The Terraform invoice, itemised.

For nearly two decades, WordPress has been known for a simple, powerful idea: that anyone should be able to get online and start creating with minimal friction. The famous five-minute install captu…

And it made me wonder what the future of UI holds

John O'Nolan built a CLI for his own product - and found himself using it in an entirely new way. The underlying trend here is really exciting.

If you were anywhere near a computer in the mid-to-late 1990s, you almost certainly encountered a Zip drive. That distinctive purple peripheral, with its satisfying clunk as you slotted in a cartri…

Digital Convergence Corporation is hardly a household name, and there’s a good reason for that. However, it raised about $185 million in investments around the year 2000 from companies such a…

Over-engineering slows delivery, raises costs, and kills products. Learn why it happens—and how to build simpler, stronger software.

Developer experience is the critical multiplier for engineering output. Learn why DX determines which teams ship faster, retain talent, and outperform.

News and insights on the Android platform, developer tools, and events.

News and insights on the Android platform, developer tools, and events.

OpsOrch stitches together telemetry, incident response, and automation so teams can see, decide, and act with confidence.

We audited 30 AI agent projects. 93% use unscoped API keys with no per-agent identity, no consent, and no revocation.

From database BLOBs to object stores — understanding the architecture patterns and when to use each

People assume the interface of an open source project is the API surface. The README. The documentation. The function signatures and the error messages and...

WebAssembly is breaking out of the browser into servers, edge, and plugins. Explore why WASM is becoming the universal runtime for 2026 and beyond.

lshaz is a Clang/LLVM-based static analysis tool that detects microarchitectural latency hazards. That includes false sharing, atomic contention, cache line geometry problems. All at compile time, before code ships.

https://github.com/friendlymatthew

Consensus is one of the fundamental problems in distributed systems. In this post, we want to see what is consensus and review the most f...

A system freeze led us deep into Linux spinlock internals, where we helped find not one but three bugs in the kernel's resilient locking code used by eBPF.

I've been trying to write a 'why functional programming' piece for over a year. Here's why it keeps falling apart.

Exploring why GNU Emacs embeds a Lisp interpreter in C -- from TECO marcos to Greenspun's Tenth Rule, with architecture comparisons to Neovim and VSCode

Writing about the big beautiful mess that is making things for the world wide web.

When you think of CI, you probably picture a remote server somewhere: GitHub Actions, GitLab CI, Jenkins. You push your code, you wait, and eventually you get a green checkmark or a red X. This is so normal that we don't even question it. But why does CI have to be remote?