If I may ask, I would love to hear your perspective about the fuzzy, squishy reasons why hackable turns into maintainable from a management perspective. I thin

If I may ask, I would love to hear your perspective about the fuzzy, squishy reasons why hackable turns into maintainable from a management perspective. I think I understand what you mean about the two. I know embarassingly little about electronics despite being interested in it for a long time, and have boggled at how much a circuit schematic can differ from PCB layout. On a schematic you can just go "and here are 48 data lines and we'll just draw some dots to illustrate that they yeet all the way over there" but on a PCB you not only have to route them (possibly across multiple PCB layers) but maybe some of the lines have to have squiggly messes in them so they're all exactly the same length and the electrical impulses arrive at the correct nanosecond. The good electronic engineers are the ones who've learned to fluently translate between schematic and PCB layout in their heads, in exactly the same way someone might fluently translate between languages to the point that they forget which language they heard something in, their memory just encodes the meaning directly because the neural routing is that deep/strong/integrated. A good programmer has learned to understand/accept/integrate(/resign themselves to) the fact that the "focal point" of almost every program is in the programmer's head, not on the screen, and that whatever's onscreen is instead ultimately just a giant pile of little pinball-paddle nudges that hopefully prompt the reader to go "OH" and have the program structure "pop" into focus. Once you have that, you're good to go: that distinct mental model is detached from this class structure or that naming convention or whatever pattern, and thus not bound by the mnemonic/interpretative/structural limitations of the proverbial puzzle pieces that constitute the methodology; it's the superset of all of that and all the machinery that hasn't been set into stone yet. It is so, so weird how programming slams right up against the edge of design/engineering/bigger-picture-greater-than-the-sum-of-the-parts vs Management™.