3 ms·
I disagree. My own company in the very early days had an immense boost of productivity without tests, just by building the damn thing and failing loudly. Once w
by DanFeldman 7y ago
I disagree. My own company in the very early days had an immense boost of productivity without tests, just by building the damn thing and failing loudly. Once we got everything wired up and errant semi-colons were blocking merges, testing was a logical next-step.
- ambicapter 7y agoWriting code without thinking about tests is a great way to make writing tests a HUUUUUUUUUGE pain in the ass. Thus ensuring they never get written, and everyone is happy :)
- DanFeldman 7y agoYes, it was a pain for everyone when we had no tests in the early days (REALLY early). My main point to the OP is that you still get benefits with CI/CD for compiled projects if you only build during integration. We now have a very healthy test suite and workflow 2.5 years later. It's ok to start small and not boil the ocean immediately when jumping into modern ci/cd workflows.