> instead focus on how easy it would be to change the behaviour of existing code. This has been my principal design consideration for a while now. Not "the cod

> instead focus on how easy it would be to change the behaviour of existing code. This has been my principal design consideration for a while now. Not "the code should be short!" or "the code should be elegant!" but "it should be easy to change" because your requirements are always going to change. It just so happens that the latter usually means things like single responsibility and loose coupling that bring about the former as a matter of course.