I started building games on the side. AI tends to struggle a bit more on this, at least with Godot.
Programming
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
Teaching children to use computers and to program is difficult, but feels more like a challenge than a chore. I can only handle it two days a week, but I like that it doesn't involve LLMs much, and all the interaction feels very human for sure.
I’ve been a software engineer for a couple decades and was largely disillusioned before AI, but interestingly enough, LLMs pushed me towards what I consider a healthier relationship with work where I can more easily disconnect my emotions and pump out whatever is required to earn a paycheck.
After previously pouring my heart and soul into my work and then seeing my company get acquired by big tech, my team’s creations get enshittified, and most of my previous co-workers get laid off, this craving for “ownership” in my work I once had is gone. It has been replaced with an understanding that when you’re working for a company, you don’t own or ultimately control anything there, and you can and will be laid off at any time if it will make number go up. You are simply exchanging time for money. If companies want to pay good money for people to use LLMs to pump out drivel, then fine. Personally, I’ll reserve my best, most inspired work for my own time, thank you very much.
disinterested: Disinterested means unbiased, impartial, and free from personal stake or selfish motive.
We should be writing the code and the AI should be writing the tests and documentation.
If I wanted to be a technical writer or a tester; I would have been.
Sorry to all the technical writers and testers out there. AI sucks.
You don't want it writing the tests. They'll just pass
This is exactly how I use it. It does all the code comments, and documentation. I built it a lab on three old laptops (linux, mac and win), and one "powerful" (retired gaming pc) linux system. It builds the environments and tests the living shit out of everything, documenting everything along the way.
Unfortunately, most people and companies aren't trying to use it to better the quality of their output, they are trying to increase the speed and quantity of their output.
Hardware and firmware projects have been getting me excited for programming again! That's where I'm finding joy nowadays
I just let the AI do the work code while I fiddle around with personal or vanity projects. You doing actually need to sit there and watch it work. Just baby sit it as needed and understand that your labor and your passion will never be the same thing, and that's okay. We used to sell one for the other. Now you can just do both.
I only recently got a position as Junior Dev after graduating last year and working in a Support/Code Analysis position since then. Our company is on the smaller side and the executive team is definitely trying to push AI but thankfully leadership in the software department has been slightly more hesitant and are only providing it as a tool rather than requiring anyone to use it.
For me personally I have outright refused to use it so far because aside from my moral and ethical issues with it I find it to be a hindrance to my workflow. I end up fighting with it because it doesn’t get the solution right and I realize that I could do it in less time with a few searches online. I also realized that my understanding of the problems was suffering a lot any time I did use it and I don’t think it was conducive to learning new skills for someone as new to coding in a work environment as I was.
I don’t know what the environment is like for you but I would just try to avoid using it whenever possible because I find it much more enjoyable to write the code than to review and debug the output of the slop machine. If you can make the argument that you are more productive without it, do what you can to convey that to others. From my perspective as someone who learned to code in university and then was thrust into the AI hellscape without a job, I don’t see it being beneficial long term to have people cuck coding. I know I have a lot more to learn and I don’t think I will be able to properly learn what is needed by offloading it onto a glorified code completion tool.
dev/review skills won’t atrophy because you’re always reviewing the code
That's bullshit and the biggest lie.
When I read my first programming book (I was 15 or something), I was too anxious to compile the code and see the results (lots of psychological reasons for that). I read the whole book and in the end I said to myself "wow, I read and understood everything, I know how to program." Well, I learned absolutely nothing because you only learn from doing the stuff and making mistakes. There is no shortcut.
What I do now is learn the weirdest technologies, it's fun like it was in the good old days. For example: https://100r.co/site/uxn.html
As long as you know object-oriented programming, you can be an expert in C++, C#, and Java at the same time. It can become pretty boring, even more if they force you to use LLMs.
when the US outsourced manufacturing, its domestic technical skill base (machinists, welders, etc) atrophied. Today, some are attempting to redevelop these skills and it may take a decade minimum.
Its a cautionary tale. I would say try to hang on until the AI bubble bursts and then advocate for keeping a healthy domestic skillbase
A lot of those skills won’t come back or they’ll be more specialized.
My friend works in auto manufacturing. He welds truck frames. Except he doesn’t weld by hand at all, he uses robots to do all the welding. He can supervise a whole team of robots and adjust them to deal with flaws as well as set them up for new jobs. As one person he replaces a whole team of welders.
Now don’t get me wrong, there still are lots of manual welding jobs out there, but a lot of them are specialized into custom work or in complicated scenarios (underwater dive welding on oil rigs). The standard manufacturing line job where you perform the same welds over and over again is a thing of the past.
Welding a frame is a repetitive task, and the robots are deterministic. Programing is not repetitive, every problem is different and takes creativity, and LLMs are not deterministic.
I used to say that for a long time. But I am starting to doubt it’s gonna burst. I mean the valuations are probably way too high, but we’re never going to put the cat back in the bag. Programming is changed forever with AI. I’ve been a programmer for 25 years professionally and I am working on integrating AI in my daily work routine. I see it this way: We’ve had tools for decades that helped us write code. When ReSharper was introduced many years ago it was able to speed up writing code for all .NET programmers by suggesting snippets of code or performing large refactoring for you. Obviously AI is a whole other level, but it’s still just a tool.
I was never particularly proud of how much Stack Overflow I had memorized anyway. That wasn't the fun part of my job.
Most of these companies pushing AI so they can show half their devs the door are insane. You can't just vibe code shit and expect results other than a full airline ground stop and Microslop Office being down worldwide.
The AI is pretty worthless without me. I have zero concerns about being replaced by a project manager. Companies are being sold something else, but they're gonna figure it out pretty quickly. (Though not quickly enough for some of us. Negotiate to keep your tenure and severance when they bring you back .)
But AI as a tool is here to stay, and it's better to build those skills earlier than later. The Riemann hypothesis shows a bit of a model for future work, both good and bad. You can't just tell AI "solve the Riemann hypothesis". It would have gotten nowhere without the expert guiding it and using it as a tool. Fortunately most of the stuff we're doing isn't cutting edge research, so hopefully we don't have to deal with a pile of slop that we can prove is correct, but nobody understands how.
Out of interest, how do you recommend someone learn to use it as a tool and not over rely on it?
A couple ideas here:
- Keep coding your own stuff on the side.
- Don't let the AI give you code that you don't understand.
- Understand the greater architecture of what it's building.
- Be specific in your instructions.
Yesterday I was using Copilot and Claude to write a clone of the old trn Usenet newsreader in Rust. Got pretty far in about 7 hours. 8300 lines of code and 8300 words of design docs in Markdown. The architecture is pretty good, and the thing works. (Still missing is the thread graph display and posting, but I know those can be added without breaking anything.)
Don't get me wrong: if there were a button that destroyed LLMs forever, I'd have already pressed it. I have other projects that I write by hand even though LLMs could definitely do it because I like the challenge and I want to stay sharp. Reading code doesn't do it.
Yeah, I don't have a good answer for that. I've seen how easy it is to get lazy and just vibe with whatever it's putting out, in others and myself (sometimes).
The worst is when it's clearly not working and the person just spins the AI in circles with "well, fix it" over and over again.
I do think we have a history of looking for black and white answers that has bitten us in the ass. "Not invented here syndrome" led to the npm dependency hell, for example. There's a middle ground. log4net and whatnot are great third party tools that should absolutely not be reinvented yourself. But maybe you should have handled Leftpad on your own.
Unrealistic but fun ideas:
- unionize
- Collect/learn as much as possible about your employer's/customer's industries, client relationships, etc and start your own business stealing their customers
- Outsource your own job to some contractor for a fraction of the pay, so you don't actually need to work
- Sabotage by using as many tokens as possible to burn through budgets, massage prompts/agents to be as verbose as possible, poison long prompts, etc
- Find a new job
Whatever you do, don't let the cognitive decline set in.
No. Quit. Do it now because do you really see it getting better? Is there gonna be a profitable anti-ai wave? Fuck no. Sorry bud, I also am angered. But anger should be let go.
Breath in, think about other careers, breath out, know that billions of people significantly dumber than you somehow make money doing the task of a robot, and that all you need to do is properly frame your resume for transition. I know, easy said.
If you love programming and you want to keep loving it, just make that what you do for fun.
I don’t really program outside of work
Until that changes, there is nothing you can do and I have no advice.
Your problem is with your company, company culture and your boss. Not that much with coding.
The biggest issue is that the people in a position to influence hiring are also the people who are having AI touted as a way to lower their hiring costs.
So it’s rare you have people with enough power to push back AND care or want to.
I hates it.
You can say "no". It'll likely lead to you losing your job, but if you hate it anyway, might as well try something new.
There are still programming jobs not hit by the ai craze.
In the US at least, someone got it protected as a religious class, so you can’t be fired for refusing to use it. There were some exceptions though. But overall good.
Welcome to the orphan crushing machine, you’ve hit the point where you understand how computers work and your boss(es) don’t. To the point where all your boss(es) see is number go up - Profit/LOC - and that’s their direct metric to productivity even if the two are completely unbounded from reality.
I just feel like I’m supposed to be a rubber stamp on the output.
Nah, your role is not only that. You are also the one who's gonna be blamed if/when things go awry, and the one who'll be called to fix production on a Saturday night :)
Jokes aside (hopefully it's just a joke), I don't see may options... If you think things are gonna get better in time, you can try and endure it. If you don't, you can try and switch to a different job (company and/or position).
The bottom line is you don't enjoy doing what your boss pays you to do.
That the reason for that is the company "AI" policy does not really change this.
what's happening is that everyone is advancing to middle manager/product owner. to them, code that works is better than code that doesn't, even if the reason it doesn't work is that the developer is taking care that it works right. if you enjoy management and spec-writing, you'll be fine. if you care at all about the process of building software, you are just not going to enjoy the coming few years. there is nothing i can say to help.
if you want your skills to stay fresh, you need to the stuff you actually enjoy outside of work, at least a little. think of it like any hobby that you spend a few hours on every week. i'm trying to pivot to that by looking for jobs outside the software field.
Well don’t just rubber stamp. And do use the ai, ask it questions about the code, make it explain itself, try to beat the ai solution and find its errors. I know it can be annoying to read ai code but it can also be fun to choose the parts you want to spend time on understanding, as opposed to hand-coding all the boring parts too.
While the AI is churning away at everything that's needed to be built, if you have the time, choose something that you want to build or tech debt you want to fix and work on solving that the old way that you enjoy.
When the company I was at was pushing AI first they told us to carve time out on a Friday afternoon to work on something AI related. I found over a couple of months more and more was being shifted to AI first that I decided to flip it, and use that Friday afternoon to not use AI. Once you get started on something, you can continue with that whenever you're waiting for the AI to churn some stuff out. Context switching can be a pain but it'll allow you to keep doing the thing you love.
We programmers were never meant to write code. We were meant to automate tasks and solve problems using computers. Nothing changed in that matter, just tools are different
Maybe I just have a different set of interests/motivations here, but ...
I've been in the industry for over 20 years. First job as a programmer in 2005.
I have never been more excited/motivated/energized than I am right now.
The amount of stuff I can get done is absurd. Projects that have been collecting dust in my backlog for years are shipping. Tedious tech debt and inventory/audit concerns just fall away. I feel like the scope of the work my teams can take on is an order of magnitude larger than it used to be. Stuff that was "well that's a cool idea but we'll never have budget or time to do it" is now "fuck it I did it over the weekend with AI."
The world has changed dramatically but I don't think it's all bad.
Sounds like a person who has lost the love of the game.
Or a manager.
Wouldn't say I "lost" it.
Writing code was never the thing that really interested me. I like solving problems and analyzing and designing systems. Code was just a means to an end.
This is what enabled Altman and Musk to continue to grow and consume, eventually purchasing and monopolizing all the world’s chip manufacturing. All humans where forced to mortgage all their information through Elon, who’s Grok AI would debank you if you spoke out against him. Eventually he left for mars, and did not make it. His pantopticon shut itself down and no one could access any information any longer, including things like how to repair farm equipment or how to access bank accounts. Much of the world’s population, who had specialized ona single job as was done for centuries, tried to come together and keep things going but it was of no use. A great number died, humanity reverted to the Stone Age.
But I’m glad your hentai calculator is finally in RC or whatever
But I’m glad your hentai calculator is finally in RC or whatever
Truly an obnoxious response.
Honestly, I do work that I actually believe in, with a mission that means something to me and has positive real-world impacts, at an ESOP company.
"Getting more stuff done" is actually important to me.
Imagine you're John Henry. You're a black man in an era where you're viewed as scum feeding yourself by making steel sing with a hammer.
Now imagine the rail boss tells you instead of getting jacked pounding steel all day, you're gonna watch a piston slam-fuck your passion away for 10 hours a day.
More tracks are laid down. More trees leveled. More "stuff" delivered.
But is there anything to be proud of?
At a certain point progress needs refinement into a measure of the nurtured soul rather than pumping more shit out of humanity's butthole.
Of course you're not passionate. It's a fucking farce.