Clients hire web developers (or their firms) because we are the experts. When I call someone in to fix my air conditioner I don’t let them work for awhile and then tell them they are doing their job wrong and I know the problem is the compressor. They are the expert, not me. When a client tells me the layout is unusable, the typography is wrong, the form isn’t styled properly, or [insert common client complaint here] I simply want to say – “Why don’t you do it?”.

» 5 Reasons it Sucks to be a Web Developer | Get A New Browser

I came across this post today (via wayne-sutton.com, an area blogger). The point above (#4) really hit home, and yet I have conflicting views on it. Primarily, the comparison to an AC repairman, while not necessarily wrong, is limiting. In some cases, when doing web dev work, you’re mostly working on mechanical stuff, and the comparison is apt.

However, when doing other work – the front-facing stuff, that’s generally when clients will throw in more feedback. At that point, the AC repairman analogy breaks down. You’re now more analogous to an architect, or interior designer, or maybe even just a cleaner. The input – “change these colors, move this around, etc.” is valid. They’re telling you how to do your job because that’s what they’re paying you to do.

I’ve had very few clients debate the finer points of natural vs artificial primary keys. I’ve had plenty chime in with ideas about the functionality they’d like to have, either backend or frontend.

I’m going to tag this as ‘refreshthetriangle’ and perhaps our local Refresh group (“Refresh the Triangle!”) may throw their 2 cents in…

Blogged with Flock

Tags: refreshthetriangle, webdev, clients