Kent Beck

Kent Beck. He is one of the creators of the Agile Methodology for software development known as extreme programming . He also created, together with Erich Gamma, the unit testing framework for Java , JUnit .

Summary

[ hide ]

  • 1 Bibliography
    • 1 Reflections
    • 2 Main guidelines
      • 2.1 Values
    • 3 Communication
    • 4 Simplicity
    • 5 Feedback
    • 6 Courage
    • 7 Respect
    • 8 Others
    • 9 Kent Beck’s 4 rules for writing simple code
    • 10 See also
  • 2 Sources

Bibliography

  • Smalltalk Best Practice Patterns (ISBN 0-13-476904-X)
  • An Explanation of Extreme Programming: Embrace Change (ISBN 84-7829-055-9)
  • Test-Driven Development: By Example (ISBN 0-321-14653-0)
  • Planning Extreme Programming (ISBN 0-201-71091-9), with Martin Fowler

Reflections

“The problem (of software development projects ) is not change because change is going to happen; rather, the problem is the inability to cope with change when it occurs ”.

There, there is one of the great problems of software development projects and it is the fact of not focusing from the point of view that the initial specifications are going to change, either because the user has not adequately transferred what he wants, because the project team has not correctly interpreted what has been asked or because the requirements and / or priorities have changed.

It is not realistic to face a project in this way and yet it is the order of the day to find developments that do not have maintenance planned and that is a mistake both applying agile methodologies and, above all, applying classic methodologies .

The software has to be developed thinking about what is going to change and the means made available to the information system (or the set of information systems of an organization) must be able to respond to when these changes occur, which sometimes we will not know when, but we do know what will happen.

Main guidelines

Values

They are universal concepts, ideally they apply in all areas. It is the way to put purpose into practice.

Communication

It is an important factor in creating a sense of team and achieving effective cooperation. When surprise problems arise, you can help solve them. Most of the problems are caused by lack of knowledge or lack of communication.

If the problem originates from a lack of knowledge, there is nothing that can be done beforehand. When we encounter a problem, let us ask ourselves if it can be caused by a lack of communication. If so, it should be analyzed:

  • What kind of communication do we need to address the problem?
  • What communication do we need to stay out of this situation in the future?

Simplicity

It is the most intensely intellectual value. It’s about thinking things through in a way that eliminates all unnecessary complexity.

Feedback

Changes are inevitable and create the need for Feedback . Personally I understand that the scenario in which the situation conditions us to implement functionality imperfectly in one or more aspects is common. This situation creates a strong need for Feedback , otherwise the risk of perpetuating this imperfection is assumed and perhaps no one will remember its existence.

There are basically three reasons that make it difficult to do things right the first time:

  • When solving a problem for the first time, there may be more than one solution that works or the solution may not be entirely clear.
  • What is good today may not be good tomorrow.
  • Doing something absolutely right could take so long that future changing circumstances will invalidate today’s solution before it is finalized.

Achieving satisfaction in an improvement scheme in exchange for, expecting perfection instantly, is possible only by going to Feedback , which can be produced in several ways:

  • Listen to different opinions about an idea.
  • What the code looks like once the idea is implemented,
  • If the tests were easy to write,
  • If the tests ran,
  • How the idea works once the deploy is done .

A team should strive to generate as much Feedback as possible, as quickly as possible. As soon as the situation is known, as soon as we can adapt.

Courage

It is the effective action of facing fear.

Sometimes courage manifests itself in the form of patience. When you know there is a problem but don’t know about it, it takes courage to expect it to manifest distinctively. It must be borne in mind that courage as the main value, without counterbalanced values, can be dangerous, it can even play against the spirit of the team. But when courage plays in confluence with other values, it is a powerful tool.

Respect

This is the value that underlies the other four. XP works in a framework where each member of the team considers each other and what they are doing. Each person’s contribution needs respect.

Others

  • Quality of life.

Kent Beck’s 4 Rules for Writing Simple Code

  • Be well covered and satisfy the assertions of a good battery of unit tests .
  • Express the ideas that we as programmers want to express self-documenting code .
  • Say each thing only once.
  • Avoid having superfluous parts: it must be simple and meet current needs, without thinking about what may happen in the future; and have the minimum number of classes and methods taking into account the Single Responsibility Principle .

 

Leave a Comment

Scroll to Top