so many talkers than doers

without murmur i don't want to work

Check Run Agents, now available in @Macroscope. we made a video to show you how it works! these are super flexible agents you control that let you enforce your team's coding conventions, workflows, and compliance checks during code review. just define in markdown and include trigger rules, model choice/reasoning levels, and tool access (including any 3rd party integrations and MCP servers you've already connected to macroscope)-- then the agent spawns as a Check in GitHub. we've been delighted by the creativity and complexity of what our customers have been doing with check run agents: enforcing style conventions, coordinating multistep db migration workflows, ensuring public-facing docs are updated in sync with code changes, and more.

One of my fav features. Has made life so much easier as an oncall When things getting not clear to me, on Slack I'd @Macroscope to figure out what's breaking from log and what's the culprit in our code base. and have it to create PR for the fix

On @withmartian’s independent Code Review benchmark, Macroscope ranks #5 overall on f1 score (a metric that balances precision and recall) and higher than formidable competitors we respect like Cursor BugBot, Devin, Greptile, CodeRabbit, and Claude Code Reviewer

watched the whole game. really proud of Team Taiwan!

tell me who loves reviewing code?

our new code review pipeline is a huge step change improvement: higher severity bugs caught, with WAY fewer false positives.

Delightful demo moment that would have been inconceivable a year or two ago: While doing an onboarding yesterday, I noticed a bug in our web app. Mid-meeting I posted the bug in Slack flagging one of our devs and asking @Macroscope to make a linear ticket while + investigate and fix in parallel. 15min later Macroscope had made the ticket, found the issue, fixed it in a PR and validated no bugs in code review. End to end the fix was merged, tested (via live vercel preview link) and deployed to prod within 20min-- before the meeting was even over. Inadvertently turning a lemon into lemonade and a made for a great demo. What a time ...

Introducing Fix It For Me. Most code review tools help with finding bugs. But the time it takes to fix them still can be costly. Until now.

After 8 years and 9 months of hardcode engineering, today marked my last day at Twitter/X. Forever grateful to grow with my amazing colleagues. Stayed a little bit longer in 2.0 for self-actualization and somewhat proved I can be resilient and productive On to the next adventure

“We go because God is leading us, not supernaturally or in a dream, but through Bible study, prayer and trying to understand what a man’s life should be from His point of view.” — Gerrit Blaauw, when he left IBM to teach in Holland.

What would you do if you figure out you’re over engineering something half way..

founder mode vs manager mode is just a matter of who cares the company more

current AI dev is like coordinating for gang fight. the larger group the better. who cares to build delicate models?