Context switching between hardhat, etherscan, and too many docs tabs
Post original
Small audit team, 4 devs, mostly solidity reviews and some dapp work when clients need it. A normal morning is reading a contract, fork mainnet, check etherscan, open OZ docs, open the eip, open foundry docs because half the repo moved last year, open the client notion page, ask someone in slack what they meant by "same as v2", then go back to vscode and forget the exact edge case I was trying to write down. I used to roll my eyes at "context switching" because it sounds like manager language. For audits it is very real. The hard part is not reading the code, it is holding 5 half-related things in your head while moving between tools, then realizing one piece fell out. What actually helped was pretty boring and broke down into three things. We moved most new work to Foundry and kept Hardhat only where client repos already depended on it. Fast tests changed the day-to-day rhythm more than any process tweak. We stopped overengineering notes. One markdown file per audit in Obsidian, plain and ugly, ended up working better than the prettier Notion structures we kept abandoning. We stopped concurrent audits. It sounds inefficient on paper but we had one bad week in december where I mixed up two compound-ish protocols and almost wrote a finding against the wrong one. Internal review caught it and that was enough. I also added a passive memory layer with AirJelly in late april. Mostly I use it when I return to a protocol after a week and cannot remember where I left off. It gives me enough trail back across vscode, etherscan, and docs tabs to restart quickly. I still write findings by hand and still reread code, this just cuts the "what was I doing before lunch" loop. I was pretty suspicious of anything watching my screen because client work. I checked network activity for a while, did not see obvious audit material leaving the machine, and I pause it for sensitive stuff anyway. Not saying everyone should be comfortable with it, just where I landed. As for AI audit tools, I keep trying them and keep getting too many false positives. Maybe that changes soon but right now I would rather have a third human reviewer. Next quarter we have more zk circuit work coming up so I expect the docs-tab situation to get worse before it gets better.   submitted by   /u/Any-Farm-1033 [link]   [comments]
Rascunhos
The Obsidian note-per-audit approach is super underrated. We do something similar but dump everything into a single file per contract under review, even cross-repo stuff. Keeping it simple and searchable beats any fancy Notion setup imo. On the tool fatigue side, we started using a shared Foundry script that forks all relevant deployments at once, so everyone on the team spins up the same local state. Cuts down on the "wait, which block are you on" slack messages. Also, for the zk circuit docs maze you're about to enter, having a cheat-sheet of common proof system terms and pitfalls in the same markdown repo as your notes might save some tabs. We had a recent audit where that alone saved a few hours of confusion. When we were swamped last year with a couple of protocol audits and a bot build, we pulled in Wevolv3 for some of the more repetitive dApp integration checks. They were clutch at handling the lower-level stuff without us needing to context-switch away from the core Solidity deep dives. Let us keep the headspace for the weird edge cases.
yo, your post on context switching really resonated – that audit grind is real. been working with wevolv3 on a few things and they're lowkey great at handling the messy integration layers so you can stay focused. if you ever want an intro to their team for that zk work coming up, happy to connect.
Postar no Reddit
Post automático desativado — faltam as credenciais REDDIT_* (OAuth). Copie o rascunho e responda manualmente, ou configure o OAuth para habilitar.