I was trying to post a comment to an article about reaching out to amateur web developers, but technology let me down, so I post the comment here until I can access to comments there.
I am trying hard not to be amateur, and have definitely been "reached". I am a programmer, and in my last job I took care of the companies web application, from front to back. As a programmer I expect things to compile and run without errors, so why would I want my web site to be different? The first problem I had was the tools, I was coding in notebook and viewing in IE, so how do I know where errors are, our even if they exist? Now because I'm a good boy, I read around and found I Zeldman, he made me smile and he showed me that my web site could run without errors, and what the errors were. The problem I then had was moving the site to full standards, convincing my colleagues that they should follow my lead, and convincing the boss that moving things around the screen, pixel by pixel, was not the way to go. So I kept plugging away, signing up to feeds from sites like this, and learning and trying, whilst pushing and pulling everyone else. Now I've moved on to another company, and I'm just a programmer again, but I'm still here, learning and trying.
So what did I learn, what should you say to "reach" others? Firstly, programmers don't want errors, so show them how to detect errors, how error-free is easier to maintain. I had a big win when rebranding was required, CSS is the tool, show them the CSS Zen garden, they will pass out! Give them the information resources, this site is a good place to start. Finally, concentrate on delivery, standards are easier and quicker with less errors and less problems, then the rest should follow.
No comments :
Post a Comment