Articles
Worth reading
A short take on pieces worth your time — architecture, AI, system design, and engineering careers — each one linked back to its original source.
44 articles
Sequenced Collections in Java
A small but overdue fix to the Java collections API: a common SequencedCollection interface that finally gives every ordered collection — List, LinkedHashSet, LinkedHashMap — first/last element access and a reversed view, without the inconsistent workarounds we've all written over the years. Not a headline feature, but exactly the kind of quality-of-life change that quietly removes a class of bugs and boilerplate from day-to-day Java code. Worth five minutes if you touch Java collections regularly and haven't caught up on 21.
OpenJDK Project Loom
A solid, practical walkthrough of virtual threads — the biggest change to how Java handles concurrency since threads themselves, letting the JVM multiplex huge numbers of blocking I/O-bound tasks onto a handful of OS threads instead of paying the memory and context-switch tax for each one. If you're still writing reactive pipelines purely to dodge thread exhaustion, this is the article that explains why that tradeoff is largely gone as of modern Java LTS releases. Baeldung's usual strength: code you can actually run, not just theory.
Avoiding fallback in distributed systems
A genuinely counterintuitive argument from AWS's own playbook: fallback logic — the code path meant to save you when the primary system fails — is often the riskier system, precisely because it almost never runs and so almost never gets tested under real conditions. I've seen this bite teams that were proud of their "graceful degradation" story; the fix argued for here is investing that same engineering effort into making the primary path more reliable instead of building a second, untested one. Changed how I run resilience design reviews.
The Tail at Scale
The paper that explains why your p50 latency dashboard is lying to you: at scale, it's the tail — p99, p999 — that decides whether users experience your service as fast, because any single request has to survive every slow component in its path. Dean and Barroso's techniques for taming it, especially hedged and tied requests, are still the starting point for anyone designing a fan-out call pattern or arguing for stricter SLOs on a critical dependency. Dense, but every page earns its place — required reading before you design anything with fan-out on the critical path.