"I can still feel the regret of not seeking the challenge of just leadership." He's right. Programmers need to get into leadership, because they have a chance of knowing what "just leadership" might look like. When non-technical people lead technical people, the chance of getting into a good flow is less (though by no means impossible).
The problem is that many technical people are not "people" persons. Part of that may be personality, some of it is background, but a lot of it is study and thinking too.
My brother builds huge buildings. He's very proud of them. He often (gently) gives out about the marketing people and their mad notions and lack of technical understanding. But, as I point out to him, if they don't sell the apartments, he doesn't get to build the buildings in the first place.
Ultimately, therefore, if you're going to put your skills into a corporate enterprise (of any size), you need to accept that it all originates with selling. "Business is simple", says Alexandre Dumas, "it's other people's money."
Progammers should either accept that they love playing in the intellectual sandbox of coding and that the material rewards will be variable. OR they should seek leadership.
Lawyers, Bankers, and Doctors get to play in intellectual sandboxes, and they get paid really handsomely for it, even if they are completely anti-social people.
The reason we get paid less is that we don't have any of their safeguards:
- Lawyers aim to become partner. It's very socialist-y this way. The goal working in a firm is to become an owner of the firm and share in its successes.
- Doctors have a guild. They keep their bottom end tight by regulating who becomes a doctor, keeps them always in demand.
- Bankers know how much things are worth. That's their business. They know how much they generate, even if they are far from the point of sale. They also aren't squeamish about asking how much their co-workers make, and negotiate aggressively.
Programmers should start realizing that the main reason we make little is that we undercut each other a lot, and are outright hostile to many tools that other professions use to safeguard their position.
I think Lawyers and Doctors I think are much similar to programmers than you think.
Regular front line grunt work employees work long hours and get paid decent professional wage. As you said they can get promoted to Partner, a partner is a part owner of the business, they don't do much technical work, they do a lot of management. There are similar opportunities for Software people to start small companies and make money too. its not quite the same as there aren't the big company partnerships, but big startups with employee stock are close.
The biggest difference is the half life of knowledge in Software is much shorter.
Both lawyers and doctors have powerful associations that control and regulate the labor supply via a certification process. Technology doesn't have this. In fact, technology has the opposite: a H1B program that brings in more and more labor supply to keep wages low.
People also seem to value experienced Doctors and Lawyers. They just see the front of a web application, and if it looks OK they assume that it has been put together well.
You could go further regarding lawyers: they're a government jobs program. On balance a beneficial one, but a government jobs program nonetheless. If there were no government there would still be doctors and programmers (albeit probably fewer), but there wouldn't be any lawyers.
You are the first person who ever described the lawyers' dog-eat-dog up-or-out competition for parter as "socialism" -- unless you meant it as a sarcastic analogy to Chinese Communist Party
Yep, this leads me to my biggest regret as a programmer: going into engineering instead of medicine. I really should have become a doctor or some other kind of hospital worker instead: the money would have been at least as good, and I would have gotten to work in a place with lots of women.
You would also have had to go to school for several more years, incur massive debt in the process, and work insane hours for virtually no pay as a resident.
Yeah, but the long-term rewards definitely seem worth it. Also, they cut back on the residency requirements a while back because sleep-deprived residents were making fatal mistakes.
'Leadership' is not a job description. I hate it when people act like it is. Even if your job is making decisions; leadership isn't making decisions, it's making them in such a way that those under you feel empowered by them, rather than powerless in the face of them, and that you take responsibility for any fallout from those decisions rather than letting that shit role down hill.
Everyone I know who has wanted to 'bring leadership' in their role, and nothing else, has been a complete waste of space, at best useless, at worst an obstacle. I have never been glad to have such a person working with me.
The problem is that many technical people are not "people" persons. Part of that may be personality, some of it is background, but a lot of it is study and thinking too.
My brother builds huge buildings. He's very proud of them. He often (gently) gives out about the marketing people and their mad notions and lack of technical understanding. But, as I point out to him, if they don't sell the apartments, he doesn't get to build the buildings in the first place.
Ultimately, therefore, if you're going to put your skills into a corporate enterprise (of any size), you need to accept that it all originates with selling. "Business is simple", says Alexandre Dumas, "it's other people's money."
Progammers should either accept that they love playing in the intellectual sandbox of coding and that the material rewards will be variable. OR they should seek leadership.