I’ve been reading through a lot of your comments and you’ve made me want to review my existing code bases and simplify things! I’ve been that intern who has had

I’ve been reading through a lot of your comments and you’ve made me want to review my existing code bases and simplify things! I’ve been that intern who has had a large legacy C/C++ codebase dropped on my lap, and I would have certainly appreciated it had the original developers had your mindset going into their development. It certainly makes sense to me why we, as developers, should be writing both performant but readable-first code that allows those in the future, given an inherent assumption that the project we’re working on will succeed, to be able to easily maintain, debug, and improve the codebase. I think if the language-specific constructs offer a significant advantage that is not achievable in another, more straightforward, language-agnostic manner, then the intention and explanation of its function should be clearly annotated in comments from the original developer (with reasoning, pitfalls to avoid when attempting to debug, refactor, extend, etc).