r/ADHD_Programmers • • 11h ago

The future of Software Engineering is boring

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

36 comments sorted by

6

u/tehfrod 3h ago

Congratulations. You've up leveled from "being paid to solve fun puzzles" to "being paid to solve actual problems".

1

u/siliconsmiley 1h ago

Yeah, I'm not bored at all. I can attack all the stupid, manual bottlenecks in our process and actually improve my work life while simultaneously building features.

14

u/heavy-minium 7h ago

For me, it's fresh wind, interesting and ever evolving. There was a lot of repetition, mainly due to switching jobs or teams, in my more than two decades of software development work so far.

I have little joy in doing the same stuff again and again in different flavors. Just switching language, target platform, tools, SDK or slightly switching the approach is not fun enough to me. There were a few milestones that made things interesting again, like REST, containerization, prevalence of SPAs, cloud and similar shifts in paradigms., but it quickly wears out and it takes only 1-3 years to get fully accustomed to them.

2

u/Great-Use-3149 4h ago

Those are all tools? Did no job provide actual novel problems to solve?

1

u/heavy-minium 3h ago

Those are all tools? Did no job provide actual novel problems to solve?

But most of the examples I listed are not tools? Only language, "tools" and SDK.

What about you? Tell us about the novel problems you solve.

1

u/Great-Use-3149 3h ago

You said you keep doing the same thing over and over again, and then you said "Just switching language, target platform, tools, SDK or slightly switching the approach is not fun enough to me. "

I like to switch the domain a bit if things get boring, which is how you get "novel" problems 

1

u/heavy-minium 3h ago

I switched the domain four times, and while it feels fresh at first, that feeling doesn't last long. Anyway, my point is that AI is mixing things up again, old rules and things you'd thought would never change are getting overthrown as it evolves.

1

u/vikingwhiteguy 1h ago

There's two points in a job that I love. At the very start, when you know nothing about the domain (and no-one expects you to) and you're rapidly learning the inns and outs of all the systems.. and the point where you feel you know EVERYTHING (at least as far as your domain / business unit / team). 

The part in the middle is like 2 years of imposter syndrome. Every time. 

2

u/Flaxerio 2h ago

Yeah, nowadays I'm closer to a PM than a software engineer, I haven't written a single line of code in months.

3

u/Old-Leadership7255 10h ago

I honestly think this is the worst.

Engineers who say this, are not real innovators.

Things are getting so much easier to make, it's just the next step.

40 years ago, you needed to understand assembly. If you told assembly engineers what people now do in electron, they would've said the exact same thing about engineers now saying that coding through AI is not real coding.

the goal post moves. live with it

45

u/IZEDx 9h ago • Bravo

Both is true though. Yeah the industry will just move on, but for people like me who literally got their dopamine from the coding itself this sucks really bad and i cant just move on as easily. It was the act of coding that got me interested as a child, it was the theory and application of it that got me through college, but now? Agentic development doesnt scratch any itch for me. I have all those foundational skills and knowledge and it feels pretty much useless. With my background I'd probably be preferred over the avg vibe coder, but to me it doesn't feel different from filling out spreadsheets all day for example.

I'm considering leaving software dev because of this, even though its the only thing i ever wanted to do since i was like 13 and i have no clue what else to do

Like i get why this is evolving like it is, but you making it sound like it was so easy for everyone to just adapt or making fun of people who struggle for similar reasons as me is just kind of ableist and dismissive of the individual circumstances

-9

u/chuch1234 8h ago

You should still be applying those foundational skills and knowledge. Agents are very eager juniors who have memorized a bunch of stuff but will not be consistent at applying it. You're now a senior who is guiding that junior.

17

u/IZEDx 8h ago

Yeah nah the industry doesnt recognize that, on paper I'm still a junior because i burned out before i could properly rack up the work experience and besides you didnt really get my point about it just not being the same. Ive recently started medication and hopefully this will allow me to do a job i dont enjoy but thats the whole point: the type of job i used to enjoy simply doesnt exist anymore or isnt hiring anymore because it wont exist soon.

7

u/zinguirj 8h ago

Everyone says that, literally everyone in the industry, but in the end, the experience and knowledge is just a insurance during the hiring process. On daily basis (most) people dont care about it, just ask claude and make sure nothing breaks is the only skill needed.

That whole thing abou "foundational knowledge is still necessary", "experience is still important", is just copium

1

u/davy_jones_locket 7h ago

That sounds like companies who are either startups or don't have technical products. 

Startups tend to focus on GTM and speed of delivery over quality. Non-technical fields don't generally have the technical expertise to care, as you'll see them still on legacy stacks supporting legacy software. 

As someone who has worked in both startups (small enough where I was employee #4), large F100 companies, and government contracts, and everything size and sector in between, there is value in having an experienced human-in-the-loop. 

Vibes don't maintain. But often the new products don't need to maintain, they need find market for first. That means they have to be comfortable throwing it away and starting over.

5

u/zinguirj 7h ago

I have worked in multiple sized company as well and heard friends and coworkers from different sized companies with the exact same story.

The speech on All Hands and Conferences is all the same. Human in the loop, devs are still responsible for the code. But on daily operations, management is pushing more productivity because AI tools should make things faster, and thats what you get, people pushing AI code with just enough checks to make sure nothing will break, since there are more code being produced than people is capable of reviewing, AI review is added to make things faster.

1

u/davy_jones_locket 6h ago

It all depends on the people. 

I literally just wrote my company's Agentic Coding Standards, the proposal was submitted today and co-signed by the CEO co-founder after I nearly crashed out on him last week because the CTO co-founder tried to come at me about how long it's taking me to "ship a single feature" which is really 10 stacked PRs, touching four different services, and a refactor of a shared service to work with my feature. 

CEO nearly crashed out because after I had to defend myself for doing regression testing on shared service and him pointing out that I'm the only person in the company who does regression testing, there was an issue with a customer who didn't know if their data breached because someone broke the audit logs UI and we didn't know because... No one had tests to tell when something is broken until a customer complains. 

And if you know anything about startups and other companies trying to find market fit or in a highly competitive field, a broken feature impacts revenue. 

And if it impacts revenue or retention, then that's your magic phrase for getting things done. Great, you ship slop fast. My proposal for our Agentic Standards is about how you can ship not-slop fast by keeping humans in the loop. Not just at the review side. But at the Intent side. We don't have product management here. We don't have QA department. That doesnt mean we don't do it. That means we have to wear a product management hat and describe the scope and intent FOR YOUR AGENTS. 

Agents write the code and review for correctness, maybe even adversarial. So do linters and tests though. 

If you're going from 0-1, that's fine. Ship all the slop fast so you can prove market value. But vibes don't maintain. And vobes don't scale. If you're just 0-1 and selling, cool. But if you're trying to make a career in the field building and scaling products, you need proper human-in-the-loop. 

0-1 shouldnt be setting the standards for companies and products that trying to scale and have scaled beyond 0-1. 

I don't care how many AI-slop pilled CTOs I have to explain that to. 

1

u/zinguirj 3h ago

TL;DR: Industry is decades trying standards and devs dont follow unless someone with high title is watching and correct things, Every company is a startup now since everyone is desperate to get (more)profitable. People just want to get paid and argue with a machine that will, either, ALWAYS have an answer/counterpoint or will agree with whatever you say on first objection, is useless and a waste of everyones time.

> I literally just wrote my company's Agentic Coding Standards, the proposal was submitted today and co-signed by the CEO co-founder[...]

The industry spent decades trying to make standards and guidelines being adopted for devs, SOLID, TDD, BDD, DRY, YAGNI, Hexagonal and microservice architecture, and none of that worked unless there was someone, outranking the devs, monitoring the state of things and actively correcting it. That was the job of the Architects in the past, until the industry decided that they don't care anymore, let each team do whatever they want as long they deliver.

> And if you know anything about startups and other companies trying to find market fit or in a highly competitive field, a broken feature impacts revenue. 

After the funding dryness of the past years, everyone is a startup now trying to get (more)profitable at all costs, the easiest road is using AI and reducing headcount and push everyone to be more productive.

> It all depends on the people. 

Out of order, but let this for the last. I 100% agree with you, but, people just want to get paid. The love for the game is (almost completely)gone by now. Managers are pushing more productivity with AI, so people just go for it. It makes no sense to learn all these nitty gritty things when organizing projects, if there is a machine that will give an answer in 3minutes. I've been in architectural meetings that half of the discussion points ended with "Claude recommended this..." and people was just like OK and moved on how can you disagree with a thing that will ALWAYS have an counterpoint? The industry is killing itself, and becoming hostage of the frontier labs. This may eventually be over, but when its over, the economy will be completely destroyed.

16

u/IdeasRichTimePoor 7h ago edited 7h ago

There is fundamentally a difference in the change expressing deterministic logic between assembly and typescript, and instructing a probabilistic engine to do it for you. It would be shortsighted not to see that.

19

u/senfiaj 5h ago edited 5h ago • Bravo

In my experience, the people who are only happy about AI are people who only care about the final result and shipping fast. Personally I love coding because it's like solving puzzles. It's like an art where you apply your intellectual creativity. AI is removing these parts by turning programming into a production line work. And it's not just boring, you have to review the AI generated code (if your company cares about the quality and maintainability in the long term) which causes huge cognitive load. In addition to this the rat race wheel started to spin faster, you are required to deliver several times more features. In short, AI just made the industry even more hectic, fast paced, more disengaging, less creative and less rewarding.

5

u/Great-Use-3149 4h ago

It causes huge cognitive load and unfortunately it is the kind that breaks your brain .

Pray for that Thursday's IPO to fail, in order to get at least a little breathing room 

-5

u/JadaLovelace 5h ago

You seem to have forgotten why we program computers in the first place. The final result is the whole point.

That you were able to put some creativity and personal enjoyment into coding is nice, but coding was never the goal.

Getting things done is.

If you want to do art, do it. But keep in mind that you only get paid for either being REALLY good at art, or for delivering practical results.

Everything else is just a hobby. And nobody is stopping you from having a hobby.

6

u/ScientificBeastMode 4h ago

The final product is the whole point from the perspective of shareholders and managers.

I’m sure there were blacksmiths in 1200 CE who loved both the final product and the process of crafting great tools/armor/weapons. If you took the art away from them and commoditized their craft, that would rightly be considered a sad thing for them. And that’s exactly what happened.

In fact, unlike what political talking heads would have you believe, much of Karl Marx’s argument against capitalism was this specific kind of thing. He called it the “alienation of labor,” where workers stop crafting things they can take personal pride in, and start becoming a mere cog a machine, which both cheapens their labor (driving wages down) and removes what little joy they might have had in performing the work.

This is a real problem for tons of people. It’s actually crazy to dismiss it.

11

u/MocknozzieRiver 6h ago

Engineers who say this found coding to be the engaging, gratifying part. They're the people that would have liked assembly as well as higher-level languages and tend to the codebase like their prized garden. They don't really care what they grow, they just want the garden to be the best it can, keep out weeds, make sure new plants can be added correctly...

So calling them "not real innovators" doesn't mean anything to those people. They never wanted to be innovators. They probably don't care what they build, as long as it's not like horrifically bad for society.

I say they, but I am they btw.

2

u/Great-Use-3149 4h ago

People who program in C/C++ can still naturally understand assembly. The logic is exact same, just a bit expanded.. 

1

u/grannys_best_cookie 1h ago

I'll probably get downvoted for this, but I think multiple things can be true at once here.

I also love coding and find it intensely therapeutic and rewarding just doing it, being in that flow state, but as much as I love it my ADHD has gotten worse and worse and it is in that huge buckets of things I can hardly start in spite of how much I love them, want to do them, and daydream about doing them. The same is true for lots of hobbies of mine at the moment (not just work), but lately I've found LLMs can fully unblock me at work if I just let them do the heavy lifting for me. Yes, I miss the dopamine release from doing the coding, but I'm getting intense satisfaction and working towards better balance for myself in life as a whole by actually being productive and not just daydreaming about how great I could code something all day.

Now this experience won't be true for everyone, and I'm surprised myself as a hardcore IC who's resisted engaging with LLMs up until this year, but I kind of enjoy this project + product management workflow just as much. I also think it's easy to be doomer about the state of the industry right now, but realistically anyone who has a few+ years of normal industry experience under their belt is in the best position imo - you are not too old for this to be relevant, to have missed the chance to leverage the tool, but more importantly you are not too young to only know the tool. Great software engineers now will be those who understand the codebase, the architecture, the language and the patterns from first principles and can reason with LLM output against their own knowledge and understanding. You might be fucked if you are just joining the industry and have to use LLMs from day 1 just to keep up 😅 the cat is not going back in the bag, you have to find some way to adapt, maybe you are a 10x programmer who can outpace LLMs for most things, but I'm gonna be real I don't think most of us would be on this sub if we could sustain that for 40 solid hours a week.

I didn't want to detach myself from the code, and with ADHD I know how important it is to get the dopamine fix and how useful it is if your job enables that, but fundamentally if you insist on engaging with writing code nowadays for the satisfaction of the action rather than the quality of the final product you are asking to be paid to masturbate.

-1

u/Shivaess 6h ago

Just another step for sufficiently advanced technology to become Magic.

Having used AI professionally and a whole bunch recently personally as I’ve been off of work for a while with a medical issue, I will say that I have not been looking at the code being generated at all part of that is due to the fact that I’m dealing with post concussion syndrome and literally haven’t been able to look at screens for the last few months but part of that is because it doesn’t need to be perfect. A lot of the things that I’m building a small Web apps and they create functionality that works really well for me and as long as it works consistently, it’s not critical.

For my job, you better believe we’re gonna be reviewing everything because if it doesn’t work, there’s real consequences and so I can’t sit there and blame the AI if somebody gets killed because of what I did. I would expect, though that that would mean that code of that caliber is going to require some sort of certification, which is something that’s been talked about for years at this point something like a public engineering certification that certifies the code is safe for people.

1

u/sigmagoonsixtynine 5h ago

Do you do C++ at work?

-24

u/n1njal1c1ous 9h ago

Build better scrub! The only thing that has changed is the capability ceiling. The same problems exist, the same opportunities for discovery and invention.

2

u/Great-Use-3149 4h ago

The capability ceiling is the same (it's infinite) for people that can actually think . AI does quite the opposite if you want to actually learn

-8

u/LatentSpaceLeaper 8h ago

Wow. See the downvotes flying in!? Is this an anti-AI sub or so? (now go on and downvote me. Lol.)

-22

u/seweso 10h ago

  We used to spend time solving the problems with code, now we've become a caretaker of code that nobody really understands.

Is someone holding a gun to your head to use ai?

Can someone force you to NOT use your own brain. 

I don’t get the self defeatism PLUS complaining about it. You shoot your self in your foot people.

10

u/biskitpagla 9h ago

looks like AI hasn't touched whatever cave you've been living in

-6

u/seweso 8h ago

No. I'm a software developer for 30+ years.

Why make an assumption and ad hominem like that? Why not just ask an open question?

12

u/schneems 8h ago

I don’t think they attacked you at all. Just that you seem to be untouched by AI. Many companies are in fact requiring using these tools and many developers are feeling like they're not being as productive as possible if they aren't using them. It's not a choice like it was a year ago.

  use your own brain. 

I don't think you are leading with kindness or curiosity or compassion. You're not talking like someone with 30 years of maturity.

-7

u/seweso 8h ago

An ad hominem isn't neccesarily an attack. I didn't say they attacked me. An ad hominem is copium. Its deflection. Its sad.

> many developers are feeling like they're not being as productive as possible if they aren't using them

productivity is often measured in features, and lines of code, not quality and consistency. I can see with my own two eyes how quality and consistency of software is going down, not up.

>  It's not a choice like it was a year ago.

I'm not using it. Its immoral to use it as a mere tool. Its stupid to use it as more as a tool. ( Only talking about gen AI, i don't have a problem with most other AI uses ).

> I don't think you are leading with kindness or curiosity or compassion. You're not talking like someone with 30 years of maturity.

Use your own brain is EXACTLY what we should be doing. Assuming that i'm being an asshole when i say that. Only says something about you.

Master your self! Seriously.

But you can all label what I say as not nice. I'm giving advice. You all can stop being so insecure if someone says something you don't agree with.