Kent Beck

Kent Beck - Toolshero

Kent Beck (born in 1961) is an American software engineer and the developer of Extreme Programming (XP). Kent Beck is considered a pioneer of design patterns for software development.

The XP software development method is known as a counterpart to traditional software development methods, which are considered rigid and formal. Kent Beck is also one of the original signatories of the Agile Manifesto, a document outlining the then new method. Extreme Programming (XP) and Agile are strongly linked to Test Driven Development (TDD).

Kent Beck biography

Technology was introduced to Kent Beck during his upbringing. He was born in Silicon Valley to an electrical engineer and his grandfather was a radio fanatic. So it was not surprising that he would follow in similar technological footsteps.

Do you want unlimited and ad-free access?   

Kent Beck was a student at the University of Oregon between 1979 and 1987, earning bachelor’s and master’s degrees in computer and information sciences. In 1996, he began to work on the Chrysler Comprehensive Compensation System. During this time, he also introduced Ron Jeffries to the company.

XP was developed during a period when he advised Smalltalk projects in the 1980s and 1990s. Smalltalk is an object-oriented programming language. Smalltalk was founded to investigate how programming can best be taught to children.

The team estimated that it would take about a year for certain product elements to be completed. A year later they introduced a new way of working. This way of working is now known as Extreme Programming (XP).

Facebook

In 2011, Beck joined the company Facebook, today known as Meta. With decades of experience, he was convinced that he had an excellent understanding of the operation and application of software.

Still, he later had to realize that Facebook was unlike any company he’d worked for before and he needed to get serious about transforming his vision of software development.

He later said of the company Facebook that it is a very agile company, always ready for change. He mainly immersed himself in the codes on which Facebook is built and the culture.

Today, Kent Beck lives in San Francisco, California. In 2019, Beck joined the Gusto company as a software coach. Here he coaches technical teams in building payroll systems for smaller companies.

Kent Beck quotes

  1. “Agitator and the Agitar Management Dashboard lower the barriers to accountability in software development and increase the value of developer testing.”
  2. “Beta testing is a symptom of weak testing practices and poor communication with customers.”
  3. “Brilliance in a scientist does not consist in being right more often but in being wrong about more interesting topics.”
  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.”
  5. “Developer testing is an important step towards accountability. It gives developers a way to demonstrate the quality of the software they produce.”
  6. “Do The Simplest Thing That Could Possibly Work.”
  7. “Extreme programming is an emotional experience.”
  8. “First you learn the value of abstraction, then you learn the cost of abstraction, then you’re ready to engineer.”
  9. >“Given the choice between an extremely skilled loner and a competent-but-social programmer, XP teams consistently choose the more social candidate. The best interviewing technique is to have the candidate work with the team for a day. Pair programming provides an excellent test of technical and social skills.”
  10. “I found out that most programmers don’t like to test their software as intensely as I do.”
  11. “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.”
  12. “I think it’s a combination of technical and social factors that leads to all the defects in deployed software.”
  13. “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.”
  14. “If I’d had a charisma-ectomy in the beginning, XP would have gone nowhere.”
  15. “If you’re happy slamming some code together that more or less works and you’re happy never looking at the result again, TDD is not for you. TDD rests on a charmingly naïve geekoid assumption that if you write better code, you’ll be more successful. TDD helps you to pay attention to the right issu.es at the right time so you can make your designs cleaner, you can refine your designs as you learn.”
  16. “I’m not a great programmer; I’m just a good programmer with great habits.”
  17. “My great-grandfather played organ for silent movies. Talkies in, Gramps out.”
  18. “No matter the circumstance you can always improve. You can always start improving with yourself. You can always start improving today.”
  19. “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.”
  20. “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.”
  21. “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.”
  22. “Rather than apply minutes of suspect reasoning, we can just ask the computer by making the change and running the tests.”
  23. “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.”
  24. “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.”
  25. “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.”
  26. “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.”
  27. “The problem is, in software design, often the consequences of your decisions don’t become apparent for years.”
  28. “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.”
  29. “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?”
  30. “There are musicians who want to make a living making music. There are listeners who want to listen to music. Complicating this relationship is a whole bunch of history: some of the music I want to listen to was made a while ago in a different economy. Some of the models of making a living making music are no longer valid but persist.”
  31. “There is a strong movement towards increased accountability for software developers and software development organizations.”
  32. “There’s a huge latent market for software development that’s just flat-out honest.”
  33. “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.”
  34. “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.”
  35. “Whether you draw diagrams that generate code or you type at a browser, you are coding.”
  36. “Without planning, we are individuals with haphazard connections and effectiveness. We are a team when we plan and work in harmony.”
  37. “Write tests until fear is transformed into boredom.”

Get Toolshero updates on new methods, models and theories!  

Publications and Books

  • 2008. Implementation Patterns. Addison-Wesley.
  • 2004. JUnit Pocket Guide. O’Reilly.
  • 2004. Extreme Programming Explained: Embrace Change, 2nd Edition. With Cynthia Andres. Addison-Wesley.
  • 2003. Contributing to Eclipse: Principles, Patterns, and Plugins. With Erich Gamma. Addison-Wesley.
  • 2002. Test-Driven Development by Example. Addison-Wesley.
  • 2000. Planning Extreme Programming. With Martin Fowler. Addison-Wesley.
  • 2000. Extreme Programming Explained: Embrace Change. Addison-Wesley. Winner of the Jolt Productivity Award.
  • 1997. Smalltalk Best Practice Patterns. Prentice Hall.
  • 1996. Kent Beck’s Guide to Better Smalltalk : A Sorted Collection. Cambridge University Press.
  • 1989. Simple Smalltalk Testing: With Patterns. SUnit framework, origin of xUnit frameworks.
  • 1989. A Laboratory For Teaching Object-Oriented Thinking. With Ward Cunningham. OOPSLA’89.
  • 1987. Using Pattern Languages for Object-Oriented Programs. With Ward Cunningham. OOPSLA’87.

How to cite this article:
Janse, B. (2022). Kent Beck. Retrieved [insert date] from Toolshero: https://www.toolshero.com/toolsheroes/kent-beck/

Published on: 09/01/2022 | Last update: 09/01/2022

Add a link to this page on your website:
<a href=” https://www.toolshero.com/toolsheroes/kent-beck/”>Toolshero: Kent Beck </a>

Did you find this article interesting?

Your rating is more than welcome or share this article via Social media!

Average rating 4 / 5. Vote count: 4

No votes so far! Be the first to rate this post.

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Tagged:

Leave a Reply