Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
stisch46038yWhat if you're a game developer and no lives are jeopardized by your bugs whatsoever?
-
metaory15098y@stisch you should code as if your users lives depends on your stability and robustness
-
@stisch you'd be amazed at how many times I have taken my own life due to an unstable game...
-
So much this. I work on programming robots, and breaking $4000 hardware because of stupid bugs that could have been caught in review or testing is unacceptable.
-
wicho25608y@Jase I don't know...Maybe because I find it not as intuitive. You make cookies and then you try them and I haven't use it so much but how do you test a complex ajax website?
-
@thureos you should try BDD then... I hate to sound like a hipster, but it's SO MUCH BETTER
-
wicho25608y@johnny-cache a friend told me about it... I haven't had the chance to try it... I hope to do that soon though...
-
willol13898y@thureos well you don't test a complex Ajax website with TDD, it's not what's it's for. You test small parts, function by function.
TDD only guarantee that every function do what it advertise, if you want to check if the functionalities of your website are OK, look toward functional tests
Related Rants
IF LIVES DEPEND ON A SYSTEM
1. Code review, collaboration, and knowledge sharing (each hour of code review saves 33 hours of maintenance)
2. TDD (40% — 80% reduction in production bug density)
3. Daily continuous integration (large code merges are a major source of bugs)
4. Minimize developer interruptions (an interrupted task takes twice as long and contains twice as many defects)
5. Linting (catches many typo and undefined variable bugs that static types could catch, as well as a host of stylistic issues that correlate with bug creation, such as accidentally assigning when you meant to compare)
6. Reduce complexity & improve modularity -- complex code is harder to understand, test, and maintain
-Eric Elliott
undefined
tdd
bug
save lives
resolution
testing