News for hackers. Stuff that matters.
Re:ThoughtWorks Retreat: Where does engineering go? [pdf] by roncesvalles on Monday March 16, 2026 @05:04PM (#47404856)
Arguably the PM role only exists because SWEs don't want to do PM work, and the industry acquiesced to this because SWEs are in very short supply - if you could hire a layperson (sorry) to take a few hours of non-technical work off a SWE's plate, it is worth it.

In a (hypothetical; not quite there yet) world where SWEs are in surplus, there is no reason to have PMs.

The really eye-popping efficiency gains from LLM coding won't come from doing the coding faster but from consolidating the PM, SWE, and QA/SDET roles under the same person. Then you'll start seeing startup/indie level productivity-per-person inside large organizations. Imagine Google is like 50,000 Pieter Levels.

Re:ThoughtWorks Retreat: Where does engineering go? [pdf] by manphone on Monday March 16, 2026 @06:03PM (#47405578)
The concept of a large organization doesn’t even make sense in this model. How do you make decisions? How do you coordinate? What is Google when you have 50,000 individual silos?
Re:ThoughtWorks Retreat: Where does engineering go? [pdf] by mbrumlow on Monday March 16, 2026 @08:58PM (#47407265)
Decisions are less costly. When a swe can take 4 days to do what would have cost 6 months, the math of making sure you are doing the right thing before executing goes away.
Re:ThoughtWorks Retreat: Where does engineering go? [pdf] by manphone on Thursday March 19, 2026 @02:24PM (#47443694)
That has little to do with building code and a lot to do with customers and releases and operations - giant companies don’t just magically demo software to people.

There’s so many layers today that can’t exist if this is the way forward.