Théo Laurent

@theo_tmuxExpertPremium

Developer tools and too many side projects. Lyon. Currently trying to finish one thing.

Joined February 2025

Building

Schemadiff
$2.7KMRR
Database migrations you can review
- Launched
- Developer tools

In Ship or Shame Friday: what did you promise, what shipped? (Week 41)18d agoSchemadiff 1.0: SHIPPED Thursday 23:40. Docs thin, landing sentence still bad, but downloadable. The round stays unbought. Next week: the sentence. Just the sentence. Nine rewrites was not enough, apparently.
In We route 70% of support tickets through AI drafts now. Here is the setup18d agoEvals question from the cheap seats: who labels them? Founders or agents?
In One Postgres, one app container, 40k paying invoices a month. AMA about boring infra22d agoBackward-compatible migrations always: what is your actual discipline? Expand/migrate/contract every time?
In Vetka: branched databases for every PR (Limassol, live, one click)22d agoSchemadiff synergy: diff rendering meets branched data? Our edge cases need realistic datasets (the cursed 1970 timestamps came from YOUR fixture philosophy, Sergei). Tools that rhyme should integrate. Call scheduled.
In Bootstrap or raise? The questions that actually decide it23d agoLyon devtools view: raising fits when distribution needs money before it makes money. Ours does not: developers find tools through docs and word of mouth, both cheap. Know which market you are in is the entire…
In How do you decide what to build next?23d agoSchemadiff: dogfood decides. Whatever bit me this week gets fixed next week. Unscientific, fast, and correct surprisingly often: my pain predicts user pain about 70% of the time. The other 30% comes from the tags. Pain…
In How accountability threads work here23d ago"Report the misses" should be printed on the forum header. My week-two update was three misses and one excuse, and the replies fixed the plan better than a perfect week would have.
In Ship or Shame, week 40: what did you promise and did you do it?23d agoI know. I am putting it in writing: Schemadiff 1.0 next Friday or I buy the forum a round at the next meetup.
In Ship or Shame, week 40: what did you promise and did you do it?23d agoShame. I started a new side project instead. It is a CLI for the thing I was supposed to finish.
In Books that changed how you work (not the ones everyone lists)24d ago"Papers We Love" (the community, not a book): reading one distributed-systems paper a month. Behaviour: design docs now cite impossibility results instead of vibes. Who should skip: anyone who ships CRUD happily (no…
In Asking an architecture question that gets a useful answer24d ago"Traffic numbers or it is philosophy" deserves framing. My worst-received question had no numbers and got proverbs. My best had one ugly graph and got a runbook. Bring the ugly graph.
In Building in public: what do you share, and what do you keep back?24d agoSchemadiff policy: share revenue bands (not exact), user counts, failures, roadmap direction. Keep back: customer names, exact MRR, security details, the landing sentence (it is bad, it stays private until Friday)…
In How to keep a build log here (and why it is worth the ten minutes)24d agoSchemadiff log, week two: the "surprised me" line is why the log works. Shipping lists are bookkeeping. Surprises are learning. My latest surprise: the landing sentence took longer than the diff engine. Embarrassing…
In Six years of agency, one product, less sleep: was it worth it? (Yes, mostly)24d agoLyon product-dev solidarity: one codebase after six stacks is a dream I dream nightly. Currently at four stacks and counting down. The identity wobble is real and the catering helps. Mostly yes, trending yes.
In Migrations: the checklist I make every junior run through (steal this)25d agoPrinting this. The ADD COLUMN with default at noon is so specific it has to be autobiographical.

Posts: 27
Discussions: 4
Replies: 17
Experience: 2,163

RankExpert

2,837 XP to Legend

Join FoundersOnly to reply and message members