3 ms·
What I've seen before, and seems to be the case in comments here, is that beliefs about programming methodology are heavily influenced by what kind of programmi
by notacoward 12y ago
What I've seen before, and seems to be the case in comments here, is that beliefs about programming methodology are heavily influenced by what kind of programming a person does. Those who work on small projects (i.e. few parallel streams of development) love their agile/scrum/whatever. Those who work on larger projects are less sanguine. Likewise, front-enders also love the hipper methodologies, while back-enders tend toward the old school, independently of whether their projects are large or small.
The confounding case is the Linux kernel, which is both large and systems-focused but seems to eschew both kinds of methodology in favor of undirected chatter on mailing lists. Then again, maybe that's just part of a two-level process. More than a few patches to the kernel have real specs behind them, though developers don't call them that. They're just "kind of long, kind of detailed" emails. This tendency to embrace a thing while rejecting the term for it is one of the weirdest tendencies many developers seem to have.