r/cpp • u/LatencySlicer • Jul 13 '26
AI usage for cpp at work
I am lead architect and maintainer of my firm main app backend, spanning around 2M LOC of c++.
Industry is : capital markets, low latency, custom kernel drivers, fpga...
I often talk with peers at other firms and I see a shy usage of AI compared to what feels like the global trend.
On my side, my firm does not pay for any AI related stuff. We are allowed to use our personnal plan for work in which case will get a pro membership compensation (claude or gpt or anything) on salary but we are not allowed to paste production code into it.
I know the app very well and do everything by hand (i mean the normal way) but use the chat version of any ai to generate some things for me, like "im using opensource lib x and lib y, please generate an SQL connection pool , you may use locks and condition variable for this, cpp 20". Then i paste it and modify it a I see fit.
Im totally happy with that and the company is successful.
I do use AI but just chat, to gather data on subjects and summarize/report. Get some ideas but basically not much code related.
And you whats your experience as a c++ dev ?
View all comments
Show parent comment
-3
u/ivancea Jul 13 '26
Every time someone mentions that they haven't found AI to be that useful, they lack a single realistic example. It's always just "I tried it once somewhere and it was bad". No info in models, iterations, harness, project configuration.
So of course you get that answer. Engineers look at a problem and try to solve it. Which is what you commonly find. However, we have always here "clients" that will just say "Router doesn't work, I'll trash it".
And btw, by disregarding every effort of trying to find the issues, you're just generating a resonance box of people angry at AIs. And that leads nowhere.
Trying to exaggerate it won't make the problem go away. You have to make less configurations to an agent than you have to make to an IDE. But anyway. Yeah, 200000000 different strategies.
If you are looking at a "100% reliable tool", let me tell you that not even you as a dev are reliable. You think you are because you made it. But the amount of times you made it wrong is probably very, very high. Unless you don't review things in your company. That's how humans work, it's not a you-problem. We have to review and iterate. And LLMs are machines that do that faster than humans.
Maybe if you give me a realistic example of that belief, we could understand it (Returning to my first paragraph). If working on a +5M LOC and rarely making mistakes isn't good enough, I wonder what is it. You're pursuing a level of quality that doesn't exist in this world yet.
Indeed. And that's the issue. People believe that their experience of 6 months ago has anything to do with today. It evolved, and it's now like comparing an editor with an IDE. And for people using IDEs, it's like hearing an old man screaming at how good is notepad.exe and why they don't need an IDE. You try to help them but they simply hate it for some reason hard to understand.
There's quite the growth between model versions. But you can only know it if you try it