3 ms·
Blaming Agile for software stagnation puts the wrong villain in the wrong play
- blueflow 2y agoAfter like 5 paragraphs without any red string or point being made i gave up. Is there any connection between the title and the text? It feels like some good AI talking random tangential things.
- alphazard 2y agoIt's more about the wave of imposters that came with Agile, than the methodology itself. There are more non-technical gatekeepers in software than actual engineers. Many of the important decision making responsibilities have been factored out of real engineering roles and assigned to Imposter Roles (think titles ending in "Manager"). At most tech companies, the ability to innovate is severely limited by the intellectual capacity of several imposters inserted along the critical path.
- porridgeraisin 2y agoIf a framework claims to solve a human resources problem, than then turns to be ridiculously susceptible to human resources misusing it, then that framework is not of much use is it.
- alphazard 2y agoI think we agree. My point would be that any framework which calls for or normalizes imposter roles is going to stifle productive output. The Agile manifesto clearly does that. https://agilemanifesto.org/principles.html https://agilemanifesto.org/principles.html > Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. This basically normalizes product managers being incompetent. Anyone can jerk the engineers around and be reactive. It takes expertise to not waste resources on the wrong thing. > Business people and developers must work together daily throughout the project. We know this is bad for engineering output empirically. You need to leave people alone to get work done. But giving the "business people" something to do legitimizes their imposter roles. Better check in on the engineers every day. > The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Imposters are adept at feigning value creation in meetings. Ask for details in writing: no shot. In a meeting, where they can nod along with people who actually know what they are doing, is where imposters really shine. Also another work activity to legitimize the imposter role.
- AnimalMuppet 2y agoWell, you know, engineers are famous for "can't code their way out of a wet paper bag" even though they sounded great in an interview. That's what FizzBuzz is for - to find out quickly if candidates can code at all. So it's not like imposters are only in non-technical roles. > > Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. > This basically normalizes product managers being incompetent. No, it normalizes product managers doing their jobs. If external circumstances change, do you want to keep building the wrong thing, or do you want to respond? Agile is all about responding when things change. But you need a product manager who is competent to do the right changes, and only those, rather than changing with every morning headline. But if you're not doing agile, you still have the same problem. If your product manager isn't competent to steer the delivery as circumstances change, how are they competent to get the requirements correct enough that they won't need to change for a year-long project? Answer: They aren't. (But agile may make their incompetence more frustrating day-to-day to the engineers, instead of letting them enjoy the sense of accomplishment of happily building something to completion, even though it's the wrong something.)
- AnimalMuppet 2y agoEverything is susceptible to being co-opted when it becomes popular, and sometimes even when it doesn't. Any religion, any political platform, any protest movement, anything with any kind of a group identity can be misused by those who want to have that identity without having to actually meet the qualifications. Expecting a one-page statement of a development philosophy to not be susceptible to that is expecting the impossible. Agile at least pointed out that the way development was being done was inhumane. That resonated with a large number of people. People wanted that more humane development style - that's why agile had so much appeal. Calling agile a "framework" seems off, though. It was a philosophy, or perhaps a set of values. A framework is something more codified and rigid - which is exactly the problem, that people tried to make agile codified and rigid. "We're going to be agile according to a rigidly defined process" is an oxymoron. But not being a framework, not being rigidly defined, there was nothing formal that stopped anyone from putting the "Agile" label on things that were antithetical to the Agile Manifesto. But they are in fact antithetical - it's like the practitioners never actually understood the manifesto, or else were never willing to actually change to correspond to what it said.
- deleted 2y ago[deleted]
- stavros 2y agoThere definitely is stagnation in software, but Agile doesn't seem to me like the culprit? I more blame the infinite abstraction layers we design, because we can't be bothered to learn about the details of the system we're using, and we'd rather use an abstraction that makes the easy things easy and the hard things impossible. It still puzzles me how many web developers in the company I work for don't know how HTTP works. If anything, we used to have much fewer, but much more competent, developers, and with the explosion of demand, the bar was lowered to include the (many more) less competent people. The only way the less competent people can produce usable software is if things are made easier, and they struggle with understanding the systems more deeply.
- JohnBooty 2y ago"Agile" is so vague, I don't even know what people mean when they're talking about it. It's like trying to talk about socialism or feminism - huge, nebulous terms and everybody has their own definition. I feel they are almost never ever talking about the original Agile Manifesto, which is pretty minimal. It's more of a rejection of "waterfall" than it is a set of actual practices: https://agilemanifesto.org/principles.html https://agilemanifesto.org/principles.html When people hate "Agile" my experience is that they are generally talking about Scrum, or some ad-hoc derivative of it as seen at many companies.
- ryandv 2y agoAnother linguistic confusion here. The author doesn't seem to clarify what exactly he thinks "agile" even means, which is not really surprising given that the original formulation [0] of "individuals and interactions over processing and tools" has somehow been co-opted and appropriated by the Scrum certified managerial class into an enterprise-scale methodology. There is Scrum(tm), and then there is kanban, and eXtreme Programming/XP, and your own homespun variant of "agile" that your team honed after a couple of years of working together and evolving your own working agreements... which one is under discussion here, and what are your definitions? The equivocation deepens once the author starts bringing devops into the picture, widening the already frighteningly large umbrella term "agile" into a diffuse, ill-defined mess: All the sins Marlinspike ascribes to Agile - siloing, big picture blindness, suppression of skills acquisition - are explicitly addressed by devops, which is entirely compatible with Agile. That being said, Moxie doesn't seem to clarify what _he_ means by "agile," either: Anybody who is managing an engineering organization will have some kind of management philosophy that is in some way downstream of, derivative of, in the zone of, or somehow related to agile [...] [1] - but given that both his remarks and TFA's recapitulation of those remarks tend to revolve around technical practices, and abstraction in particular, let's try to bring an infamous example to bear to illuminate what exactly Moxie meant by "onboarding people into software by putting them into black box abstraction layers:" Ron Jeffries' sudoku solver attempt (found at [2] and discussed ad nauseam here on HN [3]) using an array of technical practices often espoused by the "software craftsmanship"/eXtreme Programming constellation of Agile: TDD, obsessive refactoring and renaming, and object-orientation to the extreme, hoping that if you soak the problem in sufficiently many layers of abstraction, the solution will just magically fall out. Five articles into Jeffries' saga and he is still refactoring and extracting objects; Peter Norvig's solution [4] by comparison is about 200 lines of Python, without a single class definition, in a shameless and brutalist (metaphorically) procedural style. I would venture to guess that it is the former style of programming, overladen with tangled object graphs and pigeonholing of problem domains into object-oriented solution spaces (which accompanies much of the old-school Agile Manifesto and eXtreme Programming crowds) that Moxie is rallying against. Norvig's solution, on the other hand, is indeed "wizardrous" and exhibits the quality of deeply understanding the problem that Moxie espouses. There are hardly any abstractions to hide behind in those 200 lines. On a personal basis, I cut my teeth on eXtreme Programming and TDD and Uncle Bob and Fowler's "Refactoring", so I have seen their merits; unfortunately I feel that the craftsmanship movement these folks fostered has been co-opted, cargo culted, and diluted to the point of inefficacy. [0] https://agilemanifesto.org/ https://agilemanifesto.org/ [1] https://www.theregister.com/2024/08/09/marlinspike/ https://www.theregister.com/2024/08/09/marlinspike/ [2] https://ronjeffries.com/xprog/articles/oksudoku/ https://ronjeffries.com/xprog/articles/oksudoku/ [3] https://hn.algolia.com/?dateRange=all&page=0&prefix=false&query=jeffries%20sudoku&sort=byPopularity&type=all https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu... [4] https://norvig.com/sudoku.html https://norvig.com/sudoku.html