This is a perspective I've been following and cultivating for a long time, and even led to my current endeavor [0]. Code should really be structured to be easy

This is a perspective I've been following and cultivating for a long time, and even led to my current endeavor [0]. Code should really be structured to be easy for us humans to understand and change, and we humans are sometimes not as logical as we'd like to believe. It can sometimes feel like a lot of folks are chasing other priorities and forget to even consider the human aspect of architecture. I also often see people make mistakes on what "simplicity" is, and what kind of simplicity should be optimized for. For a recent example, Rust's borrow checker is based on a simple rule (roughly, a reference can have one mutable reference xor multiple readonly reference) but it can often lead to more complexity than the corresponding program written in a GC'd language. Knowing when and how this happens is an art! I'm not sure if I have anything you haven't thought of already, but I'd love to contribute a chapter or two on whatever topic, or edit anything that needs editing. If you'd like a sample of my work, I'm particularly proud of [1]! [0] https://vale.dev/ https://vale.dev/ [1] https://verdagon.dev/blog/yak-shave-language-engine-game https://verdagon.dev/blog/yak-shave-language-engine-game