A buggy app is one thing. A buggy database with corruption is another.
Constraints are a big help. Simple examples:
✅ UNIQUE (user_id, billing_period)
✅ CHECK (price >= 0)
✅ EXCLUDE USING gist (timespan WITH &&)
Use them to your advantage ✌️ 
Fun new blog post today about some git config values that should probably be the defaults.
blog.gitbutler.com/how-git-core... 
35 issues, some bugs, some feature requests, closed during Quality Week! 🎉 Next week, we're back to focusing on deeper Git integration! Have a great weekend!
Prisma Postgres 🤝 Cloudflare Workers
We’ve just shipped a brand new guide that shows you how to build + deploy a full stack serverless app using Prisma + Workers in just a few minutes!
pris.ly/cf-workers-ppg 
AI is great but I dunno how to feel about AI marketing so I of course made a video
youtu.be/qiiZycFlIVk 
Why waste time running your entire test suite for just a few line changes in a PR? It’s a CI bottleneck! Our cutting-edge selective testing solution for Xcode projects slashes test times from minutes to mere seconds.
Discover how: tuist.dev/blog/2025/0... 
Try it out at tldraw.computer We'd been asking Gemini for keywords when it made a website. The model just locked into that task completely: it was spending its whole response on thousands of keywords
I proposed to my girlfriend in Quordle. She said yes!
stevekrouse.com/proposal 
Just used chat gpt to make a little Automator app that I could drop mp4s onto to speed them up /compress them for social media (diy ffmpeg wrapper) Don’t sleep on Automator
The latest issue of our newsletter has been released! Dive into discussions about branching ecosystems, catch our interview with Vera Dias, the mastermind behind "Coding with Vera," and explore some uplifting resources.
Check it out: tuist.dev/newsletter/... 3 Xcode project pitfalls that sabotage developer productivity:
- Crawling build times
- Lagging test suites
- Unreliable tests
Tuist is your solution to all three. More engineering power isn't the answer—let us show you why. Enjoy the first three months on us.
Shoot us a DM Managing Prisma ORM in a pnpm workspaces monorepo is simple!
Follow our step-by-step guide to:
📦 Generate Prisma Client properly to avoid type resolution issues
🔗 Share and reuse Prisma Client across apps
⚙️ Use the package in a Next.js app
Check out the guide 👇
pris.ly/guide/pnpm-... 🚨 New Changelog! 🚨
🔹 Prisma Postgres is production ready!
🔹 Prisma ORM 6.4.0 introduces a new config file and case-insensitive JSON filters
🔹 A brand new onboarding for Optimize
...and more!
Get all our updates in one place every 3 weeks 👇
prisma.io/changelog 
I am looking to chat with Software Engineers that work in physical systems (robots, drones, aircraft, etc) and can tell me more about the data problems you face. Bonus point if you use or consider using SQLite. We'd love to understand how our rewrite of SQLite can help you!
At the end of the day, it's all highly dependent on your use case though, what are you building?
Lastly, Inngest has great coverage from our local dev server which runs on your machine for fast iteration and cloud observability with metrics and traces. Your code can run on any cloud or infra and it scales to billions of executions a month.
As it's event driven, Inngest can receive events from your application or webhooks to trigger workflows and the events are utilized on recovery tooling like bulk replay if you have a bug or third party API issue that you need to recover from.
www.inngest.com/docs/platfor... Inngest's SDKs all work with a very flexible "step" construct that makes it easy to define workflows in very normal looking code that can also generate new steps at runtime. This makes it ideal for workflows that are dynamic like AI agents or for building user-generated workflow systems.
I'm not an expert on DBOS and it's new-ish, so it will be hard for me to compare, but at it's core, Inngest is event-driven and has a custom-built queue that includes multi-tenant aware flow control functionality that handles complex concurrency, throttling, etc...
www.inngest.com/docs/guides/... Over the last 2 years, many users have asked, “What will Zed 1.0 look like?” We took some time to write up our vision and are ready to share. Check out our roadmap for Zed 1.0 and beyond:
zed.dev/roadmap?b=39 Zed is built from the ground up in Rust, using our own custom GPU-powered UI framework. Owning all layers in the stack allows us to deliver low-latency performance, but comes with the cost of a long beta period as we implement everything from scratch.