Entrevista a Fernando Cejas
summary
Always stay ready to roll up sleeves and change code, but prioritize refactor incrementally so problems never become an urgent bomb to defuse. Follow consistent engineering practices to avoid decay, and when messy areas appear, use metrics to find hotspots, estimate work, plan and communicate the effort, and invest time where metrics show high risk. Aim for clean code continuously rather than one big, risky rewrite.
AI-written summary · about
related talks
47mPrioritization, Refactoring, and Keeping You Codebase Healthy
02mEntrevistamos a Cristian Cotes
02mWe interview Vicente Baixauli and Paco Navarro
03mInterview with Javier Abadía, Speaker at Commit Conf 2019
03mWe interview Alvaro Fidalgo
38mWriting Code That Lasts Forever
50mRefactoring Is Not Just Clickbait
25mBuilding Castles, Not Sandcastles: Strategies for Software Architecture Success