Comments on: The Best Programmers Eat Their Applications

By: Austin Smith

Austin Smith — Fri, 28 Sep 2007 21:52:49 +0000

I feel like this post might be about me–know this–that after the document indexing feature hit, I’m actively using Wonderfile. In principle, I agree with you, but some applications (no examples needed) just don’t lend themselves to use by developers. Wonderfile isn’t one of those apps, it’s very useful for me now. You know that us coder types think about apps differently, we have more tolerance for odd behavior if it buys us some efficiency. Still, for the most part, you’re right. If nothing else, we’ll appreciate our own work more if we benefit from it.

By: Cory

Cory — Mon, 01 Oct 2007 18:43:27 +0000

we have more tolerance for odd behavior if it buys us some efficiency

I would suggest developers tolerate odd behavior because it often functionally works. Not that it works in the mental model most people might have, but it works in our little fiefdom.

Software is much, much better than it used to be. It still has a hella way to go though.

By: David Carnes

David Carnes — Mon, 01 Oct 2007 20:56:38 +0000

It’s a challenge to balance getting an app done within budget while spending the time required to reach a level of craftsmanship that makes the end-user experience painless and intuitive.

Programmers have to balance those two demands… how to code within budget while not requiring odd user behavior. It also demands a clearly communicated feature set from the client and an adequate budget to get the job done right.

Contrary to Austin’s comments - the post wasn’t directed at him - it’s just been a rant I’ve been on the last week or so.

There should be a formal, thorough, first pass test by the programmer tasked as the lead for a project, before the application is sent to QA.

By: ET

ET — Tue, 02 Oct 2007 23:10:46 +0000

I disagree with this.

Yes, programmers should be familiar with the apps they work on; yes, they should test them for usability while they’re working on them, and yes, they should absolutely ensure that the use experience is where it’s supposed to be.

However, what you’re talking about isn’t so much testing for functionality as it is evaluating usability: Programmers should not be expected to review design decisions during development any more than designers (on whose shoulders this responsibility does fall) should be expected to go over the final back-end code and suggest changes from an efficiency standpoint.

I think the solution to this problem is a good spec and a solid, -comprehensive-, well-reviewed, accepted design — all of which are things that should be present before any back-end code is written.

A painter shouldn’t have to worry about redesigning his easel while he’s working on his canvas, and you don’t ask a construction foreman to rethink the blueprints he’s given. There’s a separation of responsibility there that applies here as well: Designers are there to lay the groundwork for the application. Asking the artist to work on his easel will distract him and sap his creativity; asking the foreman to improve his skyscraper’s feng shui will result in delays at best and disasters at worst.

Again… I’m not saying programmers shouldn’t use their apps. I’m just saying that the improvement you get in the final product, if any, probably will not be significant, and your cost to benefit will almost certainly make you wonder what went wrong.

Separation of church and state, baby!