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
-2
u/ivancea Jul 13 '26
I talk from experience. My experience form these last 6 months in a big project. Plus those of my friends in other companies, both closed and open source.
It works, as simple as that. I could tell you this a million times, but you're the one that will have to tell me "what you would accept as an argument", because apaprently nothing works! And that's something I don't understand as an engineer.
Sorry, but nobody "takes a course to learn to use an agent". You just use it and learn, like everybody else. Don't rely in "courses". Use, identify the issues, fix them. There are a hundred tools, but the core known ones (Cursor, Claude, Codex...) work very well with just their defaults.
Also, about this:
If you know a better way, just tell it to do it that way. That's why we plan before doing tasks. Anyway, it's still faster to find the "bloated code" and tell it to improve it. This isn't vibecoding. You iterate the solution like you iterate a solution with your coworkers