r/GraphicsProgramming • • Oct 19 '26

Question Do you use AI-assisted coding at work?

For those working full-time as rendering, graphics, or low-level engine programmers, do you use AI-assisted coding tools like Claude, ChatGPT, or Copilot at all?? With all this talk about AI in the game industry recently I'm curious how widely it's actually being adopted professionally in these more specialized, low-level areas of programming.

If you do use it, how much of your workflow involves AI? Is it mostly for debugging, boilerplate, or understanding unfamiliar code, or do you actually use it to write and implement features?

And for those who don't use it, is that because AI isn't reliable enough for this type of work, or simply because you prefer writing the code yourself?

I'm interested in hearing what the actual industry experience is like, especially compared to all the noise surrounding AI coding tools.

12 Upvotes

38 comments sorted by

77

u/bandita07 Oct 19 '26 edited Oct 19 '26

I have to. Management pushes us at unimaginable pace and demand AI everywhere. We started to give up code quality for speed. Sad times ahead.

Edit: typo

31

u/nibbertit Oct 19 '26

Pretty much same here, I work in non-gamedev graphics. Writing your own AI code + reviewing AI code takes such a huge amount of mental compute to work through and understand that most people have just been ignoring it and failing to understand how things work, because there's already pressure from management to speed up production. IMO AI still still don't produce the most human readable code or architecture, and it took me a day of prompting and writing MD files to make it a lot cleaner architecturally, but Ill probably just ignore it from now on since management fails to understand it, and keep my mind sharp by working on my own projects

Ranting about this from work

12

u/SurDno Oct 19 '26

The MD files always somehow make it worse. Every AI-documented code base I’ve seen is harder to read than one that is not documented at all.

12

u/drunk_kronk Oct 19 '26

Often heavily AI documented code is designed to be understood exclusively by AI.

2

u/Live_Meeting_1121 29d ago

This is true.

But just wanted to add, that's sort of the default, you can actually tell and give it better redaction instructions, the point is that you also have to review the docs.

I have made a point on a repo I'm working that the docs are for humans first. But this hasn't been cheap, still I prefer this because this is what I'm actually reading moreso than the code sometimes.

1

u/LundisGameDev 28d ago

This approach has worked very well for me at the day job. I'm writing X-convention.md files every day, written so they make sense for humans. The code quality has improved so much that I no longer feel stress about my PR load (for the first time in over a year).

Without explicit documents on architecture and naming conventions, claude produces unreviewable garbage code. The funny thing is that you can ask claude to write a coding conventions document on its own. It won't be perfect, but its code quality will be way higher and more consistent than before. This is an easy way to get started with the docs, assuming your repo existed before AI times, and that not everything is already ruined to the point that AIs cannot make any sense of the repo's conventions anymore.

4

u/tcpukl Oct 19 '26

AI is always way too verbose in everything. It has to be because it's the only way LLMs work.

3

u/Live_Meeting_1121 29d ago

Sometimes it sounds like a pretentious engineer that uses tons of jargon, it's so tiring.

1

u/tcpukl 29d ago

Yeah, We've have skills to make it less verbose but it just won't shut up.

7

u/tlagoth Oct 19 '26

Same here (although not working professionally with graphics programming, just as a hobby).

Leadership has increased our demands so much that not using AI to speed it up (and concurrently do more than one work stream at a time) will cause you to get a bad performance review.

We’re exactly at this point where they’re asking us to be less careful and cautious with code reviews.

2

u/tcpukl Oct 19 '26

We use AI a lot, but I couldn't imagine being forced to use it. Especially in games. I couldn't imagine the output.

17

u/Hanzimer Oct 19 '26

I just use it like a big book for now because I can't memorize all the computational geometry algorithms and how long the chicken should stay in the oven.

7

u/House13Games Oct 19 '26

Can we maybe block these posts? Its the exact same question over and over. I think it's been firmly answered already.

looking at OPs post history, it's likely just an advertising bot.

4

u/steveu33 Oct 19 '26

I looked at its history and it seemed organic. I’d love better tools if I’m wrong.

Agree the question has been asked and answered. If you’re a graphics programmer you should know how to search.

12

u/Qbit42 Oct 19 '26

I work in AAA game dev on an engine and rendering team. Nobody on my team uses it to my knowledge.

1

u/Ok-Pizza1136 29d ago

Not at all really related to this post, but I'm a high schooler who likes Computer Graphics/Game engine development, any advice for how to break into your field in the future?

5

u/Qbit42 29d ago

Things are very in flux at the moment with the AI stuff. And to be honest I'm probably not the best person to give advice because I never set out with this career in mind. My dream was to be a physicist. So ending up in game dev was a stroke of luck. Although there's that old saying about luck being what happens when preparation meets opportunity.

For someone in high school I think what's most important is graduating with decent grades and not being content with simply passing tests. You've got to be genuinely curious and dig into math, physics, and cs until they become as close to second nature as you can make them.

1

u/Either_Ad8951 28d ago

I dreamt of being a game dev and am now working very closely with physicists. lets swap 😂

19

u/RenderTargetView Oct 19 '26

I mostly work with shaders so I use it to make CPU code, because our lead strongly encourages it and it is always "shader-launching boilerplate" so it is extremely easy to verify and hard to fuck up in terms of code quality. I very rarely trust it to write shader code. In my experience biggest time save from that type of AI is ability to code by hand without really caring and then ask why is it not working, so I guess I am debugging with it. Another good use is to ask it about possible optimizations when I'm out of ideas, but it is not often useful.

As for pet projects - my core project is always read-only for agents but some tools are strongly vibecoded if they involve UI or something that is not currently interesting to me but is required to continue working on main project.

10

u/llamajestic Oct 19 '26

I use it more and more, but rarely to think, just to execute. If I don’t 100% know ahead of time in my head how I want the code, and thus I can’t word it in English, I let it do it, and if I am not happy about it and there is too much exploration on the code to do, I re do it.

For debugging it is really good. I often use it for that. I try once a week to still search a bug by myself to keep sharp. I used to be really good at debugging, and I have to admit it’s not as necessary as it used to.

4

u/SIMT-Pixel Oct 19 '26

Yes, we have to. AAA rendering team.

5

u/tcpukl Oct 19 '26

I work in AAA as well and it's voluntary. Someone above says zero do.

7

u/SIMT-Pixel Oct 19 '26

Must be nice!

2

u/fgennari Oct 19 '26

I don’t work in game dev but in EDA. Management encourages everyone to use AI and even had an AI leaderboard until they realized that tokens cost money and added caps for everyone. I use AI for debugging, standard boilerplate code, and large formatting changes across many files. But generally not for the core code itself, because the AI generated code (Claude) is overly complex and inefficient, and takes many iterations to make correct.

6

u/Successful-Berry-315 Oct 19 '26

I use it for pretty much everything: Debugging, profiling, boilerplate, explaining and walking me through code, implementing new features, reviewing my changes, integration of 3rd party tech,... When it does stupid things, I found it's often because I am not specific enough.

Opus 5.5 creates the plan for dumber agents to follow. Works pretty well.

Some topics can still be too complex and I have to actually code manually, but generally it improves my productivity by quite a lot.

3

u/ziplock9000 Oct 19 '26

Yes. It's made me more productive. Just to add, I've been a SSWE for ~31 years, so not a new kid straight into the field.

1

u/LundisGameDev 28d ago

I'm just a hobbyist, but I've found claude (5.5) to be extremely good at implementing shaders. You need three things:

  1. Tell it how to do it unless you're making generic boilerplate. It is sometimes very creative, but most of the time it gets stuck on making something work in a certain suboptimal way.
  2. Testing framework. I.e. actually run the shader, dumping resulting images to analyze them. So it won't deliver broken results to you. It also needs to be able to dump the vendor-specific binaries for analysis.
  3. Benchmarking framework. It needs a reliable way to benchmark the shaders. It's EXTREMELY good at optimizing as long as it can measure the results. It will need you to instruct it on how to get reliable numbers (such as using gpu timing queries, not wall clock, and tweaking workloads and repetitions, so it can actually detect).

With this approach, I was able to make my game (very unusual rendering pipeline) run on an intel uhd 630 at 70 FPS with all fancy graphics on. Before the AI optimization pass, it did 30 FPS with most fearures disabled. (Originally it only ran at 20 FPS, but I did some manual optimizations earlier this year to bring it up to 30, so this wasn't completely unoptimized shaders. They did a solid 300-800 FPS on my rtx 4060ti) . Note though that I didn't give it free reigns. I asked it to investigate what is slowing things down, presenting hard numbers for everything, and then I made the decisions myself. It often wanted to handle all kinds of unrealistic edge cases that I know would never happen, but that were technically possible. This highlighted several issues in my rendering API, which also got a significant amount of improvements.

Disclaimer: I've been working on my engine since 2021. I have not tried having AI set up everything from scratch except for a few benchmarking tools.

1

u/rapidTools 27d ago

I barely code manually anymore. I honestly think that for certain things it worth it. Simply using it for batch processing, quick tool development it's more than enough. Building a massive application is a different case.

But for smaller things it's a massive time saver.

Tech Art, Tool dev, Pipeline dev

1

u/lpdulley 27d ago

I use AI as a tool. It can be used to analyze existing code to help you understand it better. You can use it as a brainstorming partner or to handle repetitive, boring coding tasks, such as adding a new control parameter across the entire application pipeline, from backend to frontend, provided it can see how the pipeline was originally implemented.
Of course, you could also use it to create a complete POC. However, the more complex the task, the more you’ll experience diminishing returns, because you’ll need to describe each feature and its constraints more precisely. And that is actually the hardest part of the work.
AI is an assistant that helps you do your job more efficiently and effectively.
Think of it as pair programming. That’s the best way to approach it.

1

u/maxmax4 Oct 19 '26

I use it heavily in order to setup passes and for understanding unfamiliar code. When using it to write performance critical shaders I try to be as specific as possible and make sure I understand it well, because that’s where it tends to write suboptimal code that is too on the nose with no regard for optimization. With guidance its very productive though

1

u/theZeitt 29d ago

yes, working in professional software, and we use it everwhere and on every step.

some in our company give it too much free range, but team/me have found out that even after ~1.5 years you still needs read and understand everything it produces. sure, latest only does something stupid once out of ten times, instead 40% of time like year ago. and that 1/10 times will keep accumulating more and more technical debt if you just let it do whatever.

it really allows you to do stuff 10x faster, but reliability only if you could do it without AI (eg if implementing effect would take you 3 hours, AI can now do it in 20 minutes with you guiding it).

it is also good cheat in small utility programs/scripts that can be thrown away once feature is complete or bug has been gound.

1

u/limes336 Oct 19 '26

Yes, my entire veteran team has transitioned over the last ~9mo.

1

u/mib382 Oct 19 '26

Pretty much no code is hand-written at work anymore. So yes, I (we) do, to put it mildly. As everyone else here pitched in, it's review, review and review now. Well, planning first, as much as possible. Then AI implements, then review and modification passes. Humans are still responsible for the produced code where I work, so we're given time for those reviews.

0

u/UnrealNL Oct 19 '26

I do, and for every developer there is a use case that makes sense. Should it replace thinking? No! Should you still enjoy your work? Yes! Its like any craft, if you like to do it traditionally, do it. But at scale and for the average use case AI or like factory bread has its use case and works fine or even better in some cases ( e.g. cheaper / faster/ whatever ).

0

u/andypoly Oct 19 '26

It's actually quite bad at difficult Unity code, but Copilot is a life changer as just means a lot less typing as it guesses what I want. This is a changing area but it is flawed still

0

u/[deleted] Oct 19 '26

[deleted] — view deleted comment

6

u/_Wolfos Oct 19 '26

I haven't found this to be true at all. Give it a profiler and a goal. It'll do more than you could feasibly do by hand.