- adding automated testing to 🚀 linguanodon keep feeling like a net-negative
- definitely agree with ~ tests introduce friction and incur tech debt like any other code (especially friction)
- the project is past pretotype, yet I often find myself making fundamental changes to the data model, which often breaks 60% of unit tests (and all integration tests)
- and securely abstracting this feels like even more overengineering
I don't like automated test suites for fast-moving, explorative side projects
Backlinks
This is a Report note.