Essential web developer skills
In the next few months we’re going to be gearing up to fill two posts (one replacement and one new post) to join the web team: a developer and an apprentice. So I’ve been thinking about a couple of things:
- What skills we are looking for in new team members?
- What skills do we already have that we’re maybe not using to their best potential within the team, or which have become a little sloppy and undisciplined that we need to work on.
I liked this comment in an article by Dan Frost on .net; it is point 6:
That search for ‘essential web developer skills’ brings a nice answer from Michael Greer (The Onion’s CTO) on Quora:
- Refuses to do anything twice: writes a script or algo[rithim] for it.
- Thinks to test, worries over load and code impact.
- Tries new stuff constantly, launches same-day ideas.
Cowardice is a nice way of phrasing ‘attention to detail’.
I remember a conversation years ago with an architect who said that he valued lazy people, because they showed him how to do things with the least amount of effort. It was from him that I also learned about cowpaths (“look where the paths are already being formed by behaviour and then formalize them”).
I like how Greer put it: refuse to do anything twice. Don’t repeat yourself; the DRY principle. Use frameworks, save snippets of code that you use often (my coding editor allows me to collect code snippets in an in-built library), don’t reinvent the wheel again and again.