Microservices Are Not an Architecture. They Are a Consequence.
Nobody chooses microservices because they are a good starting point. On service decomposition done right.
DevDick / Field notes
Engineering decisions, research, setbacks and progress. A closer look at what changes—and what it means for people building software.
Nobody chooses microservices because they are a good starting point. On service decomposition done right.
Amazon S3 can handle anything you throw at it. The code that talks to S3 often cannot.
The mental model that makes async Python straightforward.
I built a production LLM agent cutting response time from 8 minutes to 30 seconds. An honest assessment of where LLMs win and fail.
Application-layer validation can have bugs. The database constraint cannot.
After 12 years, the skill that has determined outcomes more than any technical competency is clear cross-disciplinary communication.
Event-driven architecture solves real problems. It also introduces real complexity.
Redis is a cache first. The systems that treat it carelessly are the ones that lose data at the worst moment.
Rate limiting protects your system from abuse and your legitimate users from the consequences of others' abuse.
Read new published articles in your RSS reader. No account needed.
Good software starts with better questions.
Explore my work