Archive for March, 2008

How many things must a developer do, before you call him senior?

March 24th, 2008

The anwer is, 10. Exactly.

  1. Write code to get things done
  2. Solve any task without any prior training whatsoever
  3. Know more than one programming language/IDE/operating system, at heart
  4. Debug, maintain and fix code somebody else wrote
  5. Extend functionality to code somebody else wrote before you, and whom you don’t know
  6. Write code that others think helps them to get things done easier
  7. Specify what others have to implement
  8. Understand what your clients need, in their terms
  9. Manage a continuous build & release process/system over more than one release
  10. Design systems that get used by someone else but yourself or your team