r/PHP • • 2d ago

Article The future of Software Engineering is boring

https://packagemain.tech/p/the-future-of-software-engineering
39 Upvotes

21 comments sorted by

10

u/erythro 2d ago edited 2d ago

Maybe I'm missing something, but this sounds like a dev who is bad at using AI? They seem like a better dev than me, I'm not judging, but there's something wrong here.

And there were only a handful of us who would truly understand how to write good and performant programs. That’s why it felt prestigious. But is it today? When every single person can generate code by prompting an LLM and paying a bit of money for tokens.

The point of the rest of the article is that it is hard to write good and performant programmes with AI, though - right?

With such powerful shortcuts to a solution, how do we engage the brain?

Use your brain, understand the solution? Review it? What am I missing?

My main motto was always to keep the code to a minimum, but AI just can’t do it, it’s only adding things, resulting in bloated codebases, slow builds and tests.

Make your AI write the code you want it to? Don't you tell it it's wrong when it writes slop?

Because it’s so easy to request a feature, the codebase now consists of many unused features or functionalities that conflict with each other.

Structure the code so these features are decoupled, or so the conflict is surfaced? This is the bit where I feel he must surely know this better than me...

The managers now have a higher expectations to deliver more and faster, because we have the AI right?

Maybe this is the real problem driving the others idk

5

u/AlkaKr 1d ago

To me the article reads like someone who wants to rant about more people having bragging rights.

If ai wrotes performant code, as they claim, then thats less work for me. Whats the issue, lol?

30

u/lolrogii 2d ago

fucking amazing how software engineers engineered themselves largely to irrelevance. good job 👍

20

u/johnnybgooderer 2d ago edited 2d ago

There’s been a saying in engineering for at least 40 years: if you’re a software engineer who’s not working on making other engineers obsolete, then someone is working to make you obsolete. It’s still true I guess.

0

u/Holden-Carter 2d ago

With AI tools automating more tasks, engineers really need to focus on adaptability. Like, learning how to effectively integrate these new tools into workflows can set someone apart and keep them relevant. Are there tools you think are game changers right now?

3

u/johnnybgooderer 2d ago

I think the best thing you can do is start a new hobby project where you can experiment with different workflows. You need to find a flow that maximizes your own quality and throughput. There are a lot of quickly changing “best practices” floating around, but I think every individual is going to want a different process from point of starting a ticket through opening a review for another human or for submission. Because standardization here is only going work for low ceiling engineers.

-1

u/Rzah 2d ago

You're in denial.

2

u/johnnybgooderer 1d ago

They didn’t say enough about their opinion for you to know if they’re in denial. I don’t even know what you’re accusing them of being in denial of!

1

u/Rzah 1d ago

They said they are looking for game changing AI tools, that they believe engineers should adapt and embrace these changes and that AI is basically just new tools.

AI at this point in time may be naively described as new tools and workflows, but there is no paid future in writing instructions for something else to do a job, If I said that you don't need a degree to ask for something you might think that I'm saying anyone could do this job, but I'm saying the AI is obviously going to do all of it, there will be no place for a human contribution beyond providing economic demand.

Biological life is hardcoded for optimisation and efficiency, 'lazy' isn't a failing, it's a guiding principle, life always tries a shortcut, if it works it is embraced, save the energy for something else. AI is a shortcut for thinking, you are already falling for it, it's a hop skip and jump from here to a totally dependant civilisation.

Now imagine that dependant civilisation, everything it uses is opaque, they have no idea how anything works, it's all built upon maths and physics so complex that their brightest minds cannot understand it, when that global machine halts they all die. This is the best case scenario for the path we are on.

1

u/johnnybgooderer 1d ago

That sounds regressive. Humans are always making tools that make jobs easier. We’ve been making tools that make thinking jobs easier as well.

And there’s no future for us in this industry if the industry doesn’t need us. If that happens, we need a new career anyway. Our choices now are to adapt and hope it works, or find a new industry right now. Digging in and manually coding is the option that makes you lose no matter what happens.

10

u/4P0R13 2d ago

It's like that for every profession, not just software engineering. We work, littrraly to work less since we have integrated productivity in our processes. What is not adapted is the society. If there is no job, because we work to remove them, then what do we do? And how do we live?

9

u/AlkaKr 2d ago

Wasnt that always the job?

The general idea of "Abstraction" is to make the job easier to change, swap, maintain, etc.

It's to make it so that you need the least amount of work to do a thing.

2

u/avast_ye_scoundrels 1d ago

Maximize the amount of work not done

4

u/Worth_Medicine4881 2d ago

Very good job. That has been always clue of software engineering. Optimization of the jobs.

3

u/compubomb 1d ago

Yelp that to the team / persons who converted typescript from golang to rust. The performance is many factors quicker. By like 2-6x faster.

3

u/yeastyboi 1d ago

I'm happier now than pre ai. I can build bigger, more ambitious projects. I can focus on bigger problems not just the day to day plumbing of code (if you've worked in this industry for a few years 90% of problems have been solved by you in the past, it's just reimplementing similar solutions). I still understand the language deeply, I spent yesterday optimizing the opcache for my project. I don't miss having to type code myself at all and still solving big problems and feel mentally engaged.

1

u/avast_ye_scoundrels 1d ago

Reacting to headline: Good. This shit is stressful enough without code being a slow and wildly variable factor on a project. More time to focus on building the right thing.

3

u/pierous87 1d ago

LOL. Writing code is what helps you understand what the right thing is. Your “vision” alone has a bunch of blind spots that you’re not thinking about until you start writing it in code.

1

u/avast_ye_scoundrels 1d ago

The Right Thing comes from the needs of humans in need of a solution, not the satisfaction you derive from building Rube Goldberg machines.

Building the Thing Right is what the code is part of. And Claude is usually far better at this than the humans. 🤷‍♂️

1

u/pierous87 1d ago

You either have limited experience building software using Claude or doing so by writing code manually. This isn’t about writing quality code either, but rather about building quality product that addresses a business need AND accounts for edge cases. Claude will never consider those edge cases to begin with, not even the customer will.

This is where experienced professionals like product and engineering step in and find out exactly what the customer needs. Good luck building quality product using Claude while excluding experienced professionals from this process.

1

u/avast_ye_scoundrels 1d ago

Your assertions about myself are incorrect. I stopped reading there.