2 ms·
I suppose I agree with this, I try not to obsess over the tools too much. It makes sense to have a standard IDE and standard tools in a company. However there's
by jstimpfle 4y ago
I suppose I agree with this, I try not to obsess over the tools too much. It makes sense to have a standard IDE and standard tools in a company. However there's always a possibility to improve. One can suggest new tools to a small circle of coworkers, or just start trying out new tools on one's own. In one workplace that has a huge Windows codebase I compile and debug from within Visual Studio, and edit either in Visual Studio or sometimes vim. When I get the chance to do explorative work on a rather standalone project I gravitate towards vim, even to printf debugging, even though Visual Studio is available. I don't know why this is, old habits, or is it genuinely more economic on some axis - for new projects at least?