[cgbg]

That is OK but all changes are not equal.

In our work team we had folks who had only one helpful idea every six months—but often it was so creative and powerful that it meant more than the dozens of little improvements other team members generated during the same period.

The problem with truly complex processes is that nobody fully understands them—managers who think they do are often a part of the problem and not part of the solution.

[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.