4 ms·

And good riddance too. Agile was always aiming to solve the wrong problem (that code is the bottleneck) but it turned out to be a massive lie exposed by LLMs.

And good riddance too. Agile was always aiming to solve the wrong problem (that code is the bottleneck) but it turned out to be a massive lie exposed by LLMs. It’s always the poor specs, terrible analysis and release constraints that kill projects.

DeathArrow 6mo ago
>It’s always the poor specs, terrible analysis and release constraints that kill projects. So most of the problems are related to business people and not the development teams? Who would have guessed?
- smackeyacky 6mo ago
  Holding analysts to account would be a good start. Agile lets them get away with laziness. It’s always “oh sure we got that wrong better luck next sprint”
k__ 6mo ago
"Agile was always aiming to solve the wrong problem (that code is the bottleneck)" No, it aimed to solve the "out specs are bad and we need to iterate faster" problem. "a massive lie exposed by LLMs" No. LLMs add no insight about the problem and they expose nothing. They just help to engage this well-known problem with another tool.
- smackeyacky 6mo ago
  Not in my experience. AI exposes the truth that agile as it is practised is a huge waste of time. All the bullshit ceremonies and short sprints were designed to get code squeezed out faster, no matter if the code actually addressed the goals of the project. The stupidity of agile is in its iteration speed since you can be handed utter crap, implement it to hit your story points and find out the drooling shitgibbon who wrote the specs phoned it in so your work is now wasted. Rinse, repeat.
prerok 6mo ago
Agile never claimed that. Agile is about working code instead of hundreds of pages of spec nobody reads.
- smackeyacky 6mo ago
  Ironically the AI guys are now saying good spec is what we need for the agents to code. So which one is it
rowyourboat 6mo ago
> always the poor specs But that is fundamentally what agile is about. It's not about coding faster, it's the recognition that the specs are incomplete or wrong because fundamentally, a lot of customers cannot tell you what the want until they see it. That's why "build something simple and iterate on it" works. Regardless of how good your spec is, once the coding is done the customer is going to realise that that's not what they actually wanted.
- smackeyacky 6mo ago
  This is a weird backwards logic to justify terrible analysis
  - array_key_first 6mo ago
    No this is literally in the agile manifesto. It's not logic at all, it's the written word of what agile is. What that means is that Agile and agile are not the same thing. Most companies practice Agile, very few are agile.

DeathArrow 6mo ago

>It’s always the poor specs, terrible analysis and release constraints that kill projects. So most of the problems are related to business people and not the development teams? Who would have guessed?

smackeyacky 6mo ago
Holding analysts to account would be a good start. Agile lets them get away with laziness. It’s always “oh sure we got that wrong better luck next sprint”

k__ 6mo ago

"Agile was always aiming to solve the wrong problem (that code is the bottleneck)" No, it aimed to solve the "out specs are bad and we need to iterate faster" problem. "a massive lie exposed by LLMs" No. LLMs add no insight about the problem and they expose nothing. They just help to engage this well-known problem with another tool.

smackeyacky 6mo ago
Not in my experience. AI exposes the truth that agile as it is practised is a huge waste of time. All the bullshit ceremonies and short sprints were designed to get code squeezed out faster, no matter if the code actually addressed the goals of the project. The stupidity of agile is in its iteration speed since you can be handed utter crap, implement it to hit your story points and find out the drooling shitgibbon who wrote the specs phoned it in so your work is now wasted. Rinse, repeat.

prerok 6mo ago

Agile never claimed that. Agile is about working code instead of hundreds of pages of spec nobody reads.

smackeyacky 6mo ago
Ironically the AI guys are now saying good spec is what we need for the agents to code. So which one is it

rowyourboat 6mo ago

> always the poor specs But that is fundamentally what agile is about. It's not about coding faster, it's the recognition that the specs are incomplete or wrong because fundamentally, a lot of customers cannot tell you what the want until they see it. That's why "build something simple and iterate on it" works. Regardless of how good your spec is, once the coding is done the customer is going to realise that that's not what they actually wanted.

smackeyacky 6mo ago
This is a weird backwards logic to justify terrible analysis
- array_key_first 6mo ago
  No this is literally in the agile manifesto. It's not logic at all, it's the written word of what agile is. What that means is that Agile and agile are not the same thing. Most companies practice Agile, very few are agile.