3 ms·
Agile works for web services, for small apps, but that’s it. That's plainly not true. Many large applications are written by agile teams. Anything larger, or
by matthewmacleod 11y ago
Agile works for web services, for small apps, but that’s it.
That's plainly not true. Many large applications are written by agile teams.
Anything larger, or more complex, needs planning, thought, and design. And often needs refactoring.
Yes – none of these things are banned by agile development. Refactoring is positively encouraged!
It’s rare that you can build a system where you don’t have issues with concurrency (and need to do timing analyses) or with interactions between multiple different systems.
Absolutely. This has no relation to the development process used to build those systems.
- kuschku 11y ago> Absolutely. This has no relation to the development process used to build those systems. Yes, it has. Agile encourages people adding features without previously planning every single interaction of the feature with every other piece of software. Which means, Agile encourages writing code without being sure it will interact safely with other parts.
- dustinleblanc 11y agoNo, it doesn't, you are making things up. There are plenty of agile/scrum teams who run continuous integration that won't allow code that breaks a build to even be in production. They write integration tests and acceptance tests and all of it is done with sprints and iteration. Agile does no encouraging of adding features. It simply gives you the freedom to choose which ones get implemented based on the current knowledge rather than be forced to make those decisions based on 18 months ago knowledge.
- kuschku 11y agoSure? Because last I remember, Google is constantly shipping their Android Compat Libs with constant integration issues. You’d assume that at least Google gets it right.