needless to say I prefer the latter for my in-terminal agent

gave codex a try for a few days now and realised that it serves a different purpose than Claude Code. Codex excels if you have well-written concepts and a verbose prompt. It's also very good at helping draft concepts. Claude is the "run typecheck and fix errors" kind of person..

very grateful to be part of this community, and a huge thanks to @supabase for inviting me over.

What really made the week special though was being part of the team. behind all the slack / github profile pictures is a group of people who are incredibly sharp, yet humble and approachable.

The conference itself (my first one ever) had a ridiculous panel. A mix of deep technical sessions and honest founder conversations. No filler, just solid content.

Finally had time to reflect on the past week at #SupabaseSelect, and I really feel like I got to be part of something special.

hacking at @ycombinator with the @supabase community today ⚡️ #SupabaseSelect

just packed my bags for a week in san francisco for @supabase select 🎉 excited to finally meet internet friends in person—if you’re around and want to hang out, let’s connect!

the most interesting part of this PR is how claude was leveraged to get a head-start. I can only recommend going through early commits - there is a lot to learn!

still hard to believe how fast things have progressed in the past months. then: now:

I told Claude Code multiple times not to stop until it's done — now it's turned into its own hype-man, literally cheering itself on to keep going like a human 😂

if you are in Berlin, come join us next week to celebrate launch week and talk Postgres and AI over a slice of pizza! 🍕 (there will be a huge opportunity from @supabase for anyone joining a meet-up this time!) https://t.co/SUvto2qHKT 9/9

and last but not least, we fixed all the reported crashes, rewrote the entire change handling, introduced a custom tokenizer and lexer, and made other stability improvements under the hood. If it was crashing for you in the past, now is a good time to give it another try! 8/9

syntax error reporting for plpgsql! this was a low hanging fruit but is already making my day job much more pleasant. 7/9

our linter also received a facelift. we added line suppressions for more fine-grained control. under the hood, we expanded the context for each rule to enable more sophisticated rules. 6/9

workspace support! believe it or not, we received a request from someone who works with seven(!!) @supabase projects in a single monorepo. to support this better, you can now extend your root config and overwrite the database config for each workspace. 5/9

the language server now reports issues and provides autocomplete within sql function bodies 4/9

we shipped "execute statement under cursor" as our first code action. this is very useful if you want to quickly iterate on a function. 3/9

we made significant improvements to the autocompletion: - Support for many more statement types (even RLS) - Better weighting and filtering of results Kudos to @juleswritescode for shipping this! I believe this is now best in class for Postgres. 2/9

In honor of @supabase launch week, we wanted to share what's new in the Postgres language server since launch. We've been focusing on stability, improving existing features, and unblocking our exciting future plans 1/9