32 comments

[ 2.7 ms ] story [ 45.0 ms ] thread
"What I see is a future where AI handles the grunt work, freeing us up to focus on the truly human part of creation: the next step, the novel idea, the new invention. If we don’t have to spend five years of our early careers doing repetitive tasks, that isn’t a threat, it’s a massive opportunity. It’s an acceleration of our potential."

The problem is that only a fraction of software developer have the ability/skills to work on the hard problems. A much larger percentage will only be able to work on things like CRUD apps and grunt work.

When these jobs are eliminated, many developers will be out of work.

This is a rational take, which is why it is wrong.

I agree that we're not about to be all replaced with AGI, that there is still a need for junior eng, and with several of these points.

None of those arguments matter if the C suite doesn't care and keeps doing crazy layoffs so they can buy more GPUs, and intelligence and rationality are way less common than following the cargo cult among that group.

> and keeps doing crazy layoffs so they can buy more GPUs

They're doing layoffs and giving a wall street friendly reason for it

The media eats the shit up because it's run by a bunch of people who hate the tech industry

I guess it'll work until the market turns around and it forces them to shut up or bleed talent. Which could be around the corner since the R&D tax deduction is coming back, or if interest rates start dropping

I am not worried at all. The C suite will very quickly find out that developers are still needed. And you can then negotiate a better pay + bonus to return.
Google search is giving us a taste of AI summarised results, and for simple things its passable, but ask a serious question and you get good looking garbage. Yes, I know its early days, but looking at the current output quality we have nothing to worry about. It will be used as calculators, offload some menial repetetive task which can be automated, but the next gen of developers will still be tasked to solve complex problems.
(comment deleted)
I just recently inherited a vibe coded project in iOS (fully created with ChatGPT), and not even close to working. This is annoying.
Quitting programming as a career right now because of LLMs would be like quitting carpentry as a career thanks to the invention of the table saw.
It's hard to see manual coding of web sites remaining a thing for much longer.
AI is a red herring. The current malaise in the industry is caused by interest rates. Certainly, AI has the potential to disrupt things further later down the line, but the present has already been shaken enough by the whiplash between pandemic binging and post-ZIRP purging.
> We are all, collectively, building a giant, shared brain.

"Shared" as in shareholder?

"Shared" as in piracy?

"Shared" as in monthly subscription?

"Shared" as in sharing the wealth when you lose your job to AI?

As this started with career advice, two points: the world values certain things (usually making people’s lives easier, one version of that is building useful tools) and the individual has a set of interests and skills. Finding the intersection of that for you should help guide you toward a career that the world values and interests you (if that’s important to you).

I’m looking at this as the landscape of the tools is changing, so personally anyway, I just keep looking for ways to use those tools to solve problems / make peoples lives easier (by offering new products etc). It’s an enabler rather than a threat, once the perspective is broadened, I feel.

Initially I felt anxiety about AI and it's potential to destroy my career. However now I am much more concerned about what will happen in 5 or 10 years of widespread AI slop. When humans lose motivation to produce content and all we're left is AI continually regenerating the same rubbish over and over again. I suspect there'll be a shortage of programmers in the future as people are hesitant to start a career in programming.
I wasted 2 days using Cursor with the 3.7 thinking models to implement a relatively straightforward task (somewhat malicious compliance with being highly encouraged to use the tools, and because a coworker insisted I use their overly complex mini framework instead of just plain code for this task)

It went round in circles doubting itself. When I challenged it, it would redo or undo too much of its work instead of focussing on what I'm asking it about. It seemed to be desperate to please me, backing down to my challenging it.

Ie depending on it turned me into a junior coder. Overly complex code, jumping to code without enough thought etc

Yes yes I'm holding it wrong

The code they create seems to be creating a mess that also is solved by AI. Huge sprawling messes. Funny that. God help us if we need to clear up these messes if AI dies down

It's not just the grunt work going to AI. Actually it is the opposite. Grunt work of dealing with mess is the only thing that is left for humans. Think of legacy systems, archaic processes, meaningless workflows, dealing with other teams and people, politics of work, negotiations, team calls, history of technical issues... AI is a new recruit that has massive general abilities, but has no clue about the dingy layers of the corporate mess.
Software engineers should unionize. We’re not real engineers until we have professional standards that are enforced (as well as liability for what we make). Virtually every other profession has some mandatory license or other mechanism to bring credibility and standards to their fields. AI just further emphasizes the need for such an institution.
I think a lot of people are feeling this, not just engineers. Engineering already has a high entry bar, and now with AI moving so fast, it’s honestly overwhelming. Feels like there's no way to avoid it—we either embrace it, actively or passively, whether we like it or not.

Personally, I think this whole shift might actually be better for young people early in their careers. They can change direction more easily, and in a weird way, AI kind of puts everyone back at the starting line. Stuff that used to take years to master, you can now learn—or get help with—in minutes. I’ve had interns solve problems way faster and smarter than me just because they knew how to use AI tools better. That’s been a real wake-up call.

I’m doing my best to treat AI as a teammate. It really does help with productivity. But the world never stop changing, and that’s exhausting sometimes. I try to keep learning, keep practicing, and keep adapting. And yeah, if I ever lose my job because of AI... ok, fine, I’ll have to change and try getting another, maybe different job. Easy to say, harder to do—but that mindset at least helps me not spiral.

> We are all, collectively, building a giant, shared brain. Every time you write a blog post, answer a question on a forum, or push a project to GitHub, you are contributing to this massive corpus of human knowledge.

I would be more excited about this concept if this shared brain wasn't owned by rich, powerful people who will most certainly deploy this power in ways that benefit themselves to the detriment of everyone else.

Sad truth is that we probably don't see any AI effects on hiring yet, or maybe only minimally so. For now, this is just normal cyclic shit. The worst is yet to come.
Why are software engineers paid well to date? Successful software uniquely benefits from operational and financial leverage. Which creates the term "software margins"

Financial leverage: It is cheap to write code, experiments are inexpensive. A million dollars in funding for a B2B SaaS gives many more shots on goal vs a million dollars in funding for drug research or manufacturing. This increases probability of ROI and permits aggressive investment.

Operational leverage: Scaling code is cheap as well. It is free to copy. Solving one problem with software well often enables solving immediately adjacent problems very cheaply.

Do LLMs decrease or increase the leverage here?

Writing code is cheaper, a single engineer can now do much more. Does that endanger engineers? Yes, if their job is "take requirements and implement to spec". No, if their job is "solve important business problems at scale". The former are already typically not valued or paid exceptionally highly. The latter are likely to be valued and paid even more than they already are.

Or put another way, if software engineers are going to be hurt by LLMs who is going to benefit? This is assuming a zero sum game which I would disagree with here. But if not software engineers than who is better positioned to wield LLMs effectively?

Well my company hired an american manager and now my job is in fact "do the tickets"… I just think it's done on purpose to get rid of the european office (where 100% of the product was implemented).
> What I see is a future where AI handles the grunt work, freeing us up to focus on the truly human part of creation: the next step, the novel idea, the new invention. If we don’t have to spend five years of our early careers doing repetitive tasks, that isn’t a threat, it’s a massive opportunity. It’s an acceleration of our potential.

Yeah, no that is always promised but historically this has never been true. On the contrary. Every technical revolution ever has brought great short term suffering to the majority and in the long term served to alienate people from their work.

It has been creative people, translator, writers, editor, artists, musicians who most fear to lose their jobs due to generative AI.

What is more fulfilling? Creating had crafted items or just being a cog in the assembly line? Writing your own code or micromanaging an AI?

Doesn't mean that progress is inherently bad but that it is a political question. Will the productivity gains allow us to work less and enjoy life more or will they make rich people more rich? Currently rich people are winning but the wind can change.

Coding was always a temporary profession.

Back 200 years ago, most people were illiterate. If you could read and write, there was work. You could become part of the machinery of the beginning industrial revolution, actually quite an important cog. Just by knowing how to read and write, someone would need your skills to coordinate stuff, mostly mundane. But it meant you had a way into a business. You might convert your clerkship into accountancy or law, or you would become a manager, knowledgeable about whatever business you were working in.

As time passed, everyone became literate. Knowing how to read and write stopped being the only thing you needed to get on the career ladder.

When I started working, my boss had no degree. He had energy, and he could do arithmetic. This got him a job as a young man running around with slips of paper in the LIFFE pit. Eventually he learned how option trading worked.

He got older and hired me. By this time, you could easily find a highly numerate graduate, and only such people were considered for finance roles. It was enough to have an Oxbridge degree and just sort of be smart enough to figure out coding on the job.

Now, when I look at the new grads, they blow me away. They can already code quite well. They already have internships in the business. They already have an idea of what alpha is, and how to find it. They are well on their way to just being quantitative trading professionals.

We are in an interim period similar to the expansion of literacy. The school system has not ramped up computer literacy in the way it successfully got most kids to be able to read and write.

Until there are lots of people able to code, there will be lots of programming jobs. That is, jobs where the person is in the seat because they can code. Much as in 1825, there were clerking jobs for guys who could read and write.

Or so we thought.

Now there is a tool that allows the business side to make code. It's not even that terrible code in my opinion, and it will only get better. It's here, and if you know what the business needs, you can use it to further the business goals.

The great divide that will open up is that developers who got into business because they could code are now in a bit of a wonderland. They not only know what code is needed, they can implement it without their friends who are further down the chain.

People who are just finishing a course in how to code, well, they face a bit of a struggle. On one hand, it's an important skill. On the other hand, for that skill to pay, you need to jump the gap that was once a stable existence. It might not be its own skill any longer, you might need the domain knowledge on a whole higher level.

I don't know where you find these expert new grads, but that is very far from my own experience.
> Look closely at every major breakthrough, even those in AI-driven medicine. It’s still humans pointing the AI down the right paths. Human creativity is the spark.

In the short term yes, but we're already seeing nearly autonomous agents get impressive results. It won't be very long until the average person can be that guiding hand, rather than a software engineer who knows how to code by hand and design software. This is good for the world, terrible for the software dev

Excellent blog post and thinking. We all need to create that personal and project context document(s) to benefit maximally from AI.
Stay away from CS. There are barely any jobs left and it will get even worse.

It's not only AI, it's rampant ageism as well where you are old late 20s for this field. It's a hype driven, youth obsessed career.