soontimes
10 hours ago
Product managers is not just about making product features. It’s a job that requires lots of human interaction, and this part is notoriously complicated for engineers. Article states that a person coding the feature can build a product intuition, and that’s true, product is not sorcery, but from my experience most engineers are just not interested in that. That may change, of course, if engineers will be pressured by economic situation, but until that they’re happy when someone else is interacting with users and stakeholders.
thousand_nights
10 hours ago
at my company they are trying to get us engineers to absorb that role so now we spend a lot of our time doing meetings and human interactions like this with other parts of the business and making decisions
idk how common this is in the industry though, but since the introduction of AI my role has expanded so much beyond what is just writing code, i'm now a devops/product/dev person and expected to do all of that at once for the same pay as before
i actually enjoy it myself cause you feel less like a ticket pusher
soontimes
9 hours ago
It is common, and you can resist (risking your salary), going deeper (hardening engineering skills) or wider (doing product, analytical, etc. work). I believe that an engineer with product mindset is extremely valuable for a company, so I would encourage taking that route. However I’m also seeing engineers taking first or second path.
As long as humans are making decisions, human interaction remains important. From this perspective, PMs are still in a better position than engineers
doc_ick
7 hours ago
“It’s a job that requires lots of human interaction, and this part is notoriously complicated for engineers.”
Don’t worry, human interaction is very complicated. Thankfully there are no llm models/google/xai with technology to do exactly that. Your pearls are safe.
user
9 hours ago
random3
10 hours ago
users will get their problems solved directly by engaging with AI without needing software
flowerlad
9 hours ago
Users, sure. But what about businesses?
tmpz22
10 hours ago
We don't need code anymore, we just need intermediate deterministic artifacts that the AI can produce and the user can validate in order to circumvent the - by definition - non-deterministic nature of LLMs.
What should we call these intermediate deterministic artifacts? Code!
nkozyra
9 hours ago
I think there's a big distinction between needing code - the machine abstraction for electrical logic gates - and code that will ever need to be read by a human.
Yeah we'll still need to know a sequence to flip bits in the right order, but it isn't code you'll recognize.
MiroslavPokorny
9 hours ago
You fail to appreciate that creativity is more than just code. I would argue code is the easy part. The difficult part which you obviously dont appreciate or value is being creative and "different". Thinking what or how something can change or be better.
agumonkey
10 hours ago
the day hardware and whatever ml engine reach apple ii cost then yeah everybody will just let it run
iugtmkbdfil834
9 hours ago
I honestly can't tell if it is satire or not and I like AI.
pianopatrick
9 hours ago
I had to call Verizon customer support yesterday for something. Their AI customer support agent sounded like a person and worked just fine.
I think you can eventually set up an AI system that handles a lot of the interactions and conversations people have.
jghn
9 hours ago
You're right that this is going to suck for the engineers who fit the stereotype, didn't like interacting with users, and would express that they just want to stay in the code.
For the rest of us, that's not a problem.
solatic
9 hours ago
You're missing the point about how the industry is going to go through a great narrowing. In the past, you'd have one PM and 8-12 engineers. Now you only need 2-3 people with both product and engineering ("architecture", to quote the author) skillsets. You are absolutely correct that most engineers are not interested in the Product side - those are the engineers who are going to get cut in this great narrowing. Quoting the author:
> I grew up with the distinction of "tech guy" needs a "product guy". I am not dismissing it, I am just saying that the world is entering into a phase where both roles are eventually melting into a single function.
The whole reason why Engineering exists in organizations is to take Product's ideas and turn them into reality. When Product can realize its own ideas (through AI) then Engineering is no longer necessary as a political sub-organization. Making it happen requires engineers to learn Product skills and adopt a "Product" job title. We will likely call people with both skillsets Product Engineers. People who can't adapt to learning both skillsets are at risk of losing their jobs.
soontimes
9 hours ago
I agree with your point about great narrowing, but I also expect complexity to increase accordingly. Yes, in the past you needed 10 engineers to solve a problem, and now you need only 2. How I see this - problems will become more complicated, so that you still need 10 engineers to maintain your business profitable and competitive.
I do not believe in PM making good engineering solutions, even with AI. Similarly to engineers, not interested in product, products have no interest in engineering. However you still need someone responsible for the decisions.
One possible future I’m considering is humanity converging to a “unit of responsibility” - in order to run a company with a certain scale you’ll need to have N humans responsible for different parts of the business.
solatic
2 hours ago
Let's put it this way - I don't think you could run a Fortune 500 company with 2-3 engineers. I do think there's still a role for "Non-Functional Software Engineers" who are hired to take a long-term perspective on systems maintenance for the golden geese that keep the company's revenues rolling in, handle vendor migrations, stuff like that, which is very different from the responsive, short-term perspective that Product needs. Companies will probably still benefit from people dedicated to their analytics / BI / data pipelines, as an internal product. Roles like Security, Legal, GRC will survive, not because AI can't replace them technically, but because someone still needs to be held accountable. Headcount will still rise with the number of products offered, and eventually you still need the systems and guardrails needed to keep that number of people aligned. All of that is complexity.
sdevonoes
9 hours ago
But “product” people can’t really build real production software even with claude. Prototypes, sure. Engineers can (and many do already) deal with product topics. It’s easier for engineers to become more produc oriented than for PM to be able to handle tech topics with AI
baconner
9 hours ago
I think that's the point. Product only people who didn't build significant engineering understanding aren't going to be replacing anybody and are now at serious risk. Engineering people who did the same and don't want to go find out with customers and the like are also at risk. Smaller teams of people with more cross cutting skills in eng, product, design are going to outperform in this world. everyone else is just vibing their way rapidly to problems imo.
Ai makes it a lot more urgent but pm folks who dropped features from on high never worked as well as pms down in the weeds with engineering in the first place, nor did engineers who didn't want to get out there with customers and understand the why deeply.
user
2 hours ago
sublinear
7 hours ago
It's not that bad. You're describing what senior devs have always been.
Don't get me wrong. There absolutely is survival bias at play here. Historically speaking, most devs change careers long before they turn senior.
I'm just not understanding the hysteria. This is the latest set of reasons for people to quit. Before AI, it was outsourcing. If you want to, just quit already. If you want to stay, deal with it.
28304283409234
8 hours ago
> notoriously complicated for engineers
That is such bs. I’ve known just as many pms incapable of human connection. And scrummasters. And project managers. And every other “needs empathy” job.
Stop spreading this bias nonesense.
llm_nerd
10 hours ago
What would you say you do here? - https://www.youtube.com/shorts/z4Xw6WMvfNk
Gen AI has changed every single part of classic software development, and the impact hasn't even remotely been felt. And zero jobs are "safe" in that traditional way that we saw them.
It's actually staggering to think of how the teams I've led developed software five years ago, ten years ago, fifteen years ago and twenty years ago. Easily 95% of that effort has been obliterated (I'm estimating on the low side, more like 99.5%). Classic wisdom like "the specification needs to be 100% up front because once we implement it stratifies" are relics of the past.
Everything has changed. I can't fully express how software development will work, but it certainly won't involve someone whose job is "human interaction".
iugtmkbdfil834
9 hours ago
:D Eh. We know how it is going to work, which is the more ability you have to stay away from the 'blast radius' as some llms would like to say, the happier you will be when it inevitably tumbles down, because a very, very confident manager thought they understood what they pressed Y for.
mono442
10 hours ago
I don't believe other jobs are going to be as impacted as software engineering. Software is unique in that regard that the results can be verified quickly and easily fixed. On the other hand nobody is going to try building a building only to check if it's structurally sound because that would be absurd.
mwwaters
9 hours ago
A sufficiently sandboxed, low-stakes thing that self-verifies by its visual output can be easily created by AI.
For security or applying business logic (and how it interfaces with programming or database logic), you get less and less assurance by just looking at it.
batshit_beaver
9 hours ago
> Software is unique in that regard that the results can be verified quickly and easily fixed
Neither of these statements are true if your team is building anything remotely complex with real customers. You can’t quickly verify if your decisions will survive the test of time and past mistakes can’t always be easily fixed. LLMs trivialize the easy parts of software development and enable faster enshittification of the projects they’re used on, but that’s about it.
groestl
9 hours ago
> the results can be verified quickly and easily fixed
Citation needed. Many of my users don't even know what correct would be.
> nobody is going to try building a building only to check if it's structurally sound because that would be absurd.
Well, that otoh can be simulated quite easily.
llm_nerd
9 hours ago
Paradoxically, gen AI being good at software engineering massively accelerated its impact on many other fields as a second order effect. Once generative AI could build code to analyze data, etc, its reach massively expanded.
> On the other hand nobody is going to try building a building only to check if it's structurally sound because that would be absurd.
Structural engineering isn't some mystical science. It's a set of mathematical truths, calculations, SOPs, and so on. If a human can do it, of course a machine can do it, and I'm obviously not saying "run it through the stochastic parrot and out comes a corporate headquarter building", but it's a part of the process where we're rapidly going to get there. And of course, the disruption in that field is already underway. For instance Stru AI. Yes, an engineer is still involved, but the premise is that your single engineer now replaces 10 engineers, and so on.
Gen AI isn't going to be plunging toilets or changing bedpans...yet...but it disrupts almost every role in the "white collar" world. That doesn't mean it eliminates every job, but it completely upends the norms.
lemonmelon
7 hours ago
[flagged]