Here's something grep physically cannot do. I asked my code tool: does the data from this network read ever reach this memory copy? It didn't search for a name. It walked the actual value from where…

A thing I wanted my code graph to answer that most tools can't: at this exact line, which earlier assignment to this variable is the one that actually reaches here. Not "where is this name used."…

Yesterday I said it can tell which of two near-identical functions checks its input and which one doesn't. here it is on real code. Same shape: both do the copy, one checks the length first, and one…

grep can't tell you who calls a function after someone renames it. you search the old name, get nothing, and the caller is still there, one alias away. That gap is most of why reading code is slow.…