Refactoring: The Golden Master Technique
The Golden Master method aims to prevent regressions during refactoring and relies on the prior creation of a set of functional logs.
The Golden Master method aims to prevent regressions during refactoring and relies on the prior creation of a set of functional logs.
Technologies are fleeting: invest in mastering architectures, paradigms, and methodologies, which will serve you throughout your life.
Technology is beautiful and fascinating, but it is not an end in itself. Information technology is there to solve problems in a pragmatic way.
Trying to support a company or an individual who doesn’t want to change is counterproductive. It’s better to rely on the corporate culture.
Error as a pedagogical principle: it is necessary for a deep understanding of problems and gives meaning to best practices.
Refactoring comes with two challenges: avoiding regressions and overcoming tunnel vision. To help you: Golden Master, the Mikado Method, and the Strangler Fig pattern.
Technical debt is dangerous because it accumulates silently, until the day the company hits a wall. CEOs, take the lead.
Writing code isn’t that hard; evolving it is. Readability, testability, modularity: the three pillars of software craftsmanship.
Training is, at best, a spark. Without ongoing support, putting what you’ve learned into practice is often difficult.
When the organization is dysfunctional, you call in an agile coach. When the codebase stops evolving, you call in a code doctor: a technical coach.