Thank you for this! I’ve been feeling this a lot recently too. It’s cool that we’re able to contribute code so much faster (especially new engineers or on new projects). But we’re sacrificing understanding for speed which will eventually have an inverse effect when we can’t understand anything anymore. It’s awesome that I was able to contribute a performance fix to Zensical which is written in Rust, a language which I don’t know well. I understood what I could, but they are responsible for what goes into the repo ultimately. It unblocked me and they accepted the quality, great! But we MUST NOT apply the same bar to projects where we are the core maintainers. However, that’s what’s happening unfortunately.
Quick though is to have some global or repo-level skill that asks questions throughout a session or towards the end to probe for understanding. But I agree, there needs to be some deeper process or cultural change.