3 ms·

Developers will do anything not to write tests

• mdaniel 3y ago
  My life experience has been that is often the intersection of two very hard problems: test-thinking is a learned skillset that often consumes a lot more active-thought than implementation-thinking and, as I repeatedly and loudly say to my team: testing is always AGAINST REQUIREMENTS. No requirements means no accurate tests, only busywork/metric-gaming. And, as I also always point out: no, your fever-dream one sentence statement of outcome is not a "requirement" The bad news is that often the business folks don't know what they want, either, which is how "agile" became a thing. I recognize the ship has sailed on that, but it's "cake and eat it too" to think one can have good tests and ship "PoCs that do something valuable" in 2 week increments