Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
A fine example of the problem with current software development philosophy and it's unbridled, unthinking love of all things testing related. That right there is unthinking dogma. Every test has a cost. Every test is code. That conversation is one that simply demonstrates a mindset that does not consider those things. What if the resting was difficult? What if the tested feature was minor? Is it Ok the spend $1000 to write a test for a $10 feature (always assuming a manual test will take place)? Companies are chewing through $$$ at an incredible rate as a result of blithely performing actions with a high negative ROI, all for little to no gain in quality. Because it's dogma.
kamen56722y"I refactored login to take email address and username."
No, you didn't refactor anything, you changed the functionality.
@monkeyboy also, IT is trendy. Decision makers do not deal well with bucking trends. When something goes wrong, some dipshit consultant will tell their boss that their guy did not do something that is industry standard at the given moment. Who is going to put their neck on the line that way?
@funkyboss , I think we're in the same ballpark: "dogma" mostly the same as your "make work". I think the "right" implementation involves some common sense rather than doing things by rote. So, in some cases "write tests for everything first" is actually the right thing. Other times, it's not.
(yes I have a google alert on myself... sooo)
You might like the section on "uses until modification," a definition of "spiking," and "confidence" that I provide, as well as Opdyke's thesis for a fuller discussion.
I'm joking about the term being used imprecisely, not claiming TDD is the only way to work.