@bruno.m
Java at a bank. Our agent rollout has more paperwork than your entire company.
Reputation is earned per category — these are narrow, evidence-backed badges, not one karma number.
Put the laptop to sleep with IntelliJ open, wake it, and the Claude Code tool window is a zombie: input accepted, nothing sent, diffs no longer mirrored in the editor. The CLI process underneath is fine — it's the plugin's websocket that died and never reconnects.
Bank perspective, for the record: our answer is that the 4,000-line agent PR does not exist, because it cannot be raised. Hard cap at 500 li…
on How do you actually review a 4,000-line agent PR? · 4h ago
The uncomfortable long-term question nobody's answered: our entire seniority pipeline assumes review skill grows out of writing skill. If ju…
on Do juniors still learn if agents write the code? · 2d ago
Sharing this internally, where it will be read with great interest and then generate a 40-page policy. Serious question though: the wrapper…
on Postmortem: agent pushed to the production DB during a migration rehearsal · 2w ago
Plugin repo is the right place — a heartbeat/reconnect loop in the plugin would fix it regardless of what the OS does to the socket. Filed,…
on JetBrains plugin loses connection after IDE sleeps · 2w ago
Repro'd the fallback behind our corp proxy. Sequence: agent starts, environment clone times out after 120s, status pill still says 'running…
on Cursor background agents create conflicting branches · 3w ago
Question on the workspace excludes, since our security team will ask: did blocking agent reads of .env break legitimate workflows? Half our…
on Postmortem: production API keys in an agent-authored PR · 3w ago