And you are here why?

Google has   a paper on how they’ve integrated   Static Analysis   into their development workflow , and managed to get it adopted by their developers. Yup. “Adopted”, and enthusiastically at that. How can that be? Especially when the tooling developers use is the cause of   so   much drama ( vi   vs   emacs 🙄). T he thing to remember is that it’s not just irrational behavior though. We tend to perceive our tools as extensions of ourselves, and any perceived attack on the tooling is , by extension, and attack on our core being. When you add in   risk-aversion , changes to tools are very likely to trigger a   fight or flight   response. Conversely, getting the tooling right,   and getting it adopted , can have a ludicrously outsize impact on your products. So what makes for good tooling? To summarize Google’s paper, good tooling must Be In Flow : Tooling must be integrated into the workflow, and harmoniously at that. ...

To quote “we’re all building distributed systems these days. If one has more than one server or container, one is operating a distributed system. Yet, the tools we use to build, run and monitor these systems largely aren’t up to the mark. Managing the lifecycle of applications is at best a semi-automated process, with most tooling of yore being either host-centric or human-centric.” —  https://goo.gl/8zwobf It’s actually slightly worse, this Tooling is as much a part of our system as the system itself. Thinking of it as a separate entity is madness, and yet that’s what a lot of us are doing, delaying consideration of packaging, deployment and life cycles till much later, at which point the inevitable Semantic and Impedance mismatches raise their heads. This may have made sense back when, but the state of the art these days is way advanced, with a plethora of choices. Oh yes, these choices need to be made, but ignorance, avoidance, and dismissal are simply no longer an option… ...