Lack of Appreciation/Understanding for Developers

A couple months back a bunch of us had a cool thread going on feeling like your programming talent is underappreciated.  Basically, a few people mentioned that it seemed like the artist got all the praise for a good website design, but no one (but us) seem to be impressed over a fully functional database driven backend.

Part of the role of an application architect (as I see it) is to help the project manager avoid these types of moral killers.  The application architect is usually a senior developer who has seen it all, and can help the project manager avoid project killing mistakes.  I specialize in the middle and data tiers, and make no claims that I produce usable UIs.  If I want a project to get rave reviews, I try to make sure the PM has a budget that includes a graphic artist, otherwise I hire a programmer that can produce usable UIs.  Over the last couple years, I've worked very hard at improving my UI talent, but I know that I can only take it so far.  I've been blessed with the luck of working with some great graphic artists, that have taught me a lot, but I can never be as good as them (but they can never code like me either).

The other thing I try to remind the PM is that developers and not marketing types.  That's why it is always good to designate someone on the project as the lead Public Relations person.  Developers, in general, aren't typically the ones who are great at doing presentations for corporate management.  So you have 2 choices, hire someone how can do the PR work, and code a bit, or get a developer to work on their presentation skills.  A developer that can do "dog and pony" shows for management will typically go far in the corporation, even if they don't code very well.

I know of developers that have taken singing lessons, and acting classes, just to feel more comfortable doing presentations.  Your look also goes a long way to get respect.  You can't look too corporate, otherwise the corporate folks will never believe that you can code.  And you can't go too extreme on the geek look either, otherwise you'll frighten the stiffs.  A good mix is nice stylish clothes (but no tie), long hair (or no hair), and maybe some facial hair.  Check out the folks on VB TV or one of the other MSDN video series.

DonXML

3 Comments

  • some good points. many times it is the lead architects job to make sure that the PM has a data architect, a top-notch ui person, a lead designer, etc... to make sure that the project is successful. or have multi-talented people who can wear multiple hats.





    many times these different disciplines are underrepresented and the end-product shows. for example, a great architecture but it looks like crap or it looks great but it isn't really scaleable.





    just my thoughts and rants.


  • ahh - reading this makes me so happy I work for myself and don't have to deal with that stuff. Even Don Box finally gave in and cut his hair.

  • Had to go through that crap at my last job. Although, we did pretty well, because we both wore more than one hat. I still saw my share of excitement for the program only because it looked nice, but then again, our IT manager wasn't really an IT manager and new nothing of programming, so it was doomed from the start! :P

Comments have been disabled for this content.