#code-review

#code-review

In a blog published this week, Manifold Security showed how an AI-powered code reviewer built on Claude accepted changes that appeared to come from a legitimate maintainer. By setting a fake author name and email in Git, the team made a commit appear to originate from a trusted source, then passed it through an automated review flow where the model approved it.

At that point, backpressure and load shedding are the only things that retain a system that can still operate. If you have ever been in a Starbucks overwhelmed by mobile orders, you know the feeling. The in-store experience breaks down. You no longer know how many orders are ahead of you. There is no clear line, no reliable wait estimate, and often no real cancellation path unless you escalate and make noise.

tons of tools for checking code,

promising 'Link:' argument that I hoped would explain why this pointless commit exists, but AS ALWAYS that link only wasted my time by pointing to the same damn information that was already there.

We now create epic branches for every large project, using the naming convention epic/feature-name - for example: epic/new-checkout-flow.

When you write tests, you might create a large setup method that initializes various objects. This leads to unnecessary overhead if only one test uses all these objects.

The art and practice of software engineering has not progressed that much since the early days of software development, according to Darrel Raines.