> In most teams, coding - reading, writing, and debugging code - used to be the part that took engineers the most time, but that is no longer the bottleneck.
I keep seeing this statement as a prelude to "AI changes everything", but my experience never really had me see writing as the bottleneck, but rather designing (technical and not) and supporting what's already there while building the next thing. If anything, being able to execute faster puts more pressure on those two parts of the process.
"We will probably see fewer full-stack engineer openings and more roles for back-end and front-end engineers."
That doesn't appear to be the case now, well after the ascent of AI began. Job descriptions indicate that employers believe AI allows your average engineer to fulfill the responsibilities of front-end engineer, backend engineer, system architect and (to a lesser degree) DevOps.
> In most teams, coding - reading, writing, and debugging code - used to be the part that took engineers the most time, but that is no longer the bottleneck.
I keep seeing this statement as a prelude to "AI changes everything", but my experience never really had me see writing as the bottleneck, but rather designing (technical and not) and supporting what's already there while building the next thing. If anything, being able to execute faster puts more pressure on those two parts of the process.
"We will probably see fewer full-stack engineer openings and more roles for back-end and front-end engineers."
That doesn't appear to be the case now, well after the ascent of AI began. Job descriptions indicate that employers believe AI allows your average engineer to fulfill the responsibilities of front-end engineer, backend engineer, system architect and (to a lesser degree) DevOps.
as a skinny slice engineer you will promote maintainence of single pizza team performance.
this is to note that those concepts talk about *family* pizzas, not regular, single person pizzas.