Friday, March 24, 2006

Friday Bitch-Blogging

Writing Design Requirements Documents is like explaining how to tie your shoes to a particularly stupid child.

Over the phone.


Sluggo said...

yeah, dequirements documents are de bitch.

and they do require a certan amount of abilq.

Neddie said...

Yeah, Johnny Proofreader, that's me.

Mike said...

Writing software when the suits can't decide wtf they really want is like uhm....

Oh fuck it. It sucks. No matter what you give them, they'll want the opposite. This is true even when you do have a requirments doc, but at least then you can charge them extra for their stupidity.

Software development tip: Get the artwork done first thing, before you even write code. Good looking screenshots are far more important than good functionality. The only downside is that most of the time, the client won't understand what's taking so long to get the code done since you already showed them screenshots.

Not that I'm bitter about those wmkcrqm smoking morons.

Mike Kretzler said...

OK, now that it's Saturday and I've had my walk in the cool, sunny morning with the dog, I can say: I love collecting the requirements from the people who will use the product, as long as they care about what they're doing. It's my favorite part of the job. Writing that understanding down is hard -- that's why they call it work -- but coming to the understanding of what they do and what they need? Priceless.

The suits? Screw 'em.

XTCfan said...

Mike, I'm with you all the way. The part I hate is when Dev goes and builds it the way they want to anyway, and when you point to your Interaction Spec and ask why they didn't do it the way you'd told them, they say it's too late, we gotta hit this deadline, so change them specs to match what we built.

And that's why I'm trying to get away from software development.

The End.