4 ms·
I take it you've never worked in that type of an environment, with code review and (good, not necessarily perfect) test coverage. I am working in an environment
by anthony_r 6y ago
I take it you've never worked in that type of an environment, with code review and (good, not necessarily perfect) test coverage. I am working in an environment like that and I regularly push 20-40 changes per week. There's no problem with speed. Furthermore, had there not been tests (and not just unit tests; the important stuff is large scale performance tests and output differs) I would never be able to push code out so quickly.
- mattmanser 6y agoI can regularly push 20-40 changes per week, with or without tests. What's special about that? How can writing MORE code be faster? Be honest with yourself, you know it's slower, it's hard to get right, and it's easy for many programmers to end up writing really bad tests that hinder rather than help. Certain orgs might be able to pull it off, but generally speaking it's cargo culting.
- UK-Al05 6y agoIt works because tests provide you with incredibly fast feedback if your change works or not. Then you can confidently and automatically deploy to prod straight away without much manual checking.