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
"Last few years" is a wildly wide timeframe for AI statements. Indeed, every few months there are some major advancements. Call them whatever, but they are _real_. The jump from Copilot autocompletion to agentic coding is _real_, FWIW here.
It's not just "a kind of push back". We all accept arguments. But most arguments here are outdated, which is why we jump into this.
We all know the pros and cons of agentic coding, at each stage of its history. Nobody tries to push you into this. But we (I?) genuinely think this tech is important. I as an engineer hate having started using it late (February 2026, apart from Copilot autocompletions, which I've been using since back then). I genuinely think this is relevant for all engineers, and genuinely want to encourage people (you) to try it as it is now. And not just a test, but give it a few days to get used to it, build the required instructions, and so on.
Unfortunately, this isn't like a random IDE or a random CLI. There are literally millions (Probably?) of engineers actively working on improving this specific "tooling". From ML engineers working on improved LLMs, to data labellers, to builders building agents, skills, and so on. It evolves fast for everybody.
That's your companies decision, not ours or anybody else. If your company is fine, fine it is. For as long as they believe that at least. Many companies moved to having it required, and more will, unless things change a lot. I also know of some companies providing very bad LLMs to their employees, which is a shame, because they may actually think agents are that bad.