Breaking out of legacy with 3P

Me ha llamado la atención esta receta 3P de Johan Martinsson. A la hora de iniciar el trabajo en una historia de usuario o tarea:

  • Empezaremos protegiendo el comportamiento existente con los tests que sean necesarios (Protect).
  • Luego refactorizaremos para que la nueva funcionalidad se pueda introducir fácilmente (Prepare)
  • Cuando tenemos esto, desarrollamos la nueva funcionalidad con TDD (Produce):

This is where the idea of the 3Ps comes in, where we not only bring the investment closer to the benefit, but also we are the foremost beneficiaries of the tests just wrote and the refactoring we just did! This has the added benefit that any ill-conceived tests and refactoring are immediately brought to the attention of just the right person to fix the issue.

The idea is simple, for each story break down the work into:

  • Protect
  • Prepare
  • Produce

Breaking out of legacy with 3P

January 21, 2024

Etiquetas: tb-list   refactoring  

Temas

good-practices

refactoring

php

testing

tdd

python

blogtober19

design-principles

design-patterns

bdd

misc

tb-list

legacy

golang

dungeon

ruby

tools

tips

hexagonal

ddd

bbdd

soft-skills

books

oop

javascript

api

sql

ethics

typescript

swift

java

agile