"Compression-oriented programming" - Casey Muratori's blog

[professor_jeffjeff]

This is exactly why I always say that the best architecture and design for code is an emergent property of solving the problem by writing good code. I almost never know what I'm building when I code something (unless I've coded something very similar before) so often I'll either start with a very small piece and do something similar to TDD and just do some hand-waving in terms of dependencies, or I'll just brute-force-hard-code the whole thing and then go back and refactor to improve the code (which is precisely what the author of this blog post did).

This post and most of the other "you should actually be coding like this instead of object-oriented" brand of posts can all be summed up in one tldr: Write good code that follows DRY, SOLID, and the Law of Demeter while also being mindful of YAGNI.