News for hackers. Stuff that matters.
Re:The preposterous notion of AI automating "repetitive" work by tacostakohashi on Friday January 30, 2026 @12:53PM (#46827519)
You _could_ write non-AI tools for those examples. That's basically what sonarqube, coverity, lint, etc... are. They might even do a better job, with better correctness and deterministic results.

There are also plenty of code generation / templating tools available. Maybe there are other tasks where AI offers novel capabilities, like interacting with humans, but at least for those two examples I think a lot of people are really just distracted by the novelty of AI, and perceiving the results of non-deterministic / black box system as "magic" or "creative".

Re:The preposterous notion of AI automating "repetitive" work by newzino on Saturday January 31, 2026 @10:38AM (#46837567)
You're right that static analysis tools handle well-defined rule violations - null pointer dereferences, buffer overflows, style violations. Those are formally specifiable.

But "review this pull request" isn't just about catching bugs the linter would find. It includes things like "does this architectural choice make sense given where the codebase is heading" or "is this abstraction going to cause problems when we add feature Y next quarter." Those require contextual judgment that's hard to encode in rules.

Same with boilerplate - yes, templating tools exist, but they require you to anticipate the parameterization ahead of time. AI handles "I need a thing like X but slightly different in ways that are obvious if you look at the existing code." That's a fuzzy spec problem, not a rule-based generation problem.

Whether that's "magic" or just pattern matching on training data is a fair philosophical question. But pragmatically, it solves a category of tasks that neither linters nor template generators handle well.