Var0

Good code doesn't only describe what it does. It communicates why it exists. A look at how intent shapes names, abstractions, comments, and commit messages.

Retries are great for transient failures, but they can't solve eventual consistency. Treating one problem as the other often adds unnecessary complexity to distributed systems.

Everyone recognizes a microservice but nobody can define one. That's because microservices don't solve a technical problem, they solve an organizational one.

The industry conflates perfection with over-engineering. They're not the same. Over-engineering is solving the wrong problem; a perfect solution exists once the requirements are clear.

Every abstraction leaks. GraphQL is the only one I know that leaks in both directions: out to the frontend and back into the backend.

2 Posts, 0 Following, 1 Follower Software engineer interested in distributed systems, privacy, and music. Currently building something, most likely.