Matt Biilmann
@biilmann.blog
3 days ago Thanks Dave, means a lot.
💬 0
♻️ 0
❤️ 6
Thanks Dave, means a lot.
the deno contribution charts are looking very funky. lots of commits, mostly from ~3 humans and 3 robots
One week out from the AI Tinkerers Munich meetup on May 4th. 🇩🇪
Our own Ben Brandt will be giving a talk, alongside demos from builders shipping real AI in production. Co-sponsored with @jetbrains.com.
Space is filling up. RSVP in the comments. Six years is a long time, and we don't want to lose you over pricing without at least taking a look. There's almost always something we can do on usage or plan structure that gets the bill closer to where it needs to be. Mind if someone from our team reaches out to dig in before you go?
Netlify Database is live. Fully integrated Postgres as a new core primitive on our platform.
Watch it happen end to end in this demo:
www.youtube.com/watch?v=InMK... Try it with a prompt like "I want an app to manage my list of mythical creatures."
The agent will spin up the schema, wire up the UI, and give you a preview running on a real Postgres branch in a couple of minutes.
app.netlify.com/start This works for whoever is building. A designer prompting an app into existence gets the same safety net as a team of engineers running migrations through Drizzle. Same workflow, same guarantees, no extra setup.
How a schema change flows end to end: 1. Agent writes code and a migration file 2. Preview build runs the migration on your branch 3. You test. Break things. Add junk data 4. Publish when ready 5. Netlify applies the right migrations to production No 2am rollbacks.
The agent literally cannot modify production. Not a permission flag, not a toggle. It just cannot reach it. It writes SQL migration files as it works. Those run against your branch during preview builds. Production is only modified when you go live.
When you start an agent run, Netlify provisions a Postgres branch based on the latest production data. Schema changes, test records, half-baked experiments, all contained. Production stays untouched until you choose to publish.
Years ago, Deploy Previews changed how we ship code. Safe to break things, easy to roll back, every branch isolated. The database layer never got that treatment. One environment, shared, always a little broken. That's what we fixed.
Meet the new Netlify Database.
Fully managed Postgres, built into the platform. Every agent run automatically gets its own database branch.
Here's why that matters. 🧵
www.netlify.com/blog/netlify... Read full blog post here
commandcode.ai/blog/determ... Two events ship today:
1. PreToolUse (can block)
2. PostToolUse (observes)
Works across shell, read, write, and edit tools.
Read docs for more details 🪧
commandcode.ai/docs/hooks Introducing Hooks in Command Code.
Gives you deterministic control over agent behavior without relying on the model to follow instructions.
- Block dangerous commands
- Auto-format on edit
- Run custom validations
Try now!
|_ npm i -g command-code Did you know that the latest version of @vite.dev's @react.dev plugin comes without Babel?
Less dependencies as Oxc is taking over these transforms since Vite 8. 🎉
If you wonder how the React Compiler works then, no worries, there is a preset for it adding Babel back. Now all we need is a way to incentivize decentralized storage operators!
also PLEASE bill for orgs! I want to pay for good things!
also while I've got you here, I'd really want to put Atuin under an atuin org, so I expected this to contain "new org" or similar
am aware it probably makes sense under your model to have @atuin.sh make an account, but we would also want to make sure multiple people can have admin/etc ersc.io - i have no idea about how it looks but based on who's involved my hype for it is immense Fantastic news!!
I really like what you're doing, but to be totally blunt; it does feel like your site was designed by backend engineers 😭