IllustrationEngineering judgment
Why working code is not always good engineering
Correct output is a starting point. Maintainability and operational behavior need their own questions.
ENGINEERING NOTES
Working through the details
Practical reasoning about the systems we build and the decisions behind them.
6 notes
Illustration
IllustrationAI-assisted development
Using AI without outsourcing engineering judgment
Use generated code as a candidate implementation that still needs context, reasoning, and verification.
IllustrationTesting
Why passing tests is not enough
An assertion is useful only when it distinguishes required behavior from plausible defects.
IllustrationArchitecture
The hidden cost of unnecessary complexity
A new component brings an operational responsibility as well as a technical capability.
IllustrationArchitecture
When microservices are the wrong choice
Deployment boundaries should solve an identified problem that is worth their coordination cost.
IllustrationAPI engineering
Building reliable third-party integrations
Treat the external boundary as a contract with failures, retries, and evolving data.
No matching notes. Try another word or category.