Oh yeah, that’s why we design before we code

Joel Spolsky has a new article out, and as usual it’s interesting and fun to read.  But one of the best parts for me was actually in a comment from a reader, who linked back to an old article of Joel’s from 2000.  That one was about writing actual specifications before coding actual software.  Sometimes I use the analogy that if you needed to build a house, you wouldn’t begin by delivering a pile of lumber and start hammering, right?  But that’s how some people build software, and Joel’s article points out why that doesn’t work.  It was a great reminder about why we follow our seven-step process in all our projects, in which Design always comes before Construction.

~Armen

Share this post

Related Articles

Man and woman shake hands at desk.

Can You Take Yes for an Answer?

Working with hundreds of potential clients over the years, I’ve learned that reaching an agreement requires both timing and confidence. When a conversation is going well, you must recognize it and lead the client to the next steps without over-explaining. Once the client says “yes”, it’s essential to take that answer and move forward rather than offer more reassurance when it isn’t needed. A specific example is references. Sure, we have a bunch of them – but we don’t offer them when the answer is already yes!

Read More »