Angel Chen ▄ ▀

This was mine. It depends on what you’ve previously engaged with or marked as irrelevant

Much decision-making is tacit or qualitative. Making our OODA loops more legible is the first step towards observability & steerability. AI systems might help us codify this nebulous process. But how will it be trained to do this, and on what data? We don’t have good primitives or tooling for this.

The article I most want to read right now is a detailed breakdown of prompt engineering project from somebody who hand-wrote their own simple automated evals and then used those to iterate on a prompt over time, measuring the impact each change had on their eval score and shipping an improved app

GitHub - ueberdosis/awesome-tiptap: ⚡ Delightful Tiptap packages and resources ⚡ Delightful Tiptap packages and resources. Contribute to ueberdosis/awesome-tiptap development by creating an account on GitHub.

Flowbite, mymind. GitLab, Doist.
github.com/Doist/typist

Tiptap’s awesome-tiptap resource collection has a list of who’s using it, including open-source projects: github.com/ueberdosis/a...

This can be achieved with Tiptap’s custom extensions.

Tiptap is a wrapper over ProseMirror, and if you know your way around ProseMirror, you could probably whip up a Tiptap extension!

lol const GOVT_EFFICIENCY = true

Follow as in: “I don’t follow what you’re saying” (“je ne comprends pas”)

Not literally “I don’t Follow you here on Bluesky”

Code snippet showing the customized JSON.stringify() and JSON.parse(), which serializes all fields in Prisma's returned object to JSON compatible values that Inngest will return

Fields that are not JSON-compatible get silently excluded from @inngest.com function output: e.g. BigInt, which is how we save Clerk's UNIX millisecond timestamps in
@prisma.io.

So I serialize query results with a customized JSON.stringify() (thanks @prisma.io docs!), then parse back to object.

We used the new
@inngest.com test helper library together with @vitest.dev, works smoothly so far! ✨
github.com/inngest/inng...

(clerkDeletedAt is our own tombstone flag using event timestamp as proxy—doesn't actually exist on Clerk because the whole record gets deleted there)

#buildinpublic

I think it’d work better if the orange dotted line fanned out instead of pointing directly to GitHub’s logo, and if that avatar conformed to the “grid lines” instead of sticking out!

This unlocked memories of my (probably offbrand) matcha-scented Hamtaro beanie keychain! 😁

Today: updating our webhook integration tests (going from NextJS route handler -> @inngest.com step fn).

Yesterday: manual tests, collating notes+samples of Clerk webhook event payloads which differ from docs (as do the libraries’ exported types) to send to support.

#buildinpublic

Thread Collapsing · Issue #1547 · bluesky-social/social-app A thread collapsing feature could be implemented to allow users to easily navigate through comment threads by collapsing and expanding them as needed. This feature should include: A mechanism for c...

github.com/bluesky-soci...

Collapsible threads would be neat (there’s a feature request for this on GitHub)

Would you look at that. GitHub has added support for Bluesky handles on your GitHub profile.