The next 60 ETHSecurity Badge holders have been selected using a new rubric updated by the applicants themselves!
Thank you to the people who chatted with the bot, your refinement of the rubric is the first DAO experiment we have tested.
And thank you to @bonfiresai for making amazing DAO tooling!
no comments, no deps, no docs, no tests (except e2e ones), no PRs, very little CI, a lot of CD - this might be the uncomfortable future we're headed to
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
https://t.co/nqeRdY62ee
@Gossip_Goblin Soon the world will understand Hollywood was filled with slightly above average creators who merely had a stranglehold on the means of production.
We deleted 800k lines of unit tests from the @sazabi monorepo earlier this week.
Three hypotheses:
1- Unit tests "lock-in" slop code by making it hard to change or remove
2- Unit tests slow down dev cycles by making your agent do more work locally and by increasing CI times
3- Unit tests waste money by making your agent generate more tokens and by adding useless CI runs
Will report back soon with the results!
Thanks Jack.ย
20 of the blocks had "false positives" although we didn't research those 20 too much, we just assumed they are benign
> Or do you have a sense for how low false positives would need to be to make this a no-brainer for protocol teams
The results seem promising to me, although there's still plenty of room for optimization, calibrating the questions, etc.
Adding protocol context such as invariants and permissions, and limiting alerts to activity involving the protocolโs addresses, would reduce the noise further.
You could also add an agentic triage layer to investigate flagged transactions.
@blockrotator@aviggiano it's a bleeding edge agentic swarm intelligent anime reference to the "yAcademy fellowships" that i believe were originally inspired by your suggestion 5 years ago
@n4nika_ Just saw the new business announcemnt. Sounds awesome. Good luck. I'm sure you'll crush it!
-- and no, you're not a founder if you're not shipping on a Friday night ๐ค