In my experience that’s only been the case for functionally non-unique software. At my job we write software that’s effectively unique. There isn’t a pattern to fall back on. It makes a lot more mistakes very frequently, since the nature of it keeps trying to guide it to the known path. It’s great for debugging since the manner that some check failed is chasing through known logic, and it doesn’t matter that it doesn’t see the existing code as probable or fitting a known pattern if the shape of a switch statement is still the same. In my personal projects I’ve even run into issues getting it to do stuff like vulkan synchronization barriers in a way that doesn’t continuously devolve into what you see in tutorials, with an ultimately unstructured pile of adhoc resource allocation and barriers.