True, it would not have happened back in the day. But oftentimes what would happen is that sane, sensible leadership would have a talk about delays on the critical path and adjust the schedule accordingly.

Maybe not as satisfying to people who enjoy being heroes. But it would not have been an automatic disaster.

▲

xtiansimon 10 hours ago | parent | next [-]

> “…talk about delays on the critical path and adjust the schedule accordingly.”

And self-imposed deadlines are the worst—not saying that’s the case here. And when your leadership sets the goals, you do your best. But fast, good, cheap; pick two.

	▲	bunderbunder 9 hours ago \| parent [-]
		And if the deadlines really are hard, then you should be actively managing the critical path from the get-go. The very existence of upstream critical path dependencies that, as the parent poster’s story demonstrates, weren’t even necessary in the first place. Which suggests that this heroic agentic quick fix was the proverbial pound of cure. I’d even go so far as to speculate that perhaps agentic coding also steered people away from the ounce of prevention in the first place. Humans aren’t perfect either, but over the past couple years I’ve had to spend increasingly much time asking, “Why again are we creating all this unnecessary complexity?”

▲

archagon 20 hours ago | parent | prev [-]

“Look at how much more busywork I can do for the same salary!”

	▲	ffsm8 12 hours ago \| parent [-]
		Naw, you've missed a critical detail > My offshore team This is partially driven by the good old enterprise game of not being at fault when things go wrong and being able to communicate that to the stakeholders It's not fancy but it's necessary in a lot of enterprises