PWV Portfolio Feed

companies are not legally required to maximize profits (that's misinfo) and people are not legally required to maximize their short-term productivity if it feels terrible!

sometimes when i'm having the inevitable Do You Use AI conversation i say something like "it would make me more efficient but it also makes me very sad so I don't do it" and that is, like, a very straightforward and defensible position imho!

let me be clear, doing things out of spite is a perfectly fine reason to do things

for the last year or so, every time i land on someone's blog i subscribe to it immediately. it's been entirely good, most people post sporadically but post good things. i recommend it.

3️⃣ If the queries don’t depend on each other, don’t use an interactive transaction.

Interactive transactions = more control, but more operations.

Use them only when needed (like if you need a value from a previous query).

2️⃣ Need to create or connect records in one operation?

Use Prisma ORM-specific nested-relation helpers such as `connectOrCreate` or `set` to create or link related records in a single operation.

1️⃣ Used batched queries instead of looping DB calls.

💡 Use createMany, updateMany, deleteMany to batch work into a single request.

e.g, For the query below, it'll be 1 operation, not 3 👇

👀 Are you a Prisma Postgres user?

Here are 3 quick tips to write smarter queries and optimize your operation count 🧵

Also try out rolldown-vite in your Vite projects and share your feedback!

🙌

Bicycle habitat, king kog, and ride brooklyn all have pretty good reputations!

Bonus point for recording a little 5min video demo of your most proud work showcasing a focus on details, performance and accessibility. 🙏

Looking for an experienced frontend developer for a very interesting contract project (related to AI and LiveStore). 

Please get in touch via DM with references. (Ideally minimum of 5 years of experience.) Referrals welcome!

🎓 What does Stale-While-Revalidate (SWR) mean when caching DB results?

When you set SWR, results will be served from the cache for the specified time. Also: for every cache hit, a new DB query is triggered and the cached data is "refreshed" & the SWR timer is reset.