GoKawiil
Tech News
A new Fleet survey of over 250 enterprise Apple IT admins, each managing roughly 2,000 devices, found widespread adoption of AI tools in daily work. In the past 30 days, 68% used AI for troubleshooting or log analysis, 62% for writing scripts, and 61% for creating device management profiles or configurations, though errors from AI-written code reportedly take days to resolve.
GitHub reported that over the past year it expanded its infrastructure by 4 million CPU cores, 160 petabytes of storage, and 50 Tb/s of networking capacity to cope with a surge in AI-generated code activity. The company said code commits grew sixfold and merged pull requests quadrupled year-over-year, with monthly commits rising from 1.4 billion in April to 7.4 billion by September, and total pushes over the past 12 months exceeding the combined totals of 2024 and 2025.
A new tool called Sphinx has been shared on Show HN that intercepts 'git push' and asks the developer questions about the code changes being committed, particularly code generated by AI assistants. The demo shows it probing a developer's understanding of a Stripe webhook handler's idempotency logic, following up when an initial answer is incorrect.
At the Maintainers Summit held October 8, 2026 in Prague, Linux kernel maintainers decided to remove the 'Assisted-by' tag requirement, meaning contributors no longer must disclose when code was generated with AI assistance. Linus Torvalds defended the decision on the mailing list, likening a ban on AI tools to banning text editors and saying he expects contributors to understand their own submissions rather than follow blanket rules. Torvalds separately said he has used AI to help parse difficult patches and recently posted a development-branch fix for cache contention that he claims showed a 23x improvement in a synthetic benchmark.
A developer released ai-deslop, an npm package bundling Oxlint rules aimed at flagging common low-quality patterns found in AI-generated TypeScript code, such as chained type assertions, unsafe use of 'unknown' types, and object-typed function parameters. The rules combine ones vendored from dmmulroy/anti-slop with additional checks, all under a deslop/* namespace, and ship as compiled JavaScript compatible with any Oxlint JS-plugin runtime including Bun, Deno, or Node.js.
A blog post by Simon Späti argues that the real risk from AI-generated code isn't poor quality but that engineers and teams no longer understand why architectural decisions were made. He cites a viral tweet describing a large company where specs, tickets, tests and code are all produced via Claude Code, with staff at every level simply prompting the AI and management pressuring teams to ship faster without reviewing output.
A software engineer using the handle v0xium described in a viral X post working 12-13 hour days at an unnamed large company where nearly all coding is done via Anthropic's Claude Code tool. The engineer said staff across seniority levels mostly approve AI-generated code rather than write or debug it themselves, calling the process "soul-sucking" and noting that no one seems to understand the resulting software.
A software commentary piece argues that app features, once shipped, behave like kudzu — an invasive plant that spreads uncontrollably and is nearly impossible to remove. The author cites a personal example: adding AI-driven hashtag bubbles to a blog in May, then discovering months later through Plausible analytics that the feature never cracked the top 30 visited pages, making it not worth maintaining.
Vibe coding, the practice of using AI language models to write software with minimal manual coding, is drawing scrutiny after Georgia Tech researchers linked dozens of security vulnerabilities directly to AI-generated code in just a three-month sample. Despite these risks, a survey of over 1,100 professional programmers found that 72 percent use AI coding tools daily, with AI-generated or -assisted code making up 42 percent of their codebases and expected to exceed half by next year.
A software engineering essay, part of a series called 'Conquering Entropy,' examines how AI-generated code changes the trust relationships within engineering organizations—from trusting the ticket author and reviewing engineer to trusting test suites, CI/CD pipelines, and even AI-driven site reliability tools. The author argues that as AI agents make code generation faster and cheaper, teams need explicit accountability: whoever ships a PR should be responsible for fixing it if it breaks in production.