So true
//Cyclomatic complexity and function size don't matter to agents//
We need to reconsider our priors on code readability.
Humans, compared to agents, are pretty slow at understanding large quantities of text. So in the old days, readability was important so the human could efficiently grok what was going on.
So readability now comes down to:
1. Can a human, if needed, jump in and understand the code
2. Does the code use the same domain language as the human describing the code?
1 helps with observability and the occasional spot checks you need to do on important PR's. 2 helps the agent translate the words you use into code changes.
In other words, readability is now a nicety, not a necessity.
The way agents 'read' code is different - good agents are all about gathering data about how the code works. They'll prod around with it, execute parts of it.
So 'readability' to agents really means 'verifiability'. How easy it is to mess about with that code to see it working.
Let's take this scenario:
- You have a huge module in your codebase that uses all sorts of complex performance tricks
- It has 100% test coverage
A talented human would need an hour or two to get comfortable working in that module.
An agent needs zero time. They verify it with the tests, poke about a bit, and they're good to go.
The takeaways:
- When judging a module (or a codebase), don't think about how easy the code is to read
- Instead, think about how easy it is to verify
- Design your codebase so modules can be tested and verified independently
- Feel free to sacrifice a bit of readability for performance
- Cyclomatic complexity and function size don't matter to agents
1
23
rickmak retweeted
Some mistakes you might be making:
Your effort level is too high
Your skills are too long
You're not aligning before you start work
You're aligning too often, and too hard
Your automated checks are too lax
Your custom tooling is too token-inefficient
You aren't doing enough automated review
You aren't reviewing previous coding sessions (with an agent)
You're doing too much human review
You aren't vibe coding enough prototypes
Your agent can't verify its own work
You're babysitting the agent too much
You've overloaded your global steering files
Your codebase is hard to navigate
You aren't building a shared language
Your codebase architecture allows bad tests to be written
You aren't thinking strategically enough
You aren't thinking enough
rickmak retweeted
Finally! This is great, now I can stop dropping CLAUDEmd files which just contain "@AGENTSmd"
So Base is no longer eth? hmm, other l2 have no volume anyway...
ethdaily.io/ethereum-and-bas…
2
23
rickmak retweeted
BREAKING: EU Parliament advances “Chat Control 1.0,” allowing mass scanning of private communications through 2028.
rickmak retweeted
We're opening the waitlist for our Monetization Gateway, which will allow you to charge for any web page, dataset, API, or MCP tool behind Cloudflare. The charges will settle in stablecoins over the x402 open protocol. cfl.re/4eUFdt6
You go as fast as the slowest part of the system you built.
jamesshore.com/v2/blog/2026/…
Loop intelligence is lack of spot light in recent hype: robert-glaser.de/when-everyo…
26
// In contributor poker, you bet on the contributor, not on the contents of their first PR.
kristoff.it/blog/contributor…
23
So it becomes federation of Bank. Defi code if for fast execution, it is not the ultimate law for human.
Aave is my life's work and we're working nonstop to find the best possible outcome for users.
I’m personally contributing 5000 ETH to DeFi United as we continue working together with partners on formalizing more commitments. I’m working to see this resolved and market conditions normalized as soon as possible.
DeFi United.
31
Not surprise with reference to the 2016 eth DAO event.
The Arbitrum Security Council has taken emergency action to freeze the 30,766 ETH being held in the address on Arbitrum One that is connected to the KelpDAO exploit. The Security Council acted with input from law enforcement as to the exploiter’s identity, and, at all times, weighed its commitment to the security and integrity of the Arbitrum community without impacting any Arbitrum users or applications.
After significant technical diligence and deliberation, the Security Council identified and executed a technical approach to move funds to safety without affecting any other chain state or Arbitrum users.
As of April 20 11:26pm ET the funds have been successfully transferred to an intermediary frozen wallet. They are no longer accessible to the address that originally held the funds, and can only be moved by further action by Arbitrum governance, which will be coordinated with relevant parties.
20












