I love this. For as long as code needs to be maintained, code will always be just as much about communicating with people as it is about people communicating w

I love this. For as long as code needs to be maintained, code will always be just as much about communicating with people as it is about people communicating with machines. One thing I still enjoy about message passing OO (by which I really mean Ruby) is how it’s really easy to separate concerns to the extent that each file contains one module/class with one public and a few private methods in it. I went a bit bonkers this year and found myself doing one method per module, which is the extreme version of this. Languages with mixins are great for this too. Mixins are, amongst other things, a nice shortcut around composition that lets you put individual facets of functionality in separate files, albeit with fewer guarantees about code remaining uncoupled. It’s a shame Ruby’s module system doesn’t better support private for modules though.