6 posts

#engineering

Articles tagged #engineering.

← All articles

(01) Choosing a tech stack in 2026 — stop optimizing for greenfield Tech stack debates assume greenfield. Real projects inherit existing code, team expertise, infrastructure decisions made years ago. Picking the "best" stack in 2026 is mostly about matching what your team already knows. The shiny new framework rarely wins. (02) Secrets management without a vault platform HashiCorp Vault, AWS Secrets Manager, Doppler — paid vault platforms are great, and overkill for small teams. Smaller teams can handle secrets cleanly with simpler tooling that fits within their cloud provider and developer workflow. (03) Serverless cost traps and how to avoid them Serverless promises pay-only-for-what-you-use. Real bills frequently surprise teams: 50x estimated cost from unexpected patterns. The traps are predictable and avoidable if you know what to look for. (04) From monolith to modular monolith — when to skip microservices Microservices were the default architectural answer for a decade. In 2026 most teams that adopted them are walking back. The modular monolith is a saner middle ground for teams of 5-50 engineers. (05) HTMX in production: where it works and where it falls apart HTMX promises SPA without SPA: attributes on HTML, server returns HTML fragments. Three production projects later — here is where it really is simpler and where it hit the wall. (06) Claude Code writes 4% of all public GitHub commits — what it means for teams SemiAnalysis says 4% of public GitHub commits ran through Claude Code in March 2026. They project 20% by December. Here is what actually changed in hiring and review.