Monday morning. Updated my IDE. Updated my browser. Ran npm upgrade. Encountered new bugs. Why can't our industry focus on releasing stable software and shipping updates that reduce bugs without introducing new ones? I thought everyone except for me must be doing 100% test-driven development by now, especially the corporate devs?

You have decided to use npm. Did you really expect to get something else?

As a corporate dev, no, no one is doing TDD, not even 50%.
And even if it was 100% TDD, it doesn’t magically save you from bugs.

I don't know about TDD but software testing is never robust and doesn't meet the goal of avoiding/reducing regression bugs

In some cases, bugs are introduced hoping those won't get noticed or they didn't get the attention necessary to be classified as critical bugs to be addressed before releasing

@Lensflare you only test to expect what's going wrong as a nerd. Best software I made was handtested by people relaying on the software. As result you get super good input, also for features and our software costed money for users so they didn't do bullshit inputs what you normally test with unit tests

There's a picture of how qa's work: a guy walks into a bar and orders 99999 cokes and 5000 fries. Everything goes ok. Now there comes a guy order one coke and one fries and the bar gets on fire

@retoor was that one Coke actually Alcohol?

@retoor QA person walks into a bar and orders 1 beer.
Then orders 5 beers. Then 9999999 beers. Then -1 beers and finally sqrt(-1) beers.
Everything is fine.

Then a normal user walks in and asks the bartender where the restroom is.
Bar catches fire and burns down.

@Lensflare that was the image huh?

@asgs nah, thin white line. It was one of those places