clean code guy @unclebobmartin says he creates good software without reading the code
was curious so I spent an afternoon reading some recent code.
not sure i agree, PR here 🤗
https://t.co/jvg92dMapO
TL;DR: read the code pls Bob
https://t.co/0T4E2qIeuq
true that agents bloat tf out of unit tests but its still the best way to set invariants/guard against edge cases into your code
good luck migrating/rewriting existing code without unit tests
tbh just dont get lazy when writing tests. dont vibe them and make sure they actually test behavior and not implementation
IMO the only tests you should have in the age of coding agents are, in order of priority:
1. Full E2E tests. Nothing mocked out at all. Can even be something that runs in prod on test accounts via Playwright or equivalent.
2. Integration tests. Agents make more mistakes as things bleed between data/API boundaries where schemas can drift.
3. Golden tests. This helps ground the code with real examples of data, and can be used as regressions against edge cases.
Unit tests are bloat 99% of the time if you’re using a frontier model since they’re smart enough now to get the implementation (and subsequent iterations) right on the first shot, so they only add bloat at this point.
even with the most beautiful login page,
0% marketshare gained - the “easy to use” cloud hosting platforms are already aws wrappers and any serious company will migrate from there to aws
just stop making cost manager cost money to view