[Myrddin]

Tools like CodeScene are like a scalpel in the hand of a surgeon. Intelligent interpretation of results is a part of the process. Another tool I like is "Understand". It does a fine job of ingesting and diagramming code. Very important when I'm bidding on a proposal and trying to make reasonable estimates of the effort to maintain or repair a body of code that the request for proposal cites as a substantial target of the effort.

My work today consists of wrapping prior standalone server environments into reusable docker containers managed with kubernetes. It's a lot of work to package the containers in a reusable form and make them capable of being tailored to the needs of the end user community. I miss the joy of writing ultra compact DSP code to run in a tiny processor. A developer on my current team needs a minimum quad core I7 and 64 GB RAM and 2 TB disk to run the VMs and kubernetes clusters.

[HamiltonJay]

The days of the typical coders understanding the hardware (other than very specific niches) are long gone.

Virtualization is great, as someone who used to have to deal with base iron and all the problems that it could introduce, modern frameworks and tooling etc are all great as well.... but I’ll be honest, I got more reward a few years back porting a telnet program to my Commodore 128, than I’ve gotten building anything commercially in a long time.

[central_va]

Such HorseshIt. Make the simple complicated and call it better.

[BikerJoe]

Another tool I like is "Understand".

Been using that tool for a loonngg time. It's awesome.