I like to build software products. I don’t like to build software, but it’s the only way to build software products.

“Understanding” is quite an overloaded word.

Understanding architecture, robustness, the “crumple zones” of a system? I’m all for it.

Taking three days to “understand” how postgres transactions work under the hood for your generic SaaS? Uh..

I have seen a lot(!) of the last type of “understanding” and it’s infuriating. The same types will often not understand the business, its stakeholders, the architectural constraints beyond the technical, etc. Understanding takes many forms.