For a very long time that was my own journey. I got up to CTO level for a while. Then I realized I just don't enjoy it, so now I'm a senior engineer again. Wanting to be a CEO takes a very specific mindset.
For a very long time that was my own journey. I got up to CTO level for a while. Then I realized I just don't enjoy it, so now I'm a senior engineer again. Wanting to be a CEO takes a very specific mindset.
There is no such thing as 'not having a boss' unless you live in a cabin in the woods, independent of the world.
Either you work for a corp. with a manager, with what are frankly relatively clear functions - or - you work for the whims of the market and or consulting customers (and possibly a board and investors) in which case you adopt an utterly different tone and there's no expectations of clarity or consistency and you're always on your heels.
I don't think people have an internal conception for how that 'stability, clarity and peace of mind' that they seek is actually a total luxury, something which all those people working out there struggle and toil to create. Like a little cottage on the ocean that doesn't move with the big waves, it's a fabrication, something constructed, not a 'simpler escape' detached from the system.
I am surprised at how few of them do, considering how low the barriers of entry to company making in tech are (compared to other industries with heavy requirements in space, equipment, expertise and regulations)
So I am also surprised at your experience. Most devs I know just wanna code.
We all know that developer who wanted to start their own startup/product but felt into hard times and so to keep the lights running they started to do consultancy/freelancing on the side. Then consultancy became their main thing and the startup was sent to the back burner or they just quit the venture entirely.
Same here. Never heard of any developer wanting to be CEO of a big company. Typically startup, yes, but that's mostly for "independence" and doing something cool, faster, etc.
Second, I also think you have a very common but incorrect view of what a developer even is. You write:
> Most developers who enjoy writing code run away from meetings given the slightest opportunity,
Most developers don't necessarily enjoy writing code. Some do, to be sure, but a lot view writing code as a means to an end. Sometimes that end is money; sometimes that end is to create products. And if what you want is money, or to create new products (or to have new experiences, or to have a fancy job title, etc), all of those are reasons to want to run a large company. (Not all of these are what I would consider good reasons, but they are reasons).
Secondly, you can really hate meetings when your job is to write code, but also would enjoy meetings when your job is no longer only about writing code. Forget running large companies - most people who get even a mid-level manager position will be busy in meetings for a large amount of their time, and will rarely if ever code, and this is considered a very desirable career path by many devs (though not all, to be sure).
Think they want to run their own large companies.
> A lifestyle business is a business set up and run by its founders primarily with the aim of sustaining a particular level of income and no more; or to provide a foundation from which to enjoy a particular lifestyle.
Most engineers like tech, but have little exposure to how they interact with the larger organizational structure and design, with customers, with fundraising, and with a slew of other things. Stepping through a few roles gives that visibility. That makes for a better engineer.
I'll start and end my career in a tech role, but I do periodically do dives into other sorts of roles in the meantime.
This sounds like an unremarkable subset of {vaguely dissatisfied lower-level workers who dream of a new job with far more power, fame, money, and/or interesting stuff}.
Similar are the people who read novels (at least occasionally), and have dreams of becoming a famous author. In my experience, ~0% of them are actually willing to sit down and try to write a 3-page story.
If I say "no that would be bad, goes against my ethics, increases tech debt too much, bad for UX, etc." I don't want anybody to override me, even though generally decisions ultimately fall on the CEO.
We probably should just avoid saying "average" and use "mean", "mode", "median", or whatever we actually mean instead.
It’s only when someone says something like the average family rather than saying the average income when things get ambiguous. Typical on the other hand is closer to mean because it’s tossing out outliers.
It is also pretty absurd to assume without explanation that a minority who are especially bad at management have even their minority presence in management given that if sucking matters it should correlate with some type of failure that eventually correlates to drop out.
In fact, it's the other way around - a proof that the person suggesting this doesn't know math.
If 80% are skilled at 1 and 20% are skilled at -100, then most are better than average.
Or: Imagine a room of people. Bill Gates walks into that room. Most people are now below-average wealthy.