Marcus Böhm
3.7K posts

Marcus Böhm
@_mavilein
Backend Engineer @prisma previously: @Microsoft To-Do, @Wunderlist
Berlin Katılım Aralık 2010
919 Takip Edilen311 Takipçiler

cursor just made every $200/month copilot subscription look like a scam
dropped today with their own coding model
what took 8 hours of manual coding now takes 30 seconds
and it runs 8 versions of itself in parallel to pick the best solution
while github's charging $20/month for autocomplete, cursor built an entire autonomous dev team
composer model:
→ 4x faster than gpt/claude
→ completes full features in <30 seconds
→ tests its own code automatically
→ built with reinforcement learning on real codebases
here's what's actually wild:
most companies paying $150k/year for junior devs to do work this does for $20/month
just saved a client $253k/month migrating their dev work to cursor's multi-agent system
the intelligence gap between "we hired 3 developers" and "we deployed cursor" is getting stupid
comment "COMPOSER" and ill send the full breakdown of how to replace your dev costs with this
English
Marcus Böhm retweetledi
Marcus Böhm retweetledi
Marcus Böhm retweetledi

🌙X4 Thief Edgar Giveaway🌙(+ other giveaway on my YT)
To enter:
🌙- Follow @SpenLC
🧣- Retweet & Like
The winners will be announced on March 14th
Good Luck #ThiefEdgarGiveaway #Brawlstars

English
Marcus Böhm retweetledi
Marcus Böhm retweetledi

@_mavilein @nikolasburk @prisma I'm all for the fastest solution. I really appreciate the time you took to reply this. I'll keep you posted when I make these changes
English

@ntorresdev @nikolasburk @prisma Not using a transaction around it would probably speed things up a bit. On the other hand you would have to deal with cleanups if one of the subsequent steps fail.
Probably I wasn't clear. I would wrap all of this in a transaction.
English

@ntorresdev @nikolasburk @prisma This would give you by far the fastest solution. It would also allow you to wrap everything in a single transaction.
But the first approach is much easier to implement.
So pick your poison :-)
English

@ntorresdev @nikolasburk @prisma 1. Create all docsets at once using createMany. You can't specify the relations here. Grab all the created ids.
2. Create all related versions using createMany. Use the ids from previous step in relation fields.
3. Do the same once more for the pages.
English







