top | item 46673046

(no title)

sky2224 | 1 month ago

Let me ask: in what way have you been proven wrong?

Have you simply just seen it build a pretty CRUD application that you feel like would take you many hours to do on your own? If that's the case, then you really shouldn't be too worried about that. Being able to build a CRUD application is not what you're getting paid for.

If you've seen something that involves genuinely emulating the essence of a software engineer (i.e., knowing what users want and need), then I'd ask you to show me that example.

discuss

order

atleastoptimal|1 month ago

Knowing what users want and need is more the essence of a product manager, not a software engineer.

Software engineering is solving problems given a set of requirements, and determining the value, need and natural constraints of those requirements in a given system. Understanding users is a task interfaces with software engineering but is more on the "find any way to get this done" axis of value rather than the "here is how we will get it done" one.

I'd say what OP is referencing is that LLM's are increasingly adept at writing software that fulfills a set of requirements, with the prompter acting as a product manager. This devalues software engineers in that many somewhat difficult technical tasks, once the sole domain of SWEs is not commodified via agentic coding tools.

veunes|1 month ago

That's a dangerous distinction in the AI era. If you reduce your work to solving problems given a set of requirements, you put yourself in direct competition with agents. LLMs are perfect for taking a clear spec and outputting code. A "pure" engineer who refuses to understand the product and the user risks becoming just middleware between the PM and the AI. In the future, the lines between PM and Tech Lead will blur, and the engineers who survive will be those who can not only "do as told" but propose "how to do it better for the business"

raw_anon_1111|1 month ago

> Software engineering is solving problems given a set of requirements, and determining the value, need and natural constraints of those requirements in a given system

That’s the description of a mid level code monkey according to every tech company with leveling guidelines and easily outsourced and commoditized before the age of AI.

ativzzz|1 month ago

Great, then we can use AI to solve the problems given a set of requirements, and spend more time thinking about what the requirements are by understanding the users.

PM and software development will converge more and more as AI gets better.

The best PMs will be the ones who can understand customers and create low-fidelity prototypes or even "good enough" vibe coded solutions to customers

The best engineers will be the ones who use their fleet of subagents to work on the "correct" requirements, by understanding their customers

At the end of the day, we are using software to solve people's problems. Those who understand that, and have skills around diving in and navigating people's problems will come out ahead