Live data from Hacker News

Saying goodbye to Agile

lewiscampbell.tech

1–10 of 271 posts

Re: Saying goodbye to Agile

#2
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.

Re: Saying goodbye to Agile

#3
I really doubt spec driven development is gonna last. As before, creating working software and iterating on it is faster and makes it easier to understand what you thought you wanted but don't, even if it's vibe coded. So, hello agile, welcome back.

Re: Saying goodbye to Agile

#6

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.

>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?

Re: Saying goodbye to Agile

#8
Someone once described agile as this: Its just pantomime and posit notes... implying that the process (from the outside) was more performative than anything else.

From "scrum masters" to "planing poker" it's all very silly.

Re: Saying goodbye to Agile

#9
post #3

I really doubt spec driven development is gonna last. As before, creating working software and iterating on it is faster and makes it easier to understand what you thought you wanted but don't, even if it's vibe coded. So, hello agile, welcome back.

I think there is some good middle ground between spec driven development and iterations, like Compound Engineering. https://github.com/EveryInc/compound-engineering-plugin

Re: Saying goodbye to Agile

#10

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.

"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.

Post reply on HN