Archive for March, 2008
How many things must a developer do, before you call him senior?
March 24th, 2008The anwer is, 10. Exactly.
- Write code to get things done
- Solve any task without any prior training whatsoever
- Know more than one programming language/IDE/operating system, at heart
- Debug, maintain and fix code somebody else wrote
- Extend functionality to code somebody else wrote before you, and whom you don’t know
- Write code that others think helps them to get things done easier
- Specify what others have to implement
- Understand what your clients need, in their terms
- Manage a continuous build & release process/system over more than one release
- Design systems that get used by someone else but yourself or your team