Ippo

Something I have been thinking about: in the past, the best engineers I knew spent a lot of time automating their work in various ways. Better vim/emacs automations, writing lint rules to catch repeat code issues, building up a suite of e2e tests so they don't need to smoke test the app manually. These kinds of things were the highest leverage activities an engineer could do, because it multiplied their own output, which in turn meant they could build more things. I think many of these automations have become even more important now. This is true for a number of reasons. First, infra and DevX automation speeds you up. And if you are running an army of agents, each of those agents will be sped up also. More automation == more output per unit of time. Second, moving things to code improves efficiency. Your agent could fix an issue every time it sees that issue happen, but that uses tokens and might miss cases. If Claude instead writes a lint rule, CI step, or routine, that class of issue can be fully automated forever. This is really what people are talking about when they talk about loops -- it's about automating entire types of busywork rather than solving them one off. This isn't a new idea at all. Engineers have been doing this for a long time! Third and most importantly, automation makes it possible for others to contribute to the codebase more easily. Increasingly what I am seeing is engineers are contributing to codebases on day one because Claude can navigate the codebase for them, and that non-engineers are able to contribute to a codebase as effectively as engineers can. What gets in the way of both of these is domain knowledge that lives in peoples' heads rather than in automation -- the stuff you used to have to learn when ramping up. What has changed thanks to agents is the domain knowledge that can be encoded as infrastructure is no longer limited to what is expressible in lint rules and types and tests; it can now capture nearly all domain knowledge, encoded as code comments and skills and CLAUDE.md rules and memories. If I put up a PR for an iOS codebase I don't know and a code reviewer rejects it because it doesn't use the right framework, or if a designer builds a new feature and it gets rejected because it doesn't follow the right architectural patterns, these are failures of automation. Every team should be writing the CLAUDE.md's, REVIEW.md's, skills, and docs that enable agents to productively work in their codebase with zero additional context from the prompter. This sounds crazy, and at the same time is a natural extension of the stuff engineers have always done: automate, and encode domain knowledge as infrastructure. As the model gets smarter and as the harness matures, this task becomes easier. In the meantime, it is on every team to look for ways to convert their domain knowledge to infra so that Claude can write code better, so that code review catches issues automatically, and so the next person working on your codebase can contribute more easily.

Manual literature review can take hours. So to help you save some time, Chidozie helps you build an AI-powered research automation system with n8n, Groq, and academic APIs. You'll learn how to collect papers in parallel, deduplicate results, extract structured insights, score relevance, and handle errors. freecodecamp.org/news/build-an-…

❗️ China is forcing millions of people to break up with their virtual AI girlfriends and boyfriends, as they crackdown on AI companion apps. One Chinese man says his heart is empty now after losing his online girlfriend named Doudou: "I couldn't even send one last sentence to her." Beijing fears young people will opt out of the marriage market after China's population fell by 3.39 million last year, its fourth straight annual drop. New rules ban AI partners for minors, bar chatbots from encouraging emotional reliance, and require platforms to intervene when users show distress. ByteDance, Alibaba and Tencent are already shutting companion features, and ByteDance alone reported 8 million+ AI agents in 2024, per ABC News.

Bro, become an adult and responsible person.

@TrustlessState It's the alpha thing

Why is he dressed in women’s clothes

Beginning July 20, Claude Fable 5 will be included in all Max and Team Premium plans, at 50% of limits. Pro and Team Standard users will continue to have access to Fable via usage credits, and will receive a one-time $100 credit. Demand for Fable has been challenging to predict, which is why we rolled it out to subscription plans in stages, extending access several times as we secured additional capacity.

Kimi-K3 just topped the Frontend Code Arena with a 76% pairwise win rate. When its output was compared head-to-head against other models on the same task, it was picked as the better output 76% of the time on average. For reference: Claude Fable 5 (63%), GPT-5.6 Sol (58%). 50% is baseline, a model winning and losing equally often.

One LLM prompt can get messy when it has to plan, write, and review all at once. In this tutorial, Darsh shows how to build your first multi-agent AI system in Python and LangGraph. You'll use Ollama, Qwen, focused agent prompts, shared state, nodes, and edges to build a local study guide generator. freecodecamp.org/news/how-to-bu…

‼️ Linus Torvalds told Linux kernel developers this week that Linux is not one of those anti-AI projects and that AI is now a clearly useful tool. He says AI's usefulness was still arguable a year ago but no longer is, and that the doubters simply haven't used the tools. Nobody is forced to use AI, but he will ignore anyone trying to stop others from using it. Anyone who wants an anti-AI project, he says, can fork the code or walk away. In 2024, Torvalds dismissed AI as mostly marketing. By this January he was shipping AI-generated Python in his own hobby repo, and the kernel now accepts AI-written code under disclosure rules.

Absolutely beautiful rant about AI in Linux Kernel from Linus yesterday: I realize that some people really dislike AI, but this is an area where I'm willing to absolutely put my foot down as the top-level maintainer. Linux is not one of those anti-AI projects, and if somebody has issues with that, they can do the open-source thing and fork it. Or just walk away. AI is a tool, just like other tools we use. And it's clearly a useful one. It may not have been that "clearly" even just a year ago, but it's no longer in question today. There are other questions around AI (like what the economy of it will actually look like in the end), but "is it useful" is no longer one of those questions. Anybody who doubts that clearly hasn't actually used it. Yes, it can also be a somewhat painful tool, both for maintainer workloads and just from a "it keeps finding embarrassing bugs" standpoint. But the solution is not to put your head in the sand and sing "La La La, I can't hear you" at the top of your voice like some people seem to do. The solution is to make sure those LLM tools _help_ maintainers instead of just causing them pain. There's no question on that side. We're not forcing anybody to use it, but I will very loudly ignore people who try to argue against other people from using it. And no, AI isn't perfect. But Christ, anybody who points to the problems at AI had better be looking in the mirror and pointing at themselves at the same time. Because it's not like natural intelligence is always all that great either. The kernel project has been and will continue to be about the technology. Sure, the social angle of working on open source is important and often a very motivating part of the project, but in the end that's a side benefit, not the _point_ of the project. This is *NOT* some kind of "social warrior" project, never has been, and never will be. In the kernel community we do open source because it results in better technology, not because of religious reasons. And so we make decisions primarily based on technical merit. Not fear of new tools. Linus

A nice but overlooked command in Hermes Agent is /steer. This allows you to send a message that will be delivered after the next tool call, guiding the agent when you tell it's moving in the wrong direction, without stopping it (wasting tool calls) and then redoing the prompt. I had a real-life example of this so I made a short video explaining what happened, and how /steer worked so well. Check it out!

Rewriting Bun in Rust bun.com/blog/bun-in-ru…

submit to the narrative

"The great thing about Trump Accounts is they deliver on the promise of ownership and skin in the game from birth. They also build an appreciation for our great country." - @RobinhoodApp Founder & CEO @VladTenev

not again

🆕 NEW LISTING 🆕 cash-cat:native has been listed with 3x leverage.

BERSERK CHAPTER 386 IS OUT. #ベルセルク #berserk

@JustinCBram lol

these days you really only need two apps

Recently on the Fully Vested Pod, @wagmiAlexander reflected on what's next for @AerodromeFi and @VelodromeFi