PWV Portfolio Feed

I would love to layer on more ways to use Inngest’s primitives over time, like how we’re doing with AgentKit. I think as we’ve seen several other companies adopt the step/context.run model after Inngest tools could also be interoperable.

Yeah, that’s interesting. Maybe workflow kit needs to be more composable and kinda of like a portable format like it can be an output and an input whereas Inngest function outputs and trace visualizations now cannot be inputs.

Maybe this is a bad path the more I look at things. 🙈

That's helpful. I have to admit that I'm not very well accustom to xstate and just took a look at it for a few minutes to explore how we might map it to Inngest and there are so many ways to create state machines in xstate it's hard to find a clean path to map to

The Git integration MVP is starting to shape up! We are still iterating over some remaining bugs and UI polish so that we can deliver a beta worth testing. Have a great weekend everyone!

Ah ok - that's the main main value for you w/ xstate? the visual side of seeing it ahead of time?

In fact, I thought I _just_ saw in the GerritForge summit video that branch based review was _maybe_ on the horizon

I’m curious. You say “series” but my last run in with Gerrit was that it was very single commit based. Even looking at the docs now, it still appears single patch based. Can you do a series of commits as a change basis now?

I just read it for a different book club, so I'd be down if you're okay with 'random internet strangers'

The flow that one has when they get started building apps goes away when reached certain scale.
Bringing it back is what drives our work at Tuist, and if you are a leader in the space, I’d consider striving for it in your mobile organization.

Now we can run `npx prisma generate --sql` to get Prisma to pick up the types generated by the SQL file.

This means we can use the query function and get type safety over the result.

Let's say we want to form a totally different query than we'd get from Prisma ORM. 

Perhaps using `WITH users AS` so we can shape a different output.

Next, create a new directory inside your existing `prisma` directory called `sql`. 

In here, place a .sql file such as `getUsers.sql`.

✅ Start by enabling `typedSql` as a preview feature in your schema

Using a type-safe ORM means easier query authoring, fewer bugs, and better coordination across teams.

Prisma ORM also allows you to drop down to raw SQL in a type-safe way as well. You're never restricted to just using the ORM.

Here's a quick look at how to use it 👇

Right? In the end, we're happy to step into things that Apple could have solved, but some of these feel like such a no-brainer. They might solve this at a more foundation level in the future, but who knows how long that will take.

It has been a few weeks since we launched Prisma Postgres in GA and shipped a brand new website. 🎉

Have you found the easter egg yet 👀