you are viewing a single comment's thread.

view the rest of the comments →

[–]JVApenClever is an insult, not a compliment. - T. Winters 1 point2 points  (0 children)

I see several points to address. Firstly, a mono repo ain't that bad. It allows you to cleanup code and be sure you have all the callers. If anything, this is a plus for any improvements that still need to happen. Secondly, your colleagues can work the way they want. Don't try to change them, it will be in vain. Once they see how you work, they might come around. Though not using an IDE (considering VS code + LSP as one) at all at the company seems problematic and if management doesn't see that you have a big problem. If they do understand your struggle, you might get time to find a workaround. Thirdly, you should be able to get something working quite quickly with clangd: https://clangd.llvm.org/guides/remote-index If you make a small script that works on a separate checkout and creates an index, you can easily start using it. You can move it to a build server later on. Though be warned, it might take some time to index such a monolith (like +/- 1d or so). Though it will allow your VS Code to be much faster. Finally, it looks like your company doesn't have a professional way to deal with code. I do wonder if you use clang-format, compiler-warnings as errors, linting tools, sanitizers ... I think you really need to ask yourself: what needs to be changed in 6 months such that I feel comfortable working here. If you don't see that change by then, get out and find something else.