Kent Beck Quotes

#1. 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.

Kent Beck

#2. The world is changing, and I believe that, if I want to stay employed as a programmer, I'm going to have to change with it.

Kent Beck

#3. Sheet music, recording, radio, television, cassettes, CD burners, and file sharing have all invalidated, to some extent, the old model of making a living making music.

Kent Beck

#4. Design should be easy in the sense that every step should be obviously and clearly identifiable. Simplify elements to make change simple so you can manage the technical risk.

Kent Beck

#5. Testing is not the point. The point is about responsibility.

Kent Beck

#6. The marketing of XP is very deliberate and conscious. Part of it is in co-opting the power of the media; I make sure I'm newsworthy from time to time. Part is in co-opting some of my publisher's ad budget.

Kent Beck

#7. My great-grandfather played organ for silent movies. Talkies in, Gramps out.

Kent Beck

#8. Sometimes the problem has to mature before the solution can mature.

Kent Beck

#9. There's a huge latent market for software development that's just flat-out honest.

Kent Beck

#10. I've known people who have not mastered their tools who are good programmers, but not a tool master who remained a mediocre programmer.

Kent Beck

#11. Agitator and the Agitar Management Dashboard lower the barriers to accountability in software development and increase the value of developer testing.

Kent Beck

#12. Developer testing is an important step towards accountability. It gives developers a way to demonstrate the quality of the software they produce.

Kent Beck

#13. If I'd had a charisma-ectomy in the beginning, XP would have gone nowhere.

Kent Beck

#14. Optimism is an occupational hazard of programming; feedback is the treatment.

Kent Beck

#15. The system metaphor is a story that everyone
customers, programmers, and managers
can tell about how the system works.

Kent Beck

#16. If there are forms of testing, like stress and load testing, that find defects after development is "complete," bring them into the development cycle. Run load and stress tests continuously and automatically.

Kent Beck

#17. Folk wisdom in software development teaches that interfaces shouldn't be unduly influenced by implementations. Writing a test first is a concrete way to achieve this separation.

Kent Beck

#18. I lived near Santa Cruz for ten years, and the whole time, it bothered me what an exclusionary definition of 'inclusion' was in force. Social censure was applied to those who expressed unpopular or uncomfortable ideas.

Kent Beck

#19. I found out that most programmers don't like to test their software as intensely as I do.

Kent Beck

#20. The community isn't nearly as afraid as it thinks it is.

Kent Beck

#21. Saying that programmers should just accomplish twice as much doesn't work. They can gain skills and effectiveness, but they cannot get more done on demand. More time at the desk does not equal increased productivity for creative work.

Kent Beck

#22. However, most defects end up costing more than it would have cost to prevent them. Defects are expensive when they occur, both the direct costs of fixing the defects and the indirect costs because of damaged relationships, lost business, and lost development time.

Kent Beck

#23. I'm not a great programmer; I'm just a good programmer with great habits.

Kent Beck

#24. I don't like the feeling, but I've got to say that a little fear makes me a more focused, more responsible programmer.

Kent Beck

#25. Learning research tells us that the time lag from experiment to feedback is critical ...

Kent Beck

#26. How good the design is doesn't matter near as much as whether the design is getting better or worse. If it is getting better, day by day, I can live with it forever. If it is getting worse, I will die.

Kent Beck

#27. Beta testing is a symptom of weak testing practices and poor communication with customers.

Kent Beck

#28. One of the advantages of having to live with JUnit for 8 years is now we can look back and see which decisions we made worked nicely and which we would have done differently.

Kent Beck

#29. Without planning, we are individuals with haphazard connections and effectiveness. We are a team when we plan and work in harmony.

Kent Beck

#30. The problem is, in software design, often the consequences of your decisions don't become apparent for years.

Kent Beck

#31. There is a strong movement towards increased accountability for software developers and software development organizations.

Kent Beck

#32. Of the four project development variables - scope, cost, time and quality - quality isn't really a free variable. The only possible values are "excellent" and "insanely excellent", depending on whether lives are at stake.

Kent Beck

#33. People are looking for software development that actually does something useful ... People are looking for partners who deliver when promised, and at a reasonable and transparent price. I believe that the days of being able to value price software are numbered.

Kent Beck

#34. 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.

Kent Beck

#35. I think it's a combination of technical and social factors that leads to all the defects in deployed software.

Kent Beck

#36. A plan is an example of what could happen, not a prediction of what will happen.

Kent Beck

#37. Brilliance in a scientist does not consist in being right more often but in being wrong about more interesting topics.

Kent Beck

#38. 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.

Kent Beck

#39. Extreme programming is an emotional experience.

Kent Beck

#40. Without the adjustment, you are working under a lie. Everyone knows it and has to hide to protect themselves. This is no way to get good software done and deployed;

Kent Beck

#41. I used Agitator on some code I had unit-tested, and it made me a better tester. As an Agitar Fellow, I look forward to the leverage of working with an outstanding organization as together we continue to improve the value of developer testing.

Kent Beck

#42. A rational model of software is to design it quickly - the economic pressure to improvise presents an interesting challenge.

Kent Beck

#43. Organizations want small changes in functionality on a more regular basis. An organization like Flickr deploys a new version of its software every half hour. This is a cycle that feeds on itself.

Kent Beck

#44. Listening, Testing, Coding, Designing. That's all there is to software. Anyone who tells you different is selling something.

Kent Beck

#45. Used Pluggable Adaptor, which we promise not to use again for four months, minimum, because it makes code hard to statically analyze.

Kent Beck

#46. We could talk, act, and dress funny. We were excused for socially inappropriate behavior: 'Oh, he's a programmer'. It was all because we knew this technology stuff that other people found completely mystifying.

Kent Beck

#47. When Pandora doesn't pay, and bars don't pay, and weddings don't pay, and nobody buys CDs or shirts or concert tickets or lessons, then the musician can't make a living making music.

Kent Beck

#48. First you learn the value of abstraction, then you learn the cost of abstraction, then you're ready to engineer.

Kent Beck

#49. If you're having trouble succeeding, fail.

Kent Beck

#50. the XP strategy is "design always.

Kent Beck

#51. Cards on a wall is a way of practicing transparency, valuing and respecting the input of each team member. The project manager has the task of translating the cards into whatever format is expected by the rest of the organization.

Kent Beck

#52. The XP philosophy is to start where you are now and move towards the ideal. From where you are now, could you improve a little bit?

Kent Beck

#53. Received wisdom is that if you spend time up front getting the design right, you avoid costs later. But the longer you spend getting the design right, the more your upfront costs are, and the longer it takes for the software to start earning.

Kent Beck

#54. If testing costs more than not testing, then don't test.

Kent Beck

#55. Make it work, make it right, make it fast.

Kent Beck

#56. 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.

Kent Beck