2026
127 pieces · 90,833 words · 414 minutes of reading.
September 14
- Q3 2026, in one pagebrief
- The dashboard nobody looks atessay
- Least privilege, actually appliedessay
- Reading an RFCessay
- The migration that never finishedessay
- Choosing an IDessay
- Why your tests are slowessay
- The graph nobody drewessay
- The Cyber Resilience Act's reporting clock starts todaynews
- Timeouts: every one of themessay
- Java 27 and the LTS questionnews
- The debugging notebookessay
- The annual Postgres upgrade you keep deferringnews
- The queues you did not know you hadessay
August 15
- The interface is the productessay
- What a good incident channel looks likeessay
- Rust's six-week metronome, seven years onnews
- The API you ship to yourselfessay
- Shell scripts that outlive youessay
- The cost of a 500essay
- How to run a spikeessay
- Boring technology, revisitedessay
- The service you should not have writtenessay
- Reading a flame graphessay
- What "done" actually meansessay
- Go 1.27 and the six-month metronomenews
- The load-bearing commentessay
- Two hundred pieces inessay
- The AI Act's high-risk obligations take effect todaynews
July 14
- Two years of agentic coding: what stuckessay
- Deleting code is the highest-value work nobody schedulesessay
- The performance budgetessay
- What I look for in a codebase in the first houressay
- The unreasonable effectiveness of a changelogessay
- Property-based testing deserves its momentessay
- Vendor lock-in: an honest cost modelessay
- Connection pooling, explained properlyessay
- The onboarding document that actually worksessay
- Why your container image is 1.4 gigabytesessay
- Secrets management, practicallyessay
- Code review comments that change thingsessay
- Backpressure is the concept your system is missingessay
- The crawler tolls, one year onreview
June 14
- Cross-platform is a promise you make to your budgetessay
- Retries: a complete guide to not making it worseessay
- Half of 2026, in one pagebrief
- Configuration is the most under-designed part of your systemessay
- Randomness, and the bugs you cannot reproduceessay
- What a staff engineer does all dayessay
- Licenses: a practical guide for people who shipessay
- Distributed tracing that people actually useessay
- Refactoring under an agentessay
- The World Cup is the largest load test ever runessay
- WWDC 2026 and the platform that keeps its own counselnews
- Static analysis is finally worth the false positivesessay
- Time zones, and why your calendar code is wrongessay
- Rewrites: when they actually workessay
May 14
- What a great bug report containsessay
- Edge computing, honestlyessay
- Model evaluation for people who shipessay
- Idempotency is the only distributed systems concept you needessay
- Platform teams that don't get resentedessay
- Open source funding: five models, honestly comparedessay
- Compression is underratedessay
- The queue is the architectureessay
- Run the incident before the incidentessay
- Python 3.15 and free-threading's second actnews
- I/O 2026 and the assistant that lives in everythingnews
- Error messages are a user interfaceessay
- Build 2026 and the platform that keeps absorbingnews
- Naming things: the actual rulesessay
April 14
- Hiring juniors in 2026essay
- Search is hard and you should probably not build itessay
- Migrations that don't wake anyone upessay
- The three kinds of technical debtessay
- Accessibility is a testing problemessay
- The Cyber Resilience Act and the unpaid maintainernews
- The retrieval question, revisitedessay
- The API versioning decisionessay
- You still do not need Kubernetesessay
- Observability costs more than the thing it observesessay
- Infrastructure as code, ten years of lessonsessay
- Rate limiting: the four algorithms and when each is wrongessay
- Node 26 and the build step that finally disappearednews
- The joke RFCs are the best documentationessay
March 14
- Q1 2026, in one pagebrief
- The database you should have chosenessay
- Agent fleets in production: a field reportreview
- Why your build is slowessay
- Pattern matching arrives everywhere at onceessay
- The state of self-hostingessay
- Design docs people actually readessay
- Passkeys mostly won and nobody noticednews
- HTTP/3 and QUIC, five years inreview
- The cost of a meeting, in engineering termsessay
- GTC 2026 and the rack that draws a megawattnews
- Schema design is the only design that lastsessay
- GDC and the engineering nobody outside games learns fromessay
- Feature flags and the state space nobody testsessay
February 14
- The engineer's guide to saying noessay
- The 2026 web platform baselinenews
- On-call is a design problemessay
- Small models ate the middleessay
- Documentation is a product and you should staff it like oneessay
- Every company is briefly a model companyessay
- Type systems and the cost of being rightessay
- The EU AI Act's August deadlinenews
- What happened to microservicesessay
- Prompt injection is SQL injection without the fixessay
- SQLite in the browser and the end of the API round tripessay
- Streaming an Olympics: the hardest scaling problem nobody discussesessay
- Go and the case for boringessay
- The dependency budgetessay
January 14
- How to read a benchmarkessay
- Virtual threads, two years onreview
- Your monitoring is measuring the wrong ninesessay
- The component model and the plugin problemnews
- Local-first is finally practicalessay
- Rust's eleventh year and the shape of a finished languagenews
- The electricity bill arrivesnews
- Postgres 18's async I/O, four months inreview
- Reading code is a skill and nobody teaches itessay
- Post-quantum migration is a 2026 projectnews
- Verification is the whole job nowessay
- CES 2026: the power supply is the productnews
- AGENTS.md and the repository that explains itselfnews
- Five things that will actually change in 2026essay