Static Analysis for Humans
  • Blog
  • About
  • Legal Notice
  • LinkedIn
  • Twitter
  • RSS Feed
Subscribe
  • Static Analysis in the agent loop: Three behavioral changes

    Static Analysis in the agent loop: Three behavioral changes

    Adding a static analyzer to your coding agent’s loop changes how the agent behaves. Besides catching bugs, you can see that the token bill shifts, the agent is more focused, and it reduces code bloat. By the end of this post, you will… read more …

  • Static Analysis is the Cheapest Upgrade for Your Coding Agent

    Static Analysis is the Cheapest Upgrade for Your Coding Agent

    A coding agent that reviews its own output carries the same blind spots into the review that produced the bugs in the first place. That is not verification: it is the same bias running twice. A static analyzer breaks that loop. It runs… read more …

  • Can your compiler prove your code is safe? A clear no.

    Can your compiler prove your code is safe? A clear no.

    No compiler will ever decide every safety question about your program. Alan Turing proved it in 1936, and every language picks its own way to live with that limit. By the end of this post, you will know why the limit exists, and… read more …

  • Type Safety: What Your Compiler Won’t Tell You

    Type Safety: What Your Compiler Won’t Tell You

    Most modern languages quietly convert types for you: an integer becomes a float, a signed value becomes unsigned, a 32-bit number squeezes into 8 bits. The compiler is not at fault, the language permits it. These implicit casts are valid code, and they… read more …

  • Coding Guidelines: Know When Your Tool Is Always Right

    Coding Guidelines: Know When Your Tool Is Always Right

    Not all MISRA rules are equal. Some can be checked perfectly by any tool, others are fundamentally impossible to verify with certainty. Knowing the difference saves you from arguing with your tool and tells you when your compliance is at risk, or when… read more …

  • Coding Guidelines – How to take smart shortcuts

    Coding Guidelines – How to take smart shortcuts

    Coding Guidelines are always useful. If you feel differently, you are doing it wrong. In this second article on that topic, we discuss how to reduce warnings and how to take valid shortcuts in your compliance process. In the end, it isn’t so… read more …

  • Coding Guidelines – how they work, and why we fail to love them

    Coding Guidelines – how they work, and why we fail to love them

    Coding guidelines are always useful. If you feel differently, you are doing it wrong. In this article, I show how to significantly reduce the developer burden and make the guidelines work for you, instead of you working for them. We cover different types… read more …

  • Reducing the Noise: Teaching Static Analysis new facts

    Reducing the Noise: Teaching Static Analysis new facts

    In this article, I share a simple trick that reduces warnings in your Static Analysis tool, without compromising safety. You will learn how to inject new facts into your Static Analyzer, which can save you many hours of review work, as well as… read more …

  • Error Absorption: When Static Analysis hides your bugs

    Error Absorption: When Static Analysis hides your bugs

    After Static Analysis has found a bug, it must make assumptions about how to continue the analysis. In this article, we learn about a common “filtering effect” and the pitfalls around it. At the end of this article, you will not only understand… read more …

  • Formal Methods: The strictest, most powerful kind of Static Analysis

    Formal Methods: The strictest, most powerful kind of Static Analysis

    Have you ever wished that you could find every bug in your software, fix each of them, and have a perfect piece of software? This article explains how this is possible with Formal Methods, why you might already use them without knowing it,… read more …

1 2
Next Page

For software engineers who want static analysis to actually work. Practical techniques, honest trade-offs, no tool vendor spin.

ai aliases bugs cwe errors exception false positives flow analyis guidelines human error memory methods parser process rust safety security tricks

  • LinkedIn
  • Twitter
  • RSS Feed