Developer growth

The importance of time off

Burnout is a difficult topic that people experience in varying degrees throughout their professional and personal lives. Demands from our modern societies take their toll through ever-growing expectations from others, ourselves and what we believe others expect from us. There is a great deal of focus on how we can do more, but not on how to do less. Which is why I was positively surprised about a recent article from HBR which promoted the value of down-time.

Continue Reading

Developer growth

There is no time for empathy
After my post on empathy as an essential skill, a commenter said that the most successful developers don’t need empathy, referring to John Carmack & Linus Torvalds. Not sure about John Carmack, but Linus certainly has had a brush or two with his lack of empathy when communicating with people. There is nothing to suggest that he lacks empathy, just that he on occasions doesn’t utilize it to its fullest. But this isn’t about how a man in the open-source community goes about his business…

Continue Reading

Developer growth

Reflections on “The Ten Commandments of Egoless Programming”

I stumbled over The Ten Commandments of Egoless Programming which supposedly hail from the book The Psychology of Computer Programming, and found them fascinating. I haven’t read the book but loved the idea so much that I thought I’d attempt to write down some of my thoughts. As an experiment I’ve taken the “commandments” and written my interpretations. These may or may not align with the original authors interpretation.

The Ten Commandments of Egoless Programming

  1. Understand and accept that you will make mistakes.
  2. You are not your code.
  3. No matter how much “karate” you know, someone else will always know more.
  4. Don’t re-write code without consultation.
  5. Treat people who know less than you with respect, deference, and patience.
  6. The only constant in the world is change.
  7. The only true authority stems from knowledge, not position.
  8. Fight for what you believe, but gracefully accept defeat.
  9. Don’t be the “coder int he corner”.
  10. Critique code instead of people – be kind to the coder, not the code.

Continue Reading