After weeks of building, Carte AI is live: https://t.co/1CIwNSS011
I wanted a tool that treats a menu like the room. Designed, voiced, intentional. Most restaurant menus today are Word docs someone screenshotted onto a QR builder. Most "AI menu generators" hand you a one-shot PDF and call it done.
Carte is the design-partner version. You sit with the agent like a designer, chat-refine, comment on a specific dish, undo any turn, restore wild ideas. When the menu is right, one publish freezes a permanent edition: a hosted mobile page, a branded QR card, and a print-ready PDF, all rendered from the same source. Each edition lives on its own URL forever. The QR you print today still resolves in five years.
Five hand-designed templates Classic, French Cotton, Italian Linen, Japanese Washi, Ottoman Parchment each with codified typography and voice. A kaiseki menu shouldn't read like a brasserie.
Free to draft as long as you want. $4.99 when you publish. No subscription.
The same product serves a restaurant chain and a single dinner party for six.
If you try it, I'd love your feedback. ๐ฝ๏ธ
I wanted a blog on the same domain as my app. Normally that's a separate static site, a subdomain, a second deploy pipeline, a weekend lost to DNS.
I dropped a route, wrote markdown, shipped it that afternoon.
Good DX didn't make me happier. It made the feature exist.
Does your app actually need React Server Components? Or have you just been told it does? Most people cannot answer that question. That is not a technical limitation.
After weeks of building, Carte AI is live: https://t.co/1CIwNSS011
I wanted a tool that treats a menu like the room. Designed, voiced, intentional. Most restaurant menus today are Word docs someone screenshotted onto a QR builder. Most "AI menu generators" hand you a one-shot PDF and call it done.
Carte is the design-partner version. You sit with the agent like a designer, chat-refine, comment on a specific dish, undo any turn, restore wild ideas. When the menu is right, one publish freezes a permanent edition: a hosted mobile page, a branded QR card, and a print-ready PDF, all rendered from the same source. Each edition lives on its own URL forever. The QR you print today still resolves in five years.
Five hand-designed templates Classic, French Cotton, Italian Linen, Japanese Washi, Ottoman Parchment each with codified typography and voice. A kaiseki menu shouldn't read like a brasserie.
Free to draft as long as you want. $4.99 when you publish. No subscription.
The same product serves a restaurant chain and a single dinner party for six.
If you try it, I'd love your feedback. ๐ฝ๏ธ
After weeks of building, Carte AI is live: https://t.co/1CIwNSS011
I wanted a tool that treats a menu like the room. Designed, voiced, intentional. Most restaurant menus today are Word docs someone screenshotted onto a QR builder. Most "AI menu generators" hand you a one-shot PDF and call it done.
Carte is the design-partner version. You sit with the agent like a designer, chat-refine, comment on a specific dish, undo any turn, restore wild ideas. When the menu is right, one publish freezes a permanent edition: a hosted mobile page, a branded QR card, and a print-ready PDF, all rendered from the same source. Each edition lives on its own URL forever. The QR you print today still resolves in five years.
Five hand-designed templates Classic, French Cotton, Italian Linen, Japanese Washi, Ottoman Parchment each with codified typography and voice. A kaiseki menu shouldn't read like a brasserie.
Free to draft as long as you want. $4.99 when you publish. No subscription.
The same product serves a restaurant chain and a single dinner party for six.
If you try it, I'd love your feedback. ๐ฝ๏ธ
The moment you add Turso, Litestream, and a CDN to your PHP+SQLite stack because you need two of anything, you are not simplifying. You are rebuilding Postgres with worse tooling and a vendor bill you cannot escape.
30 seconds of spinners is not great UX. ๐
@tanstack/ai now streams structured output straight into useChat. Pass a Zod schema, get a typed `partial` and `final` for free. โจ
Blog post link below ๐
The engineers writing "how we scaled to millions with microservices" have a platform team, an SRE army, and deployment tooling you are not going to get.
You are adopting the architecture without the support structure that makes it survivable.
Good DX is not developer happiness. It is whether your idea survives long enough to become code, or dies in your head on a Tuesday afternoon.
Every tool that fights you subtracts from the odds that feature ships.
GitHub silently un-merged 2,092 PRs across 230 repos for five hours and called it acceptable.
That is not a bug. That is a preview of what happens when the infrastructure layer stops feeling responsible for its output.
Implicit magic is a trap. Explicit magic is just magic.
The frameworks that know things about your code you don't are not being helpful. They're hiding the failure mode so it shows up in production instead of during development.
this OpenClaw bot finds local businesses with no branded gear, AI mocks up their logo on the right product, and runs the entire sale on autopilot.
here's how anyone can use this system to land local business clients:
- scrapes every indie business in a city from Google Maps in real time
- filters by review count, rating, and industry vertical
- maps each vertical to the right product
- pulls the logo + samples the palette from their actual visual identity
- AI-renders a photoreal mockup of the logo on the product
- writes a postcard with the owner's first name + a personalized buy link
- when they scan + pay, a print-on-demand API auto-prints + ships direct to the business
every step from discovery to fulfillment is automated.
reply "LOCAL" + RT and I'll send you a free guide so you can build this too
You see Pieter's htop screenshot.
You spin up PHP + SQLite on a $5 VPS.
Three months later you're paying Litestream and Turso and a CDNโand your queries are still slow.
That's not simple. That's complexity you didn't earn.
"Regressions are acceptable" is how teams launder accountability.
Nobody read the 10,000 line PR. Nobody can be blamed. The bug is just weather.
That is not coping. That is permission to ship worse.
Local LLMs will not replace Claude for real coding work. They also will not get a second chance if the hype oversells them and they disappoint a developer on day one. The well is being poisoned by the same people who claim they are helping it.