Test-Driven Development|Kent Beck 0321146530

||boek: Test-Driven Development|By example|Addison-Wesley

||door: Kent Beck

||taal: en
||jaar: 2006
||druk: 10th print
||pag.: 220p
||opm.: paperback|like new

||isbn: 0-321-14653-0
||code: 1:001762

--- Over het boek (foto 1): Test-Driven Development ---

Clean code that works--now. This is the seeming contradiction that lies behind much of the pain of programming. Test-driven development replies to this contradiction with a paradox--test the program before you write it.

A new idea? Not at all. Since the dawn of computing, programmers have been specifying the inputs and outputs before programming precisely. Test-driven development takes this age-old idea, mixes it with modern languages and programming environments, and cooks up a tasty stew guaranteed to satisfy your appetite for clean code that works - now.

Developers face complex programming challenges every day, yet they are not always readily prepared to determine the best solution. More often than not, such difficult projects generate a great deal of stress and bad code. To garner the strength and courage needed to surmount seemingly Herculean tasks, programmers should look to test-driven development (TDD), a proven set of techniques that encourage simple designs and test suites that inspire confidence.

By driving development with automated tests and then eliminating duplication, any developer can write reliable, bug-free code no matter what its level of complexity. Moreover, TDD encourages programmers to learn quickly, communicate more clearly, and seek out constructive feedback.

Readers will learn to:

• Solve complicated tasks, beginning with the simple and proceeding to the more complex.
• Write automated tests before coding.
• Grow a design organically by refactoring to add design decisions one at a time.
• Create tests for more complicated logic, including reflection and exceptions.
• Use patterns to decide what tests to write.
• Create tests using xUnit, the architecture at the heart of many programmer-oriented testing tools.

This book follows two TDD projects from start to finish, illustrating techniques programmers can use to easily and dramatically increase the quality of their work. The examples are followed by references to the featured TDD patterns and refactorings. With its emphasis on agile methods and fast development strategies, Test-Driven Development is sure to inspire readers to embrace these under-utilized but powerful techniques.

[source: bookcover]

Quite simply, test-driven development is meant to eliminate fear in application development. While some fear is healthy (often viewed as a conscience that tells programmers to "be careful!"), the author believes that byproducts of fear include tentative, grumpy, and uncommunicative programmers who are unable to absorb constructive criticism. When programming teams buy into TDD, they immediately see positive results. They eliminate the fear involved in their jobs, and are better equipped to tackle the difficult challenges that face them. TDD eliminates tentative traits, it teaches programmers to communicate, and it encourages team members to seek out criticism However, even the author admits that grumpiness must be worked out individually! In short, the premise behind TDD is that code should be continually tested and refactored. Kent Beck teaches programmers by example, so they can painlessly and dramatically increase the quality of their work.

[source: https--www.amazon.com]

--- Over (foto 2): Kent Beck ---

Kent Beck consistently challenges software engineering dogma, promoting ideas like patterns, test-driven development, and Extreme Programming. Currently affiliated with Three Rivers Institute and Agitar Software, he is the author of many Addison-Wesley titles.

[source: https--www.amazon.com]

Kent Beck (born 1961) is an American software engineer and the creator of extreme programming, a software development methodology that eschews rigid formal specification for a collaborative and iterative design process. Beck was one of the 17 original signatories of the Agile Manifesto, the founding document for agile software development. Extreme and Agile methods are closely associated with Test-Driven Development (TDD), of which Beck is perhaps the leading proponent.

Beck pioneered software design patterns, as well as the commercial application of Smalltalk. He wrote the SUnit unit testing framework for Smalltalk, which spawned the xUnit series of frameworks, notably JUnit for Java, which Beck wrote with Erich Gamma. Beck popularized CRC cards with Ward Cunningham, the inventor of the wiki.

He lives in San Francisco, California and worked at social media company Facebook. In 2019, Beck joined Gusto as a software fellow and coach, where he coaches engineering teams as they build out payroll systems for small businesses.

Beck attended the University of Oregon between 1979 and 1987, receiving B.S. and M.S. degrees in computer and information science.

In 1996 Beck was hired to work on the Chrysler Comprehensive Compensation System. Beck in turn brought in Ron Jeffries. In March 1996 the development team estimated the system would be ready to go into production around one year later. In 1997 the development team adopted a way of working which is now formalized as extreme programming. The one-year delivery target was nearly achieved, with actual delivery being only a couple of months late.

Publications

Books

1996 Kent Beck's Guide to Better Smalltalk : A Sorted Collection. Cambridge University Press. (ISBN 978-0521644372)
1997 Smalltalk Best Practice Patterns. Prentice Hall. (ISBN 978-0134769042)
2000 Extreme Programming Explained: Embrace Change. Addison-Wesley. Winner of the Jolt Productivity Award. (ISBN 978-0321278654)
2000 Planning Extreme Programming. With Martin Fowler. Addison-Wesley. (ISBN 978-0201710915)
2002 Test-Driven Development by Example. Addison-Wesley. Winner of the Jolt Productivity Award. (ISBN 978-0321146533)

Beck's concept of test-driven development centers on two basic rules:

• Never write a single line of code unless you have a failing automated test.
• Eliminate duplication.

The book illustrates the use of unit testing as part of the methodology, including examples in Java and Python. One section includes using test-driven development to develop a unit testing framework.

2003 Contributing to Eclipse: Principles, Patterns, and Plugins. With Erich Gamma. Addison-Wesley. (ISBN 978-0321205759)
2004 JUnit Pocket Guide. O'Reilly. (ISBN 978-0596007430)
2004 Extreme Programming Explained: Embrace Change, 2nd Edition. With Cynthia Andres. Addison-Wesley. Completely rewritten. (ISBN 978-0201616415)
2008 Implementation Patterns. Addison-Wesley. (ISBN 978-0321413093)

Selected papers

1987 "Using Pattern Languages for Object-Oriented Programs". With Ward Cunningham. OOPSLA'87.
1989 "A Laboratory For Teaching Object-Oriented Thinking". With Ward Cunningham. OOPSLA'89.
1989 "Simple Smalltalk Testing: With Patterns". SUnit framework, origin of xUnit frameworks.

[source: wikipedia]

Kent Beck is an American software engineer and the creator of extreme programming, a software development methodology that eschews rigid formal specification for a collaborative and iterative design process. Beck was one of the 17 original signatories of the Agile Manifesto, the founding document for agile software development. Extreme and Agile methods are closely associated with Test-Driven Development (TDD), of which Beck is perhaps the leading proponent.

Beck pioneered software design patterns, as well as the commercial application of Smalltalk. He wrote the SUnit unit testing framework for Smalltalk, which spawned the xUnit series of frameworks, notably JUnit for Java, which Beck wrote with Erich Gamma. Beck popularized CRC cards with Ward Cunningham, the inventor of the wiki.

He lives in San Francisco, California and worked at social media company Facebook. In 2019, Beck joined Gusto as a software fellow and coach, where he coaches engineering teams as they build out payroll systems for small businesses.

Beck attended the University of Oregon between 1979 and 1987, receiving B.S. and M.S. degrees in computer and information science.

In 1996 Beck was hired to work on the Chrysler Comprehensive Compensation System. Beck in turn brought in Ron Jeffries. In March 1996 the development team estimated the system would be ready to go into production around one year later. In 1997 the development team adopted a way of working which is now formalized as extreme programming. The one-year delivery target was nearly achieved, with actual delivery being only a couple of months late.

[source: https--londonspeakerbureau.com/speaker-profile/kent-beck]

[2022-09-20]

Kent Beck (geboren in 1961) is een Amerikaanse software-engineer en de ontwikkelaar van Extreme Programming (XP). Kent Beck geldt als een pionier op het gebied van ontwerppatronen voor softwareontwikkeling.

De Extreme Programming (XP) methode voor softwareontwikkeling staat bekend als tegenhanger van traditionele methoden voor softwareontwikkeling, die als rigide en formeel worden beschouwd. Kent Beck is daarnaast een van de oorspronkelijke ondertekenaars van het Agile Manifesto, een document waarin de toenmalige nieuwe methode uiteen werd gezet. Extreme Programming (XP) en Agile zijn sterk verbonden met Test Driven Development (TDD).

Kent Beck biografie

Technologie werd Kent Beck met de paplepel ingegoten tijdens zijn opvoeding. Hij werd geboren in Silicon Valley als zoon van een elektrotechnicus en zijn grootvader was een radiofanaat. Het was dus niet vreemd dat hij in vergelijkbare technologische voetsporen zou treden.

Kent Beck was tussen 1979 en 1987 student aan de Universiteit van Oregon en behaalde daar een Bachelor- en Mastergraad in computer- en informatiewetenschappen. In 1996 begon hij te werken aan het Chrysler Comprehensive Compensation System. Gedurende deze periode introduceerde hij ook Ron Jeffries in het bedrijf.

Extreme Programming (XP) werd ontwikkeld tijdens een periode waarin hij advies gaf aan Smalltalk-projecten in de jaren 80 en 90. Smalltalk is een objectgeoriënteerde programmeertaal. Smalltalk werd opgericht om te onderzoeken hoe programmeren het beste geleerd kan worden aan kinderen.

Het team schatte in dat het ongeveer een jaar nodig zou hebben voordat bepaalde productelementen voltooid zouden zijn. Een jaar later introduceerden zij een nieuwe manier van werken. Deze manier van werken staat nu bekend als Extreme Programming (XP).

Facebook

In 2011 trad Beck toe tot het bedrijf Facebook, tegenwoordig bekend als Meta. Met een decennia aan ervaring was hij ervan overtuigd dat hij de werking en toepassing van software uitstekend begrijpt.
Wil je onbeperkte en advertentievrije toegang?

Toch moest hij zich later realiseren dat Facebook anders was dan elk bedrijf waarvoor hij eerder had gewerkt en dat hij serieus aan de slag moest om zijn visie op softwareontwikkeling te transformeren.

Hij zei later over het bedrijf Facebook dat het een zeer agile bedrijf is, dat altijd klaar is voor verandering. Hij verdiepte zich vooral in de codes waarop Facebook gebouwd is en de cultuur.

Tegenwoordig woont Kent Beck in San Francisco, Californië. In 2019 trad Beck in dienst bij het bedrijf Gusto als softwarecoach. Hier coacht hij technische teams bij het bouwen van salarissystemen voor kleinere bedrijven.

Kent Beck quotes

• "Agitator and the Agitar Management Dashboard lower the barriers to accountability in software development and increase the value of developer testing."
• "Beta testing is a symptom of weak testing practices and poor communication with customers."
• "Brilliance in a scientist does not consist in being right more often but in being wrong about more interesting topics."
• "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."
• "Developer testing is an important step towards accountability. It gives developers a way to demonstrate the quality of the software they produce."
• "Do The Simplest Thing That Could Possibly Work."
• "Extreme programming is an emotional experience."
• "First you learn the value of abstraction, then you learn the cost of abstraction, then you're ready to engineer."
• "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."
• "I found out that most programmers don't like to test their software as intensely as I do."
• "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."
• "I think it's a combination of technical and social factors that leads to all the defects in deployed software."
• "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."
• "If I'd had a charisma-ectomy in the beginning, XP would have gone nowhere."
• "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."
• "I'm not a great programmer; I'm just a good programmer with great habits."
• "My great-grandfather played organ for silent movies. Talkies in, Gramps out."
• "No matter the circumstance you can always improve. You can always start improving with yourself. You can always start improving today."
• "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."
• "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."
• "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."
• "Rather than apply minutes of suspect reasoning, we can just ask the computer by making the change and running the tests."
• "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."
• "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."
• "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."
• "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."
• "The problem is, in software design, often the consequences of your decisions don't become apparent for years."
• "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."
• "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?"
• "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."
• "There is a strong movement towards increased accountability for software developers and software development organizations."
• "There's a huge latent market for software development that's just flat-out honest."
• "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."
• "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."
• "Whether you draw diagrams that generate code or you type at a browser, you are coding."
• "Without planning, we are individuals with haphazard connections and effectiveness. We are a team when we plan and work in harmony."
• "Write tests until fear is transformed into boredom."

Boeken en publicaties

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.

Citatie voor dit artikel:

• Janse, B. (2022). Kent Beck. Retrieved [insert date] from Toolshero: https--www.toolshero.nl/bekende-auteurs/kent-beck/

[bron: https--www.toolshero.nl/bekende-auteurs/kent-beck]