analyzers

To me HP was oscilloscopes, spectrum analyzers, network analyzers, and lightwave measurement gear.

We're definitely going to start shipping some high-value analyzers in the box (probably including the async-void one).

There's memory analyzers that can detect dozens of different classes of memory-related bugs by just watching your software run.

Didn't think too much about it since there are many C specific analyzers and tools that do the same.

Tress of horrible construction are made and root analyzers are called in to save the day.

Both sides also seem to acknowledge that the sentiment analyzers chosen don't work well for literature.

There's actually an open source project called Sigrok that's compatible with a ton of logic analyzers, including the one-chip knockoffs from China.

The ability to write my own analyzers shouldn't be a substitute for a well-curated set of code analysis checks out of the box, though.

VS Refactoring Essentials is an open source extension for Visual Studio 2015 that provides refactorings, analyzers and quick fixes for your C# and VB.

I think I can have some fun with the analyzers while improving the quality of code.

All the automated static and dynamic software analyzers catch only the easiest flaws, but can catch the more serious ones only if you're skilled and lucky.

That's easy to do with Roslyn analyzers in C#.

Likely culprits are "performance analyzers" that grade a website and report an "F" (failing) grade for not using CDN-hosted common libraries.

#21 has a flipside belief, which is "Type checkers and static analyzers catch enough bugs that I don't need to write tests".

Analyzers are available as NuGet packages, so it should be a trivial process to install one of these in your project.