4 ms·
Yes. Being forced to push changes to production with zero test coverage, and hence zero confidence in your code on a Friday night. (true story) After that you
by engineerDave 10y ago
Yes. Being forced to push changes to production with zero test coverage, and hence zero confidence in your code on a Friday night. (true story)
After that you always make sure test exist before even pondering a push of potentially breaking changes! :P
- mordocai 10y agoOh yeah, I mean I always write tests for anything for work. I don't do TDD all the time though, sometimes I write the tests after the code. A language/framework that forced me to do TDD would just piss me off, which was my original point.
- engineerDave 10y agoI was being tongue in cheek on that one, sorry if it didn't come across that way. Although I've been a Rails dev for 6 years now, I've come to hate the TDD approach and am a convert of FP and types, & compilers a la Haskell. Because there really is no such thing as a massive change in FP IMO. Unfortunately I'm not competent enough in it yet so Rails still pays the bills.