Yesterday I was auditing a batch of Crystal projects on my Fedora workstation, and it hit me how much the day-to-day code review threat model has shifted.
For years, if you wrote Crystal, your static analysis workflow was straightforward: you ran the compiler for type safety and Ameba for style …
Earlier tonight, my desktop fired a notification: upstream had tagged a new release for one of the packages I maintain in Fedora Copr. My background auditor had caught the new release tag from an Atom feed, compared it against my local RPM spec, and alerted me.
Yet nothing was committed …
Let us be real for a moment: we have all been burned by AI hallucinations.
You sit down, ask an LLM to write a helper script or refactor an awkward class, and it hands back something that looks strikingly professional. The indentation is crisp, variable names are elegant, and docstrings …