Source & Architecture
GraphQL vs. REST
A practical comparison of GraphQL and REST: how each shapes API contracts, frontend flexibility, caching, observability, team ownership, and the operational trade-offs behind choosing one style over the other.
Writing
Blog
Deep-dives on software architecture and the way source code is structured — written to be understood by beginners, yet useful to teams shipping at scale. Diagrams, real examples, no hand-waving.
Latest articles — Page 22 of 23
Engineering Culture
Handling Burnout Before It Happens
A calm look at preventing burnout in engineering teams: early signals, workload visibility, recovery time, sustainable expectations, management responsibility, and the small habits that keep people from disappearing quietly.
AI & The Future
Multimodal AI: Text, Vision, and Audio
A practical introduction to multimodal AI: how text, images, audio, and video change product workflows, what becomes possible, and why evaluation, privacy, accessibility, and human review matter more as inputs become richer.
Perspectives & Field Notes
Dealing with Legacy Code
A reflective essay on working with legacy code patiently: understanding history, adding tests, making small safe changes, respecting past constraints, and improving the codebase without rushing into a rewrite.
Ways of Working
Shift-Left Security
A practical explanation of shift-left security: bringing threat thinking, dependency checks, secrets hygiene, secure defaults, and review habits earlier in delivery without turning every engineer into a security specialist.
Source & Architecture
Designing Idempotent APIs
A practical explanation of idempotent API design: why retries happen, how duplicate requests create risk, and how idempotency keys, stable state transitions, and clear response contracts make distributed systems calmer.
Engineering Culture
Creating a Blameless Culture
A calm look at blameless engineering culture: how teams can study incidents without blame, separate accountability from punishment, improve systems, and make it safer for people to tell the truth early.
AI & The Future
AI for Code Refactoring
A practical reflection on using AI for code refactoring: where it helps with mapping, options, tests, and mechanical changes, and why engineers still need boundaries, evidence, and verification before trusting the result.
Perspectives & Field Notes
The Art of the Meaningful Commit Message
A reflective essay on meaningful commit messages: how good history helps future debugging, review, rollback, onboarding, and team memory without turning every commit into a long document.