Responsibility cannot be assigned; it can only be accepted. If someone tries to give you responsibility, only you can decide if you are responsible or if you aren’t.
Without planning, we are individuals with haphazard connections and effectiveness. We are a team when we plan and work in harmony.
I’m not a great programmer; I’m just a good programmer with great habits.
I don’t like the feeling, but I’ve got to say that a little fear makes me a more focused, more responsible programmer.
I’ve known people who have not mastered their tools who are good programmers, but not a tool master who remained a mediocre programmer.
The business changes. The technology changes. The team changes. The team members change. The problem isn’t change, per se, because change is going to happen; the problem, rather, is the inability to cope with change when it comes.
A plan is an example of what could happen, not a prediction of what will happen.
Responsible Development is the style of development I aspire to now. It can be summarized by answering the question, How would I develop if it were my money? I’m amazed how many theoretical arguments evaporate when faced with this question.
I tell people to start implementing when they are pretty sure there aren’t more important stories out there. An iteration’s worth of data is worth months of speculation.
If testing costs more than not testing, then don’t test.