Slashdot Mirror
Alan Cox on Writing Better Software
Andy Gimblett writes "Alan Cox recently gave a talk in which he discussed some current and emerging techniques for producing higher quality software. Some of these will be familiar to Slashdot readers, such as validation tools, type checking, etc, but others seem heavily influenced by his recent MBA. In particular, he has a lot to say about Quality Assurance in the software world, and the kinds of things we should be doing (and some people are doing) to make better software. Story and lots of quotes at Ping Wales, and video at IT Wales."
he has a lot to say about Quality Assurance in the software world
Quality Assurance in 4 easy steps!
Dear Managers,
1. Listen
2. Close your mouth
3. Plan everything around #1
4. Profit!!! (notice there is no line with ??? because you listened!)
The dangers of knowledge trigger emotional distress in human beings.
Who cares about what Alan Cox has to say? He's soooo 2.4
However the greatest problem with writing good software is still in the marketing. In order to sell/license software it needs to have features, and the lack of defect often does not count as "features".
Is he back on full time linux development now?
:)
"Alax Cox gave a talk"
Was it in Welsh?
It's slashdotted..
Btw He didn't write it in Welsh did he? Coz Wales officially doesn't exist http://news.bbc.co.uk/1/hi/wales/3715512.stm
The kicker is, this year that same manager wants to re-use the code that my coworker was origionally going to write.
Against stupidity, the gods themselves contend in vain.
Sometimes it is just contemplating if it makes good sense. Sort of like "I wonder if it makes good sense to take an Internet browser that connects to the most insecure network on the planet, integrate it completely into the operating system and don't properly validate data that is recieved.
From excellent karma to terible karma with a single +5 funny post...
Wonder if he also talked about being on a chip. ;-)
I'll leave the results as an exercise for the reader...
"regression testing, what's that? If it compiles it works and if it boots it's perfect!" - Linus
'nuff said
If thou see a fair woman pay court to her, for thus thou wilt obtain love
emerging techniques for producing higher quality software
So now we're taking software writing advice from PHBs now? :)
Yeah, it's not like programmers are overworked with impossible to meet deadlines and ever growing feature lists. They could easily use their lunch hour working the support desk since they all just live on a strict diet of coffeinated bewerages anyway.
Oh no, someone with an education in MANAGEMENT suggesting ways to MANAGE a production process.
Yes your average programmer/engineer might be able to manage a project. But why not take some of the expertise of a manager to make it a bit better?
If someone like Alan Cox should now be ignored as "some MBA toting PHB" how open minded are you?
I think Alan might have a bit of an idea how the software development process works.
If you're not even willing to consider their ideas, you're doing yourself quite a disservice.
...but others seem heavily influenced by his recent MBA. In particular, he has a lot to say about Quality Assurance in the software world...
Software QA by normal people: Test the product.
Software QA by MBAs: Assure that twenty thousand meaningless documents are signed, perform audits to ensure that these documents are signed, provide mandatory training so engineers know how to sign these documents, award bonuses to those who sign the most documents, define productivity to be the number of signed documents in an engineer's cabinet.
Don't blame me, I didn't vote for either of them!