Developers: "The problem is that the faster we go, the more we get things wrong and have to fix them or do them over again, which actually makes us slower overall"

Big Tech: "I see, yes. What if... hear us out... what if you could get things wrong much, much faster?"

@jasongorman well... depends if it's bandwidth or response time.
@jasongorman yeah I was thinking about this yesterday. Bugs are found by spending more time with the code and realizing mistakes. 😥
@jasongorman I remember having normal, sane discussions among stakeholders and devs of the form "can we sustain 1, 2, 4, or 12 releases every year ?".
Now it's like "we are pushing a CI/CD build every day, automated regression tests are good enough". Get ready to tell everyone "it will be fixed in the next release".
Nobody is rewarded for opposing velocity. You keep up with the chaos as long as you can.

@jasongorman

turning a big dial taht says "wrongness" on it and constantly looking back at the market for approval like a contestant on the price is right

@jasongorman Definitely! The current state of game development is a stunning example. I used to gasp at a little flaw. Now? You go through 10 games and find one that is maybe 50% OK. Complain and the devs blame your hardware that wasn't bought 5min. ago.
@adritheonly @jasongorman Compared to other software, game development is still an haven on code quality IMHO.
@antopatriarca @jasongorman Oh dear! We're stuffed then, aren't we? Gone are the days of going to the Moon with a PC running DOS.
@adritheonly @jasongorman Absolutely... Now is the time for code editors requiring 8+ GB of RAM to run.
@jasongorman Payday loans for technical debt. What could possibly go wrong?
@jasongorman @AndrewHenry bonus: what if you could get things wrong in ways you used to before you had experience? And if you're very lucky, what if you could get something catastrophically wrong?
@jasongorman I'd like to introduce Big Tech to the concept of inertia...