Earlier quoted context omitted.
There is never a right way, only trade offs. The thing about being a Monday morning quarterback is that you can always claim you would have used even more caution and process.
> you can always claim you would have used even more caution and process. Well, specifically, my claim is that any serious professional in this industry would have done so. But we're essentially in agreement, in the sense that yes, I am allowed to make this claim, and in fact already did, in the comment you are replying to. EDIT: Actually I've been thinking about this a bit more. The thing about commenting on somethi…
As a serious professional in the industry - we're dinosaurs. Nobody cares anymore.
The kids are running the show and are making billions with stuff that doesn't work. But it makes money so nobody cares.
This is not a new phenomenon, it started years ago and really took off when JS became the new hotness. You could see it happening live, right here on HN. But the blast radius is massively increased now with AI and people are getting hurt. It's not funny.
The ship has sailed on rigor.
The sad thing is that this is not going to get better. The best we can hope for is slight improvements to agentic "engineering" practice with lots and lots of blog posts on HN written about how they are rediscovering basic engineering practices.
We (the dinosaurs) will roll our eyes while making a fraction of the money the kids are making.
And even if the whole AI ecosystem implodes (it won't) that would be a massive recession and certainly wouldn't make the remaining software engineering work more rigorous either.
As the Simpsons put it: "An I out of touch? No, it's the children who are wrong."