Well, lawyers just reiterate books and like to argue a bit.
I completely agree with this post that this isn't a problem of developers at all and even that a bit more openness to lacking experience is warranted (I don't believe that to be unprofessional at all).
The fields someone has expertise in are niches in most cases. The particularities of an xcode build process isn't something you can deduct from theoretical computer science either.
I don't want to take myself and my expertise too seriously, I think CS has more of a problem with pretending to know it all. There are times when you want to reflect that, especially to customers if you think you can provide solutions to their problems. But with increasing experience you should develop an estimation on how small your area of expertise really is. Call it specialized if you want to, but looking at the big picture most engineering disciplines are too vast to champion them completely. Same with math and physics.
I would argue that effectively using tools you don't fully understand is one of the primary skills of software development. If that were not the case, we would spend about 95% of our time taking online courses and following tutorials and 5% of our time getting work done. Instead, it's the reverse.
But that does not negate the value of deep expertise in one or several chosen sub-disciplines. Being "T-shaped" is a thing.
I completely agree with this post that this isn't a problem of developers at all and even that a bit more openness to lacking experience is warranted (I don't believe that to be unprofessional at all).
The fields someone has expertise in are niches in most cases. The particularities of an xcode build process isn't something you can deduct from theoretical computer science either.
I don't want to take myself and my expertise too seriously, I think CS has more of a problem with pretending to know it all. There are times when you want to reflect that, especially to customers if you think you can provide solutions to their problems. But with increasing experience you should develop an estimation on how small your area of expertise really is. Call it specialized if you want to, but looking at the big picture most engineering disciplines are too vast to champion them completely. Same with math and physics.