Business analysts are also incredibly vulnerable - why have a middle man if the machine understands your requirements in English/French/whatever?
Can you imagine how depressing it will be to your market salary?
The opinionated thing is how to implement these within the boundaries of the existing codebase, skills, etc.
Until we have ASI (imho we're not remotely close) then there is plenty of work to be done. It will just involve fewer menial tasks.
These tools will be incredible and change how we do work forever.
I've done the kind of heavy hitting active-active, five nines engineering you'd think would be safe. I'm not so sure that doesn't change eventually.
Providing detailed instructions to computers to accomplish human/business objectives is the hard part about being a programmer.
But the level of abstraction has been increasing. It started as physically flipping switches then machine code then assembly then structured programming then object oriented programming and so on.
I remember during the 1990s with objects and VB custom controls people were talking that businesses would just hire a bunch of high school students to work part time just snapping components together like Legos.
Prompt: AI, production is down. Fix it. AI: working...
3 days later.
CEO: Hey, dear contractor, our Production is down for 3 days - can you fix it ? Contactor: Sure, give me $500/hour and within 3 weeks it might work again. You know, you have 10mio SLOC, 1mio npm dependencies so it will take a 'bit' longer...
Yes, its bit oversimplified, but imagine it ;)
Being the person who comes in to salvage a software disaster is a hell of a different career than a greenfield cloud startup dev or FAANG proto-pusher, but it can be extremely profitable. and yes, I suspect the demand for that type of software expert will be on the rise.
145mn raised to date.
No demo at all.
https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...
Healthy skepticism is pragmatic. Sequoia and FTX comes to mind as well. Don't assume an adult was in the room doing due diligence.
This is how the majority of companies actually build and release products.
You do demos behind closed doors to investors/board before showing the public.
I certainly hope that’s the case. I really like programming and building things for money, fun, and status.
It'd probably be best if we all learned some agriculture and opted for simpler lives, rebuilt our social capital (aka community) and learned to do leisure like sane people. The rat race has never thanked anyone for participating, not even software engineers.
Of course, such a solution isn't impossible. It may be that such a village, if left alone by circumstance and/or because it has an insider champion, may create such psychologically healthy and intellectually talented people that they may eventually challenge the greater status quo. Sounds like the premise of a YA mild dystopia novel!
I think a realistic timeframe is about 15 years from the time someone releases a viable tool to complete replacement of the last engineer. About half way through the pressure on salaries will become noticeable. I base this guess on how companies typically operate and how long practical adoption of smaller technology changes take.
In the first half there should be both a downward pressure due to the threat of replacement but at the same time an upward pressure for the same reason. New grads will stop coming and existing engineers can look forward to being phased out and command a premium for as long as they can.
Another possibility is that it doesn‘t quite get good enough, but regardless students start picking other subjects, creating a temporary shortage that sustains existing employees. Employees will just be reduced through retirement with half being retired after 20 years of this process anyway.
Yet another possibility is that a half-assed tool only reduces demand - again that can be fixed through retirement plus less or no new people joining the field.
Would our industry create a new job role such as "prompt engineer" aka "ai engineer supervisor" ??
Or would this ai developer be able to read jira/kanban tickets, cooperate with other "teammates", deploy fixes, etc with no major oversight?
Generally curious.