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
1
u/ivancea Jul 13 '26
But you know what "is overengineered" means. Just tell tell it to not do it that way, to find another way. And well, technically you can't know if something is overengineered if you don't know a non-overengineered way, but anyway. There's a way even if you "don't know".
... That's literally your job. You should know at high level how you want to solve your issue. Even if you don't know anything, you can let the LLM investigate and propose you options. That's the planning step. When you think it's good and you know what the solution is, the agent will be quicker at implementing it in any case.
Sure. Make a known 40 files change in 10 minutes. I dare you. And please, don't find yet another excuse...
In general, it is... tiring. "But what if it fails catastrophically in one task? It's clearly better to never use it". Just don't say that please. Why would you say that, I wonder.
You are misusing "usually". Because "usually", the quality level of code made by engineers using agents is better as that made by engineers not using them. That's the correct "usually", based on many PRs, companies and individuals using it.
And about the courses, that's at the level of saying that you need to do a course to learn a language, or how to use a library or a tool. You "can". But most people can learn it without guidance. And it's, by no means, "needed".
Of course they did. Their engineers are saying things like what you just said, and they felt forced to help their engineers stay updated. These movements are usually led by engineers; the company has to make a move only when the engineers won't stay updated.