News for hackers. Stuff that matters.
Re:It’s not the methods that are Agile, it’s the people by wpietri on Thursday November 24, 2016 @08:28PM (#13033854)
> You can't judge practices based on how they work for one particular area of software development. Especially when said area is one of the simplest out there.

You know exactly nothing about what I've based my opinion on. Because all you've done is jump in and rant about your beliefs.

> thinking about said architecture upfront with twice the development time

Design quality is limited by the information you have, and no amount of thinking creates information. The beginning of the project is when you have the least information about everything: domain, users, user needs, business needs, technology, team. Everything.

You mostly get information by trying things in the world. And actually trying things in the world is the only real test of ideas that come from thinking.

If your methodology requires understanding everything up front, then it's basically useless in the real world. Even if you could perfectly understand your intended market and use case, that will change over time. But you can't, because your competitors are always plotting to beat you, and they will not share their plans with you.

Amazon, for example, has been in operation 20 years, and could easily be going for decades more. If in the early days they had tried to write code capable of dealing with their current needs, let alone their needs from 2050, they would have been idiots. Pure up-front design is an unworkable fantasy.

> More importantly, how are you going to add proper abstractions to an existing project? No refactoring tool will ever do that [...]

Refactoring existed before automated tools, and mostly exists beyond it. Tools help, but it's mostly a human activity. Try reading Fowler's book on this, and his subsequent writing. You can't effectively criticize something you don't even understand.

There are no comments on this comment yet.