You will never refactor or write tests until you have convinced yourself that it’s the most productive strategy. Once you accept that, you won’t need management to give you time because you will be working the fastest way possible.
Refactoring _saves_ time. Tests _save_ time.
A team who allows messes to persist in their code will gradually slow down to a tiny fraction of their potential productivity. I’ve seen teams that have expanded their estimates out to weeks and months for jobs that ought to take a day or two.
The slower the team goes, the more the pressure builds. The more the pressure build the more messes are left uncleaned. Each such mess impedes the team even more; and the slower they all go. It’s a vicious cycle, and if you’ve been a programmer for more than a couple of years you’ve likely taken a few turns around it.
But it gets worse. Managers, desperate to increase productivity, hire new people. This, of course, has the opposite of the desired effect. The new people, thrown into the mass of messy code, see how things are done around here and — of course — they emulate it. So now there are even more people making messes, which drives the cycle even faster, and drags the productivity even lower.
Qué fue antes: el huevo o la gallina?
Los devs no quieren hacer una linea de código hasta que esté todo bien definido.
Pero qué incentiva que se pida estimar todo por horas para luego estar dando con el látigo y el reporting casi a diario?
The best teams I've ever worked on were not made of 10x developers who knew everything but of developers who were kind, funny, humble, and professional.
@codurance_ES Citando a Ward Cunningham: "You know you are working on clean code when each routine you read turns out to be pretty much what you expected"
@metrodesantiago hice carga en totem metro Trinidad por 5 mil con tarjeta débito y el saldo no se actualizó. Martes 2 Abril 2024. Y el cargo a la tarjeta se hizo correctamente. Ayuda
Vivimos una especie de Edad Oscura donde prácticas como testing, clean code, integración continua (tbd), tdd o patrones de diseño, son criticadas y rechazadas desde el desconocimiento y cierto temor, en lugar de ser experimentadas y adaptadas