This is a great lesson to all the normies that you do not store important things in environment variables even though you were taught to.
You can store maybe feature flags, staging or enviornment domains
But not important things, there is a reason why Hashicorp Vault is as big as it is
I think this perfectly sums up the current software space. Re-discovering and lauding solutions to problems solved decades ago
In general code should be "self-commenting" You should be able to read a method, its args, its flow and understand what it means, comments are an extra nugget of context or quirk when needed, but they should not replace the "self-commenting" role of code
ban and delete most if not all code comments!
agents love copying what already exists. a seemingly harmless comment explaining some temporary workaround is one of the worst viruses you can have in your codebase. like a weed it'll spread quickly as a tool for agents to quickly get their job done. before you know it, your codebase is overrun with hacks and stale comments. just one more workaround bro
you can use pstack's /no-comments skill as a weedkiller. it'll seek out useless comments while keeping the ones that actually should exist (like explaining a browser quirk), and figure out how to solve them on a first principles basis
here's a prompt you can try asking @bot:
create a project agent that uses /poteto-mode to spawn a /swarm to use /no-comments and identify useless code comments we can prune in my repo. come back with a high level plan of which of these workarounds would be best solved by refactoring and which we can straight up delete
x.ai/bot/plugin/9717366
New on our Engineering blog: Creating in-house source control.
In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale.
Here, we share how we built a new version control system—and fully migrated our monorepo from git—in five months: anthropic.com/engineering/re…
Indeed everything is a write-ahead log
New on our Engineering blog: Creating in-house source control.
In May, we merged around 2,500 code changes per day. In September, we merged more than 30,000 per day. As a result, we became bottlenecked by developer infrastructure built for human (rather than agent) scale.
Here, we share how we built a new version control system—and fully migrated our monorepo from git—in five months: anthropic.com/engineering/re…
s retweeted
The cheapest model with data access beats the best model without it
We ran 9 models from 5 labs on 82 work tasks where the answer has to come from real data. Each model ran the same tasks with and without access to paid data.
Claude Haiku 4.5 is one of the cheapest closed-source models you can run an agent on. Claude Opus 5.5 is one of the most capable (and expensive). Haiku with data finished 60% of the tasks. Opus without it finished 50%. Per finished task, the cost came out about the same.
It wasn't just Haiku. Every model with data beat the best model without it, open source included. The weakest, Grok 4.7, still finished 54%. That edge over Opus is small enough to be noise, but the direction never changed across models or task categories.
Most of the agent conversation is about which model to use. On this kind of work, what the agent could access mattered more.
Method, tasks and traces in the replies.
The only way consumers will be able to stop this is with discord group chats absolutely farming the fuck out of new account welcome bonuses and promotions selling food at a discount. Or maybe a class action.
hey @DoorDash- happened to notice while ordering food that the total was almost identical on two accounts, one with DashPass and one without. the promised savings seem pretty misleading 🤔
Agents can now set up your website’s security with Turnstile Spin
It's surreal seeing a string of ideas and iteration turn into a blog like this! I'm so grateful for my time at Cloudflare :)
blog.cloudflare.com/turnstil…
s retweeted
1990s:我们用上了 B+ 树和倒排索引,世界上已经没有什么几秒钟查不出来的东西了。
2010s:我们推广了分布式全文搜索引擎,几十亿条日志毫秒级命中。
2025:我们把所有文档切成稀碎的 chunk,烧掉了不知道多少算力把它们向量化后扔进向量数据库,最后把搜出来的垃圾拼成几万字 prompt 塞进大模型,然后开始祈祷它别出现幻觉。
2026:大模型告诉我们,这个 find,还有这个 grep 工具真好用。
The time between 1 and 3 am is when you have the best chance to become One with the Wired granting you access to mythical Knowledge & Compute at the cost of your Corporeal integrity
























