3 ms·
I totally agree about the process junkies ignoring good stuff and pushing their religion under banner of software engineering. They're the posers who weakened t
by nickpsecurity 11y ago
I totally agree about the process junkies ignoring good stuff and pushing their religion under banner of software engineering. They're the posers who weakened the term. The Bell Labs people were real, software engineers both experimenting and building on proven methods. Also...
"What we usually call "unit tests" these days, and certainly "mock objects""
That's not true. Like other assurance activities, Extreme Programming just did what was already done, gave it a new name, mixed it with bullshit (esp pair programming), and got it some needed attention. The Orange Book testing criteria, in 1983, required as much testing as resources allowed of primitives, their compositions, all interfaces, and common failure conditions. That's on top of specifications, covert channel analysis, pen testing, using only proven components, build system automation, etc that far exceed XP's quality regiment.
Funny you mention Cleanroom because it was first thing I thought of when I heard the "new" Agile approach. Iterative development, code reviews, usage-based testing for acceptance, verifying each module... Cleanroom had all that. At least they eventually figured it out and it seems competitors in Agile identified XP's problems as well. Although old, I'm glad the concepts are mainstreaming because it gave us something important: solid, well-maintained, constantly-updated TOOLS to support the efforts. :)
- kragen 11y agoYou're missing the point. XP testing isn't an assurance activity. XP "unit testing" isn't what's called "unit testing" in the software engineering literature, and it isn't designed to reduce bugs; it's an executable functional spec, and the reason you write the tests first is so that you don't end up designing some monstrosity of an interface whose clumsiness becomes contagious to everything that calls it. "Mock objects" are a particular way of writing those tests in which your testing stub objects actively validate that they're being invoked the way you expect, rather than just passively simulating the subsystem being stubbed out. Orange Book testing, by contrast, is aimed at reducing bugs. XP-style test-first unit testing is not the best way to develop all software, but it works pretty well for some things. Similarly for pair programming: it can help a lot with intra-team communication, code reviewing, and not getting stuck, but I'm pretty sure there are projects where working alone and doing the code review later is a better practice. Yes, Cleanroom has a lot in common with XP. I think that a lot of the "competitors in Agile" actually suffer from the same disease I'm blasting here: they try to solve technical problems with management practices, and consequently you have a lot of Scrum teams with really shitty code who can't make much progress because they're beginning programmers, or experienced programmers who have fallen into bad practices.
- nickpsecurity 11y agoAnother I agreed with almost entirely. Hell yeah! Yes, I read on unit testing and XP with its other goal. Most of what the crowd pushes it for is the benefit of catching defects usually with requirements, dependencies, or breaks from later changes. Old projects used testing for those reasons, too, although not as consistently. I'd say the real difference are greater focus on mock-ups and documentation focus as you said. Other than that, the techniques are similar and more ad hoc than before. Just getting more attention and use. Still A Good Thing. "I think that a lot of the "competitors in Agile" actually suffer from the same disease I'm blasting here: they try to solve technical problems with management practices, " Totally agree. This is a bad sign any time we see it. The focus should always be on getting the right people in there, making sure they have good tools/methods, and letting them get shit done. That's development or engineering. Documentation, etc really just becomes evidence of what was done and an aid for further development/maintenance. I'll add that I think there's a zealot kind of thing going on. They blasted me years ago with all of the stuff like it's better while not providing any empirical evidence showing it was. Some evidence appeared around testing, etc and Spiral already proved incremental approach would help. Much of it had nothing but some people's word to back it. Pair Programming even countered years of evidence about effects of interruptions on flow. So, I think it would help if they or the next group focuses on controlled studies pitting methods against each other on similar projects with objective and subjective accounts of results. Then, we'll have a better handle on what works and where. Right now, I have to rely on little empirical data and mostly just take the word of the experienced people delivering best results for given domains. Gotta get programming a bit more scientific in industry.