I've been programming for 30+ years. When I sit down to code, most of the time I've thought through it before even typing and am ~99% confident I won't hit a roadblock. I've spent half my life mastering my programming skills.
BUT: I'm a high-level technical lead / product lead, so I only get to write code a few times a month and it is more for stress-release because I've mastered it (and because I am a mentor to / lead 30+ programmers and this gives me a chance to interact with them).
If I wrote code 100% of the time I'd being winging it 1% of the time. So in this regard you are correct.
However, because of how corporations work, once you've demonstrated proficiency at "junior level work" you move up to the next big challenge. Yes, that sounds pejorative, but coding is not hard compared to the next levels of competency: programming is junior level, software architecture is senior level, product roadmap is staff level, corporate direction is above that. Sorry if that hurts your butt, but knowing the latest JS framework or how to optimize your C++ is trench-work compared to convincing the CTO where your division should invest its R&D budget for the next 5 years.
Because there is no "school" for learning how to plan your company roadmap, you really do have to wing it and learn from experience. And since shit is changing so fast... well, sure there are basic principles studied is business (that sometimes are useless for strategy but are good for tactics)... but in tech, it very much is "wtf is going to happen next and is this the right choice." Sure there is an executive board, and vice presidents gunning for your role, but you REALLY are winging it at C-level unless you are in your 70's and have helmed multiple large companies.
So from a top's down view from higher-importance positions, winging it is simply part of the job.
This viewpoint, that those jobs are harder, is just self-justification (either to themselves or to everyone else) for people higher up that list of their higher pay than those below.
I don't believe those skills are actually harder (nor easier, just different), or that you have to be good, e.g., at programming to be good at corporate direction.
What is, IMO, true, is that those skills do have larger impact (or at least, significantly more obvious impact), which is at least a reasonable justification for higher pay.
But don't pretend that being good at software architecture, corporate direction, etc, means that you're actually smarter than that person who's "just" a programmer.
He's not saying higher-ups are less competent, he's saying winging it is inevitable and necessary at the C-level _because_ it is impossible to already have experience and proper training tools for the decisions one has to make.
What I’m trying to say it’s that winging it is good, it’s good to get lost in a bazaar, we don’t all need cathedrals.
[1] https://en.wikipedia.org/wiki/Peter_principle
edit: punctuation and wording
If these folks really are winging it, that's code for "hey, we're dumb, come exploit us". It's where pomp and circumstance close deals rather than actually delivering something technically good. It's where things start turning into a social club but the salaries continue to climb.
How would you teach corporate strategy in a way that’s simultaneously honest (and useful to the individual) and palatable?
Maybe if you limited yourself to strategy within coops, where the individual’s incentives really are aligned with the incentives of everyone else in the organization, or mid-level management, where you only have a certain category of power - but that’s less useful because coops aren’t so common and mid-level management is ultimately subjected to what the upper levels decide.
In the end, individuals with positions where they have to worry about “business skills” or “corporate strategy” don’t usually have incentives which are aligned with the people at other rungs on the ladder. If you teach corporate strategy in an honest fashion, a not-insignificant portion of your material will be how to effectively redirect money from other areas in the organization to yourself. Most of your students will see that at stealing.
Or maybe you don’t teach how to leverage these strategies, but just how to spot them in action?
Either way, K-12 is traditionally focused on skills that are more foundational and generally useful. Admittedly, that’s changing as some schools introduce things like CS courses, but usually these are electives and not part of the core curriculum.
What really ought to be taught is personal finance and basic investing - those subjects can be molded into information for any age group.
I imagine some of the known valuable skills can be taught to a certain degree. Problem-solving, learning how to learn, assessing opportunities, looking for inefficiencies, communication, telling a compelling narrative, and so on. But I don't think it is easy to teach those things in a highly effective manner, at least not in a short amount of time.
This seems to imply "if only everyone got adequate training". It's not like that, though. There's a lot of important, worthwhile endeavours that inherently involve having to figure things out as you go.
In some domains you don’t have a choice; there are too many moving parts, decision making is of necessity based on noisy and incomplete information, the domain is too messy for formal models to be useful. You just have to intuit and improvise. This is more often than not the case when human interactions are involved. Trying to impose engineering solutions to social problems usually ends in disaster.
1. It's amazing how many people ignore those checklists and processes in the name of winging it, and
2. It's amazing how despite dozens, hundreds, and sometimes thousands of people-years in an organization, sometimes there's still no checklist or process and winging it is all they've got.
Your comment has given me a new perspective on what I consider a developer hostile environment.
Highly trained, competent people often encounter situations they're unfamiliar with. That's what keeps the job exciting.
To believe otherwise suggests either lack of training, or ...
I think there are benefits to both, but whenever I see someone complain about everyone winging it, I think they show their incompetence and lack of professional development.
I work in a very fluid field (I recruit salespeople), so the rules are much less defined than if I were building rocketships or bridges or whatever, but there's still an abundance of work out there giving guidance on how things can be done.
You see the same things in startups. The successful ones are emulating a lot of the lessons learnt by people who came before them, and then innovate in a small area. The unsuccessful ones are "innovating" on everything.
It's certainly the cause for a lot of overengineering and early complexity.
Competent people with good training in some discipline are able to apply that training to competently achieve goals. This allows them to apply knowledge that they didn't develop themselves by trial and error, and is much more efficient, with better outcomes than the alternatives.
Unfortunately, this often seems to be the exception rather than the rule. Although "seems" is the operative word: if it weren't for this effect, we'd see many more bridges and buildings collapsing, ships sinking, etc.
It's just that many areas of human endeavour tend to more commonly involve untrained people "winging it", and that's what the article focuses on.