Vincent van der Meulen

co-founder @mainframe. prev: @figma @diagram @facebook.

[Vincent van der Meulen @vinvan]

the future of design isn't drawing pictures and developer handoff as a step shouldn't exist.

[Vincent van der Meulen @vinvan]

It doesn't feel natural to compare Webflow or Framer X to Sketch/Figma/Adobe XD but as time progresses we totally will.

The future of design isn't drawing pictures and developer handoff as a step shouldn't exist.

[Jordan Singer @jsngr]

we're starting to test a new app with designers @mainframe

DM or reply if you want to try

[Vincent van der Meulen @vinvan]

@tkkong would love!

[Vincent van der Meulen @vinvan]

@walden_yan 🙌 did something similar! https://t.co/OcnWCmpSTx

[Vincent van der Meulen @vinvan]

human code review is almost dead. but while it's still here, it should be personalized.

we @mainframe made a /review-as skill that learns how to review like you. based on your past year of github comments.

run it on any pr to instantly flag things *you* would care about!

[Vincent van der Meulen @vinvan]

@hunvreus a few months old but still decent reference!

[Vincent van der Meulen @vinvan]

2026 is the year agents move to the cloud, and top startups like ramp already live in this future.

unfortunately many companies are unprepared. to help, we @mainframe wrote down all we know about making codebases cloud agents ready.

hope it's useful! https://t.co/ZJNQvIzUiq

[Vincent van der Meulen @vinvan]

@vanlancker

[Vincent van der Meulen @vinvan]

the world is a museum of vibe coded software

[Vincent van der Meulen @vinvan]

@ridd_design @inflight congrats @ridd_design! incredible seeing all the progress!

[Vincent van der Meulen @vinvan]

i've been shipping prs from my runs, showers, and commutes by calling @bot.

get yourself an always available eng manager. go into debt if you have to

[Vincent van der Meulen @vinvan]

how to use @bot for engineering and get a ton done:

1. create a (cursor) project for every big workstream. i have ten, such as a “mcp project” and a “bugs project”

2. make sure every project spins up cloud agents with /poteto-mode

3. in grok bot, make an eng bot whose sole job is routing requests to the right project.

4. now voice call (!) your primary bot and braindump all your tasks.

your tasks will automatically end up at the correct projects, and result in sweet prs :)

you get all the benefits of projects + pstack, but don’t have to think about anything!

[Vincent van der Meulen @vinvan]

@aurelcorp @bot nice! i haven’t tried rooms!

[Vincent van der Meulen @vinvan]

how to use @bot for engineering and get a ton done:

1. create a (cursor) project for every big workstream. i have ten, such as a “mcp project” and a “bugs project”

2. make sure every project spins up cloud agents with /poteto-mode

3. in grok bot, make an eng bot whose sole job is routing requests to the right project.

4. now voice call (!) your primary bot and braindump all your tasks.

your tasks will automatically end up at the correct projects, and result in sweet prs :)

you get all the benefits of projects + pstack, but don’t have to think about anything!

[Vincent van der Meulen @vinvan]

@uxaistudio @bot my grok is able to use @conductor_build cloud, where i have claude and codex hooked up. same idea!

[Vincent van der Meulen @vinvan]

@KINGiTAJ @poteto @bot opus 5.5! xhigh right now

[Vincent van der Meulen @vinvan]

@sheherenow_ don’t remind me 😭

[Vincent van der Meulen @vinvan]

one underrated hack is to let your @bot manage your screen time.

e.g. my grok bot has access to my rescuetime so it can change what websites are blocked, checks in daily about # hours worked, etc.

[Vincent van der Meulen @vinvan]

@krispuckett how long are you here for?! stop by our office!

[Vincent van der Meulen @vinvan]

the paid partnership label makes any brand look so cringe that i’m not sure the eyeballs are worth it

[Vincent van der Meulen @vinvan]

@reactiverobot agree! great breakdown

i do think a lot of people “don’t know” that #2 is a type of pr you can ship.

and that you can totally background #2 while still spending a lot of time doing #1 and talking to customers etc.

#2 is the kind of gardening that imo should always be happening

[Vincent van der Meulen @vinvan]

why shipping 100s of prs makes sense
there's always something to improve in your product's codebase. if your goal is to make customers happy as fast as you can, it makes sense to fix those things the moment you find out about them. we're no longer limited by intelligence!

some of this is of course the result of the new way of working. ai is a net-benefit for codebases, but leaves behind more residue as people are less in tune with low risk areas. which you then have to squash by shipping more.

of course it's a little bit different for frontend/design, where the (human) thought required for the average fix is higher. but in backend land, there are always obvious bugs waiting for you to eliminate them.

i think many people would benefit from focusing on speed! it's the equivalent of the running advice to "just run more."

unless you cheat your way out, it's hard not to get to a better product/codebase/engineering skills by simply trying to put up more prs.

we're in the brief period where models still need our slight handholding and energy, which is why this advice still feels uncomfortable. but soon enough models will make the rate at which we used to evolve products feel dull.

[Emil Kowalski @emilkowalski]

Can someone help me understand how shipping 100s PRs a day makes sense?

Why do you need to ship so many PRs in the first place?

I might just not be AI-pilled enough to understand the need for it yet, so I’m genuinely trying to understand it.