Amitai Schleier
@schmonz@schmonz.com
If the only bits of #ExtremeProgramming you’ve mastered are the technical ones, you’re not an XP expert. Especially if you’re sure you are.
@schmonz No, it’s a post of yours referencing a specific article (something about XP that wasn’t)
@schmonz The only code I'm ever satisfied with (with very rare exceptions) is my own, and that is exactly why I'm not qualified for "technical leadership" and have always avoided climbing the management ladder. I want no other responsibilities than technical ones and that's where I'm at my best.
Unfortunately, society in general does not value that.
I appreciate the reminder to consider systemic factors that push people to make such choices. The systemic factors suck. But also people who make any part of others' lives miserable suck.
@schmonz I understand the goal and targeted audience of your toot, don't worry. I just wanted to provide you with my slightly different perspective 😉
@schmonz I am almost never satisfied with neither "my", nor "others'" code. That's why I insist on the code to be maintained relentlessly (TDD, refactoring and CI above all) and that's what I expect from others. Because currently most of the others act as if the code they write is perfect (the write once mentality and the notion that the code can be "done" which it never is).
Lastly, there should be no such thing as my and your code.
Some years after learning TDD, I had a coding interview. TDD was not widely known. I delivered TDD code.
They said it was the best code they had ever seen.
A few years later, I decided to pull up my submission and take a look at it.
I was *seriously embarrassed* that I would have submitted this code for a job application. It would need a fair number of changes before I would consider it *minimally acceptable.*
I like to think I've continued with improvement.