Technologies covered on this site
Tools and systems this site writes about most often, reflecting my own background and areas of interest.
By the numbers
Editorial process
Here's how articles on this site actually get made, and where the human involvement is versus where it isn't:
Topics are drawn from a curated list of recurring themes in backend engineering, AI systems, and developer careers — areas I have direct interest and background in, covering patterns and trade-offs that are widely discussed in backend and AI engineering.
Articles are drafted with AI assistance, grounded in official documentation and established best practices. Some articles use a first-person "I" or "we" narrative with specific numbers or incidents to make trade-offs concrete — treat these as illustrative scenarios composed to reflect common real-world patterns, not as verified case studies from a specific company or system. Given the volume published here, not every article gets individual line-by-line review before it goes live — I rely on the correction process below to catch and fix mistakes.
I periodically review published articles, particularly ones getting traffic or reader feedback, and update or remove anything that's wrong, outdated, or doesn't hold up.
If you spot an error, tell me and I'll fix it. Technology also changes fast enough that older articles get revisited and updated as tools and best practices move on.
Found a factual error? Email me directly — I review and correct reported errors promptly.
Recent articles
-
Senior without the title: what stalls engineers
2026-11-18
-
Security engineering isn't a ladder
2026-11-17
-
RBAC vs ABAC: pick by blast radius
2026-11-17
-
Kubernetes Requests and Limits: Seven Production Traps
2026-11-16
-
Human-in-the-loop: when agents need a human veto
2026-11-16
-
Multi-region active-active: the hidden costs
2026-11-15
-
Python deps: uv vs Poetry vs pip-tools
2026-11-15
-
Your platform team is too big
2026-11-14