Remember 1 hour of vibe-coding can save you 1 day of debugging.

This is what I get for upload the wrong format of file for a batch generation task. I gave up.

The magic of next.js. You are building your nextjs container image, and it will actually try to connect to your database.

Based on a true story.

Creating a PR to the repo whose code base is mostly owned by you alone.

Gee. Open telemetry and grafana cloud is really a godsend. Super easy to setup, yet extremely powerful (hope to show some dashboard porn soon, but for now, not enough data). Plus, grafana cloud is just too cheap.

My day so far.

I have a solution and I don't know why it works.

I have to confess my love for nextjs. This affection does not stem from its ease to use or unparalleled power. Having went through countless seemingly un-decipherable errors of nextjs should be a competitive edge for me. I hope nextjs would be more widely adopted. All my efforts shouldn't be in vain

For this simple task, you will need mitmproxy. How exciting!

As a detective who has a lot of time bisecting, I love to solve nextjs mysteries like this. The less clues, the better.

Nextjs is really a PITA.

TIL that you need the runtime environment variable set to build a nextjs project. github.com/vercel/next....

Just found out I needed github.com/fabien0102/t... to convert real types to a zod schema. Why would I want this instead of static types? Because, trpc, the End-to-end typesafe rpc framework prefers implicit types. I have to use zod for output validation! Oh my gosh.

Here is an even uglier solution to this.

Functional programmers, guess why you have this error. One does not simply use pattern match with typescript. All you have to do is forget the good old days.

Am I doing it wrong? Or, it's just prompting requires more work? The result generated from this prompt is really underwhelming. For this particular example, I should have used better-auth's client API instead of creating back-end interfaces. Neither me or the "agent" was smart enough.