Comment by i-blis

Don't you get bored with spending many years learning and becoming advanced or an expert in a system paradigm (like different hosting systems), a programming language (i.e. Perl), or a framework (pick your JS framework), only to have it completely obsoleted a few years later? And then in a job interview, when you try to sell yourself on your wisdom as expert on thing X, new to Y, they dismiss you because the 25 year old has been using Y since its release three years ago?

And when you're in an existing company, stuck in thing X, knowing that it's obsolete, and the people doing the latest Y that's hot in the job market are in another department and jealously guard access to Y projects?

How about when you go to interview, and you not ONLY have to know Y, but the Leetcode from 15 years ago?

So maybe I've given you another alternative to 'it has to be power, there's no other rational reason to go into management'.

Here's a gentler one: if you want to build big things, involving many people, you need to be in management.

Do you enjoy brick laying and calculating angles around doorways? You're the engineer. Do you want to be the architect hiring engineers, working with project managers, and assessing the budget while worrying about approvals? They're different types of work, and it's not about 'power' like you are suggesting. Autonomy and decision-making power are more the 'power' engineers often don't get (unless they are lucky, very very smart or in a small startup-like environment).

I actually don’t think the author wants to become a real manager, he wants to play a video game where he sends NPCs around to do stuff.

Real managers deal with coaching, ownership, feelings, politics, communication, consensus building, etc. The people who are good at it like setting other people up to win.

As an engineer, I can never actually let a system write code on behalf of me with the level of complacency I've accumulated over the years. I always have opinionated design decisions, variable naming practices. It's memorable, relatable, repeatable across N projects. Sure, you can argue that you can feed all this into the context, but I've found most models to hallucinate and make things unnecessarily opaque and complex. And then, I eventually have to spend time cleaning up all that mess. OP claims they can tell the model over the phone what to do and it does it. Good for OP, but I've never personally had that level of success with my own product development workflow. It sounds too good to be true if this level of autonomy is even possible today without the AI fucking something up.

Once you've written enough image caches, I think you often find yourself ready to move on to the higher level architecture of a larger project.

Often too it's the architecture that can cause a grand idea to crash and burn—experienced devs should be moving toward solving those problems.

For me, getting into management was less about feeling bogged down in the specifics, but more about control (directed mostly above). Anyone who’s had a bad manager or bad decisions they need to adhere to might be familiar with the feeling that caused me to dip my toes into management.

Like I’ve been in situations as an IC where poor leadership from above has literally caused less efficient and more painful day-to-day work. I always hoped I could sway those decisions from my position as an IC, but reality rarely aligned with that hope.

I actually love the details, but I just don’t get too deep into them these days as I don’t want to micro-manage.

I do find I have more say in things my team deals with now that I’m a manager.

Some people want the thing done more than they want to do the thing. That gets to extremes of exploitative parasitic behavior, but it's true at much less obnoxious scales: ever used a programming language's standard library instead of inventing your own _whatever_? Probably a yes.

That can extend to arbitrary absurdity. You are probably not growing your own food, mining your own ore, forging your own tools, etc etc etc.

It's all just a matter of where you rely on external tools/abstractions to do parts of the work you don't want to do yourself.

>the joy of problem solving

It's frontier exploration that brings me joy. If a clanker can do something, then it's a solved problem. I use all the tools at my disposal to push the frontier of problems solved. Wasting my time re-inventing the wheel brings me the opposite of joy.

On a similar note, I have never heard the phrase “higher level abstractions” abstractions so much. Everywhere I look, higher level abstractions. It’s becoming one of those phrases I have an instant reaction to. The word “abstraction” used to mean something, man…

I don't really want to be a manager of humans, although my role as an engineer is a leadership role that has some overlap.

But I'm acutely conscious that in the 5+ years that I've been a senior developer, my ability to come up with useful ideas has significantly outstripped the time I have to realize those ideas (and from experience, the same is often true of academics).

At work, I have the choice between remaining hands-on and limiting what I can get done, or acting more like a manager, and having the opportunity to get more done, but only by letting other people do it, in ways that might not reflect my vision. It's pretty frustrating, to be honest.

For side projects, it's worse. Most of them just can't be done, because I don't even have the choice.

> My guess is that the drive is toward power

Not really for me. Programming is an effort type job. The more effort you put in the more you get out. True in other professions sure but multiplied with dev work. When became a dad everything changed. Solve hard problem or spend time with kid. I couldn't juggle the two. So i made a choice and fortunately had an opportunity to move into management.

Anyway full circle now I'm back to being a dev and this go around couldn't be easier with our ai agents. Point is I went into management because I was forced, not at all for power.

It’s more that there’s a career ceiling and ageism is a looming threat. There are far more management jobs than high-level IC and for decades there’s been this thought that older engineers will be replaced with younger ones more aggressively than managers, although the big tech layoffs raise questions about whether that’s still true. I know multiple people who moved into management not because they were enthusiastic about it but because that was the best path for their career.

I liken it to being an author.

You want to write a book about people's deepest motivations. Formative experiences, relationships, desires. Society, expectations, disappointment. Characters need to meet and talk at certain times. The plot needs to make sense.

You bring it to your editor. He finds you forgot to capitalise a proper noun. You also missed an Oxford comma. You used "their" instead of "they're".

He sends you back. You didn't get any feedback about whether it makes sense that the characters did what they did.

You are in hell, you won't hear anything about the structure until you fix your commas.

Eventually someone invents an automatic editor. It fixes all the little grammar and spelling and punctuation issues for you.

Now you can bring the script to an editor who tells you the character needs more development.

You are making progress.

Your only issue is the Luddites who reckon you aren't a real author, because you tend to fail their LeetGrammar tests, calling you a vibe author.

For many people, code is just a means to an end to solve problems and build. The joy from solving problems doesn't disappear. Would you use traditional (not WebAssembly) assembly to build a web application? Probably not. LLMs make a lot more sense if you think of it as a tool to translate requirements into solutions.

I became a manager so I could solve bigger problems. Good managers do dive into the details. It's a mistake to think that as a manager, you don't have to concern yourself with the minutia. You still have to do homework and deep thinking. you just don't have to write the code

It has nothing to do with power. I just want to build bigger, cooler things, faster.

I don't think it's about power. I feel more empowered as an engineer than I would as an engineering manager. As an engineer I have the power over all the intricate details of how systems work. As an engineering manager if I am lucky I would get to decide whom to fire if my team's budget gets a cut.

I think it's that there is only that much demand for solving really complex problems, and doing the same thing over and over is boring, so management is the only way forward for many people

My 15 year old son has been building his own video games with Unreal Engine for a few years..

I was recently looking for mentors to work with him and advance his skills, targeting college aged kids / young 20s..

It was surprising to me how many people I came across in this field at this young age that are trying to focus on the "higher level" game planning aspects and not so much on the lower level implementation specifics.

"I thought naively that engineering always has been about dealing with the specifics and the joy of problem solving"

For me it's the other way around. Engineering was always a means to an end - I just want to build products. It was a creative artform more than a scientific endeavour.

Engineering, to me, is simply "the art of compromise."

You can't do that from a high level abstract position. You actually need to stand at the coal face and think about it from time to time.

This article encodes an entitled laziness that's destructive to personal skill and quality work.

I think plenty would be willing to be managers if you removed the volatility of human personalities from it. At least for me, it means I get to focus on the more interesting tech work and not worry about writing tests or github actions.

another way to look at it is that management is a job with a set of skills, challenges, and rewards, just like any other, but as a civilisation we seem to have tied it to power and hierarchy, and made it something you need to be promoted into rather than choosing as a career from the outset (MBAs notwithstanding). maybe a lot of engineers would have gone into the engineering management path if they could have, and engineer was just seen as the more entry-level option.

i like the aspect of engineering that's building useful or interesting or fun things for people, and i'll always experiment with new tech that facilitates that

Software dev has been promoted as a good career path for almost 2 decades now. Naturally you'll have a bunch of people going in only because of money.

A few years ago, when Agile was still the hot thing and companies had an Agile "facilitor" or manager for each dev team, the common career path I heard when talking to those people was: "I worked as a java/cobol/etc in the past, but it just didn't click with me. I'm more of a peoples person, you know, so project management is where I really do my best work!".

Yeah, right...

It's human nature.

https://en.wikipedia.org/wiki/The_Stonecutter