1,712 karma · joined March 5, 2018
Sadly, people have been trained not to because devs always say, "Bug fixes and improvements".
Some people really do want to know what changed.
Edit: Thinking about this article more, it really goes back to hardware not getting funding unless there's a model for recurrent income. It's going to get a LOT worse before we either wise up or give up.
Can we? I don't see anyone on either side [0] of the isle doing much of anything about this.
> But more importantly, I won't be spirited away to a black site by speaking ill about the president.
No, but you can be if you're in Portland any time soon.
[0] Why TF are we stuck with TWO?
Nothing before.
[0] Not minimizing this, it’s just that our bodies tend to react to allergens in certain ways.
Rare, but it happens. The people who think this is more than a rare occurrence are not well educated on the needs of the poor.
It's just a test.
Most people reading the bible don't do this. This would be very very odd.
When it happens, deal with it - odds are it won't. Expend the energy making the code base testable not pretending to be an insurance company ("In case sh..").
This is where "make it easy to test" comes in.
And, sure, there are some things that are easy to anticipate. If you're processing CSV, you may get asked to process arbitrary delimited files next. But the point is 3 - 5 years out, you'll get asked for something the current architecture cannot support and a major effort will be required. You cannot anticipate those and thus should never try to.