Re:Ask HN: How do I know if the startup I'm working at is dy...
by viredfox on Thursday June 12, 2014 @10:36PM
(#7887204)
To be fair, I think it's more of a concern that trying to write tests would slow the actual work down - I was trying to write regression test (still unit test, but definitely not tdd).
Re:Ask HN: How do I know if the startup I'm working at is dy...
by avelis on Thursday June 12, 2014 @10:56PM
(#7887242)
Writing unit tests do not slow work down. It actually makes time more efficient by ensuring working code continues to pass over time. This has huge returns in how a developer can now spend their time.
Re:Ask HN: How do I know if the startup I'm working at is dy...
by jf22 on Friday June 13, 2014 @07:04AM
(#7888142)
Well lets be clear unit testing temporarily slows immediate progress down while potentially increasing future productivity.
Sometimes its beneficial to get a feature out the door sooner so sometimes unit testing isn't best for the business needs even if it does slow down future progress.
Right now, you want to be pushing to gain skill as quickly as possible. The skills and habits you develop now will pay back tenfold later on. This probably means being surrounded by developers smarter than you, sooner rather than later.
I'm not a TDD "fanatic" or whatever that even means, but some amount of automated testing is a sensible form of risk management. If you're being actively discouraged from pursuing it, you're the smartest guy in the room.
That means it's time to move on.