Ola Ellnestam, along with co-author Daniel Brolund, wrote the book The Mikado Method, which describes an incremental approach to code refactoring, as well as project management. In this interview Ola discusses the application of the technique, common pitfalls and objections to it, and provides insight into how the technique can be used to help communicate technical debt and dependencies with non-technical stakeholders.Listen, watch, or read the transcript
We often contrast software to physical buildings--the idea that software is easy to change, whereas buildings are difficult to change. But is this really true?
Pick a methodology: Scrum, Kanban, XP, Lean or DevOps?
None of these items directly replaces or conflicts with any of the others. In fact, you can use them all simultaneously.
"Readability" is subjective
Ask yourself: Will the least experienced developer likely to read this code be able to understand it?