Is software becoming so regulated, so expensive, and so important in our software-driven lives that the developer job is becoming not exciting anymore?
Are we developers software crafters, or mere pattern implementors?
Here I propose Continuous Change, a new methodology for creating software with only one foundational pillar: never stop challenging our code, never stop changing our software..
I consider the aversion to change that monoliths exhibit as their defining feature. And the benefits of embracing change in organizations based on software are explored.