AI slop cleaner

@IntCyberDigest @hnshah You can’t survive unless you adopt zero trust mindset and arch

‼️🚨 BREAKING: GitHub has been compromised by TeamPCP. GitHub has confirmed the internal breach. A poisoned VS Code extension on an employee device exfiltrated ~3,800 internal repositories. TeamPCP is already selling the data on a cybercrime forum.

@matteocollina Yup. Its natural evolution

Bun rewrote itself from Zig to Rust. AI did most of the work. 98% of the test suite passed on the first run. The question isn't hypothetical anymore. Should we rewrite Node.js in Rust?

@dreamsofcode_io Every software will end up rewritten as Rust as it is most performative and efficient

If the Bun to Rust rewrite ends up being a success, I wonder if Anthropic will produce a product to perform language rewrite. Basically something like AWS Transform, but for modern languages. RIIR as a service.

@marcdhi token hoarding will be norm from now

A senior engineer with 15 years of experience told me she starts panicking on the 20th of every month. I asked why. She said her GitHub Copilot AI credits are almost exhausted by then, and without it, she literally cannot deliver work anymore. 15 years of experience. Panicking because an AI subscription is running low. And I’m not laughing at her. I’m thinking about what this actually means. Every company right now is quietly building a workforce that is 100% dependent on AI to write code, make decks, draft emails, do literally everything they used to do with their own hands and brain. And the AI providers know this. Once that dependency is deep enough and it already is for a lot of people, you will pay whatever they charge. Because the alternative is not being able to do your job at all. We’ve seen it with cloud, with SaaS, with every platform that became infrastructure. The difference this time is it’s not companies locked into a vendor. It’s individual human beings locked out of their own skills.

I should port Tokio to Zig just for the marketing boost.

@mason__capital Playbook for sas company

Underrated excerpt from $FIG earnings CFO - "We are also investing in first-party models trained on Figma's design corpus to improve performance on design-specific tasks while reducing cost." This is huge While the labs are all over the place, Figma has a chance to ship a frontier design-focused model

@jorandirkgreef Anyone has few billion tokens to spare? I bet TigerBeetle can be ported to Rust

I wrote these words 7 months ago. I am more grateful today for Andrew's leadership of the ZSF, that the foundations of TigerBeetle, our compiler, should not be vibed out beneath us. Standing up to “trillion dollar” big corp… Zig is hard core quality. tigerbeetle.com/blog/2025-10-2…

@firt Why bother? Agent understands rust pretty good

🔴 Vercel Labs dropped Zero on a Friday: an experimental programming language designed for AI agents. —Uses .0 files —Syntax has a Rust/Zig vibe —Agents can understand code without digging through the implementation. zerolang.ai

@cnakazawa @amadeus @fat Hmm. Lets try reviewing bun rust PR

Codiff: A beautiful, extremely fast local diff viewer I review SO MUCH code locally these days. I asked Codex to build it using diffs.com and trees.software. Thanks @amadeus and @fat. Amazing software. It took 16 minutes to build this. It's amazing. github.com/nkzw-tech/codi…

I can finally contribute to Bun! In this PR I removed a bunch of unused dependencies with my own tool 😀 github.com/oven-sh/bun/pu…

@adamdotdev Ask to rewrite in Rust

It's 2026 and your CEO just sent you a 2,400 line pull request. You get a cup of coffee and sit down to review it. It's a disaster. A dozen unrelated refactors. Unused methods with names like `convertFromBase10` and `normalizeBeforeSerialization`. You catch a few hardcoded API keys, but that's ok. It's part of the dance. They didn't consider that someone might look at this diff. Here's a comment buddy. They respond in an hour (after Copilot, qodo, CodeRabbit and Greptile finish their reviews) saying we shouldn't worry about "implementation details" anymore, those are relics of the past. Hey let's jump into a room and figure it out. We can't just agree to disagree, this is probably my last job in tech and I can't watch this fucker burn the place to the ground. The PR merges and goes to prod. You feel a shared sense of apathy and dread with Hannah the intern (she has to review his AI generated social media posts ever since Grok got too imaginative). That night you go to sleep and have nightmares of that code. You can still see the shapes of it on the backs of your eyelids. You go to work the next day ready to quit. You no longer understand the system. There is no foundation. Time to use those savings and an SBA loan to buy a liquor store and never login to GitHub again.

@jarredsumner There is no reason to keep c++, typescript , python, codebase except lack of tokens. Rust version is faster, stronger and more stable. And easier for agent to reason. I had similar experience just smaller scale

there will be a blog post about this. on what this means for bun, benchmarks, memory usage, maintainability going forward, and also the literal process of doing this (it wasn’t just “claude, rewrite bun in rust. make no mistakes”) this is a 960,000 LOC rewrite, the code truly works, passing the test suite on Linux and soon other platforms. e2e I started working on this 6 days ago. this would’ve been a massive amount of work by hand.

99.8% of bun’s pre-existing test suite passes on Linux x64 glibc in the rust rewrite

@mehulmpt Bad rust is better than good zig

I am a huge fan of Bun, and I am excited about the new initiative they are taking with a port to Rust, but I would personally not vouch for using Bun in production for at least 1 year more, if you're serious about stability. This rewrite will fix a good category of memory bugs, sure. But this whole migration, largely LLM-driven is going to open a whole can of worms, things that you don't know you don't know. Talking about this in a video today!

In age of AI, there are only really 3 roles in company: Builder, Seller and Support. Support is really overhead and you try to make it efficient as possible. Builder = Product Engineering (customer facing) + Infrastructure eng. Seller generates revenue

@SahilBloom Never bring problems without solution

Major life hack: Don't complain, ever. Nobody likes a complainer. They drain the energy of everyone around them. It's exhausting spending time around someone who constantly complains about things outside their control. If it’s within your control, go do something about it. If it’s not, you’re just wasting energy thinking about it. Complaining gives too much power to the thing. Take back that power.

@morganlinton @martin_casado Yeah, is pragmatic choice for startup now. Anthropic price out of SMB marketplace

Officially canceling our Anthropic plan, it’s Codex + Cursor for my little 16 person eng team. Anthropic is great for companies that can spend $2,000/mo and up per engineer, but not affordable for us. Codex really upped their game recently, and with GPT 5.5, it’s just so good, and so token efficient. Still using Cursor plenty, my team still looks and reviews a lot of code. But with Cursor, we’ve never hit a limit, and Composer 2 is pretty awesome for most stuff. Testing out Droid as well and see some good early results with Droid + GLM 5.1, but still more testing to do before rolling it out to the whole team. My guess is many more engineering leaders will be sending messages like this. Anthropic makes great stuff but phew, it’s so darn token hungry. My team loves Codex and Cursor, onward!

@Trace_Cohen This is unbreakable barrier for AI rollout.

Most of you have never worked inside a massive enterprise organization, so a lot of these layoffs, while tragic and deeply unfair for many people affected, probably do not fully make sense from the outside looking in. You have to understand what it actually feels like to operate inside the machine. At my last Fortune 50 role, I was helping build internal onboarding and integration infrastructure to move partners through the pipeline dramatically faster. Nothing particularly revolutionary either. We were replacing spreadsheets, manual workflows, email chains, and fragmented approvals with digital forms, APIs, and centralized systems. The kind of thing that obviously should exist in 2026. My entire team aligned on the direction almost immediately. Engineering agreed. Product agreed. Operations agreed. The business case was obvious. Faster onboarding meant faster revenue, fewer errors, lower operational burden, and a better partner experience. But in large enterprises, alignment does not equal execution. There was a fork-in-the-road architectural decision we needed approved before rollout. So we built a deck. Scheduled meetings. Socialized it upward. My boss reviewed it so he could present it to his boss weeks later as one bullet point inside another PowerPoint for another steering committee update. The actual decision itself probably took 15 minutes. The process around the decision took over a month. And while everyone was waiting: - timelines slipped - rollout slowed - partners waited - teams got frustrated - upside disappeared - leadership asked why execution was delayed The irony is that most large enterprises are not inefficient because employees are lazy or unintelligent. Many of the smartest people I have ever worked with were trapped inside systems optimized for risk management, approvals, reporting structures, and organizational self-preservation. That worked reasonably well in slower technology cycles. It breaks in the AI era. Because AI compresses the gap between idea and execution. The organizations that win will not necessarily be the ones with the most resources. They will be the ones that can make decisions faster, restructure workflows faster, integrate systems faster, and remove layers between problem identification and action. The real disruption is not that AI replaces people. It is that AI exposes organizational latency that companies were previously able to hide behind scale.

@Spheniscidae007 agree. @eastdakota

Agentic AI is the new keyword $AKAM +29% after hours vs $NET -19% after hours. Cloudflare needs a new SEO lead

@firstadopter All software are dead only expiry time are not evenly distributed

Databricks CEO Ali Ghodsi: "If all software is dead, isn't OpenAI, Anthropic dead? They're software companies with a bunch of researchers writing software .. Nvidia should be dead because they just have really smart people who create chip designs, humans that use some software .. Software obviously isn't dead. Nvidia, OpenAI, and Anthropic are not going to be dead companies."

@dbreunig CLI is all you needed

"To be an AI-ready company you need…" 01/23: "…an AI policy." 04/23: "…a vector DB." 11/23: "…a custom GPT." 11/24: "…llms.txt." 04/25: "…an MCP." 10/25: "…Skills." 05/26: "…a CLI."