About our 3 day AI Coding Accelerator: Vignesh Mohankumar and I have both been slammed, but behind the scenes things are cooking. Vignesh just crushed two “30-day” projects in 6 and 10 daysm no Git worktrees, no multi-agent setups, no bullshit CLI layering. Just clear plans, smart

good week

Last chance to sign up for the coding accelerator! Today I'm going to live code a feature for a few hours, from meeting notes to a PR. I think it would have taken me a week manually, but we'll get it done much faster. If you have some time, come through! maven.com/nila/ai-coding…

this is actually optimal so that you don’t get out of the ai coding flow state

Some of my learnings from AI Coding Accelerator: 1) All the coding tools have realized that some form of “Explore -> Plan -> Build” is the right order to build software using AI. They’re all figuring out the right UX embed this into their products, and I think the winner is

I'm pretty convinced about Cursor's Agent Window mode now. If you haven't tried it yet, I don't think there's a button for it. Click CMD + E. - Nice diff view, like a mini PR review - Can still see the relevant file - Easier to see chat history with a sidebar

Stop waiting for your AI to respond. The worst place to be: the "valley of waiting" where your tool takes 1-2 minutes to respond. Either go lightning-fast to stay in flow, or fully async where you can switch tasks. Key takeaways from Silas Alberti (Cognition) session on the

I wanted to like it but Cursor’s browser so far doesn’t work for me. It doesn’t know how to scroll, so it screenshots the same page every time. Also doesn’t seem to know how to click things to change state. Gonna try Devin more this week

Sharing some insights from our session with Lee Robinson from Cursor. Keep your rules file minimal. Only add something when you see the model mess up 2-3 times. Focus on high-quality tokens, not writing a book of instructions. More below.

New product workflow with jason liu I gave live feedback on a prototype he built. For smaller tasks, he spun up Codex background agents to write PRs. Five minutes after the call, he sent over a list of PRs and Linear tickets (made via MCP) for me to review.

Just got my first public hater, maybe I've finally made it

cursor 2.0, sign up to hear our thoughts and talk to cursor's very own eric zakariasson maven.com/p/3656b2/offic…

relatively convinced that people saying codex is worse this week are just blindly following what’s going viral on here same when people were convinced claude code was doing the same a few months ago seriously not worth overthinking the tools this much

suddenly sonnet 4.5 feels painfully slow and codex feels glacial. just because composer 1 is that fast

some things i’ve noticed so far a week into cursor 2.0 so far git worktree based flows just aren’t working that well for me. maybe i need to learn more how to use them but i end up with so many merge conflicts, issues with the gh cli pushing the wrong branches, and general

trying to do stacked PRs instead of git worktrees today, and you end up having to rebase all the branches each commit so maybe i do need to figure out worktrees...

trying graphite mcp to handle stacked prs for me based on jason liu's suggestion, will update x.com/vig_xyz/status…

explore and plan with sonnet 4.5 build with composer 1 debug with gpt-5 codex all you need

codex really does one-shot 80% of what i throw at it (without a plan file), but takes 15min+

come hang out with eric zakariasson and Vignesh Mohankumar about how much money im spending on cursor this month w/ cursor 2.0 impressions / office hours maven.com/p/3656b2/curso…