|
|
|
|
|
by rudolph9
252 days ago
|
|
Best I can tell, it’s resulting in less churn, which isn’t the same as work getting done faster. Maybe it’s a phenomenon unique to engineering, but what I’m observing isn’t necessarily work getting done faster — it’s that a smaller number of people are able to manage a much larger footprint because AI tools have gotten really good at relaying existing knowledge. Little things that historically would get me stuck as I switch between database work, front-end, and infrastructure are no longer impeding me, because the AI tools are so good at conveying the existing knowledge of each discipline. So now, with a flat org, things just get done — there’s no need for sprint masters, knowledge-sharing sessions, or waiting on PR reviews. More people means more coordination, which ultimately takes time. In some situations that’s unavoidable, but in software engineering, most of the patterns, tools, and practices are well established; it’s just a matter of using them effectively without making your head explode. I think this relay of knowledge is especially evident when I can’t tell an AI comment from a human one in a technical discussion — a kind of modern Turing Test, or Imitation Game. |
|