More on asshole driven development

Hey folks – apologies if you’ve had problems accessing the site. The last blog post on asshole driven development was a hit. I’ve had more traffic on that then anything I’ve written in history.

If you want more commentary and painfully funny methodologies there are additional comment threads on the three major drivers of traffic: Digg & O’Reilly Radar, And Reddit.

Tiff Fehr has put together an analysis of the different methods and comments to date. Worth a look.

There are still about 120 comments in the queue (out of almost 400 total) – if yours doesn’t get posted, please don’t call me an asshole :) Many of them were redundant, bizarre or beyond my level of comprehension. They’ll all get read, but at 100+ comments I’ve got to filter some stuff out.

Not sure which of you got the run going, but thanks to all who passed my writing around.

Posted Tuesday, June 26th, 2007 at 7:06 pm

in Management, Software/Web development | 5 Comments » |

Recent Comments

TurboTax Design FAIL
jason says..."I will second the TaxAct recommendation. I have used it for several years for my personal taxes and my S-Corp taxes for the last two years. It works great and is...'
#50 – Advice for new managers: pt. 1
Juan66 says..."Thank you, Thank you, Thank you Scott!. I too am a new manager in a new position in a dept that is going through growing pains and...'
The 22 minute meeting
Jim Dowson says..."One addition, one dispute. Meetings that start a xx:15 or xx:45 are much more likely to start on time. There is research backing this, but I don’t...'
How to write a book, part 2
Craig says..."That’s a great article. Perfect. It really encapsulates what it is to be a writer in an entertaining manner. I’m ashamed to say I liked the...'

Fireblaze - July 23, 2007 at 5:29 am #

I think you get that many comment because you describe the reality of many software projects. I hope you include the development processes here in your book “The Art of Project Management”. It would be invaluebale for project managers to know these processes, so they know when something is wrong. And know why people dont listen to them anymore.

GL - December 14, 2009 at 2:21 pm #

There’s EDD (Error Driven Design) which constantly took place at a former company. Tech support tickets and “this is broken” “that is broken” dictated what we worked on. I did not stay there long needless to say. We were not allowed to ‘analyze’ and ‘design’ – just code it please and NOW. Simple-minded MANAGERS are the most to blame, managers that don’t understand that software control is serious and complex.