Qiao Han

Software Engineer @ Supabase

[Qiao Han @qiaor]

Context + prompt = diff

[Qiao Han @qiaor]

Great explainer on how coding models are trained

[Garry Tan @garrytan]

2026 and onwards is truly the age of open source

[Qiao Han @qiaor]

@bygregorr @supabase The functions team has made a lot of improvements on cold start https://t.co/POaE7BzD3S

Are there specific examples you can share from your own experience?

[Qiao Han @qiaor]

@zarazhangrui it only takes a single prompt to try it out.

can't wait to see what it produces

[Qiao Han @qiaor]

@zarazhangrui Strong signal to turn this into a product

[Qiao Han @qiaor]

Isn't this all you need to run an online business? https://t.co/N8l6Smxxx5

[Mitchell Hashimoto @mitchellh]

@gill_kyle AI friendly code storage is a GitHub alternative. This is what's going to kill GitHub (whether it's Pierre or something else), because its going to be the critical infrastructure for the next GH which is likely going to be provided by the agentic coding providers.

[Qiao Han @qiaor]

@stojaaan Isn't it nice to have gpu accelerated ram usage?

[Paul Copplestone - e/postgres @kiwicopple]

we are looking for someone to lead CLI development at @supabase

this is becoming one of the most critical interfaces for devs/agents

tag the best Go dev that you know and if we hire them I'll give you $1,000 of Supabase credits

They don't need CLI experience, they just need to have a good product sense. My pitch for Supabase:

◆ we're open source
◆ we don't do geo-adjusted pay
◆ we have an async work culture
◆ most engineers have 1 meeting per week
◆ we're full distributed across 50 countries
◆ we power the world's fasted growing companies

Application link ↓
https://t.co/flLV1GWtzZ

[Qiao Han @qiaor]

Who needs a multi tenant architecture when you can multi database your tenants?

[Supabase @supabase]

Today, we're launching Supabase for Platforms—a white-label offering that lets platforms provision and manage fully managed backends on behalf of their users

You control the entire experience. Your users get the full power of Supabase ⚡️

https://t.co/zOW7aRM1RS

[Qiao Han @qiaor]

@jmwind @supabase I wish more supabase users will follow the setup you have here.

[Qiao Han @qiaor]

@liljamesjohn @dshukertjr There's no such configuration for type generation. Instead, you can override the generated type like this https://t.co/1o4NLoCN4o

[Paul Copplestone - e/postgres @kiwicopple]

Today we are making the @orioledb Patent freely available to the Postgres community

Oriole is a storage extension for Postgres which uses Postgres' pluggable storage system. It's a drop-in replacement for Postgres' existing storage engine (Heap).

Our north star is to upstream Oriole to be part of the Postgres source tree, developed and maintained in the open alongside the rest of Postgres (if the community want it!)

We announced the acquisition of Oriole over a year ago. Since then, we have been working on cleaning up the legal structure and finalizing the asset transfers.

We have wrapped up all legal activities, and we fully own US Patent 10,325,030 (“Durable multiversion B+-tree”).

@supabase is making this Patent explicitly available to all Oriole users (including proprietary forks) in accordance with the open source license.

Oriole benchmarks show that it is around 5.5x faster than the default storage engine (Heap):

[Qiao Han @qiaor]

@kiwicopple @orioledb How's the performance on A19 chip?

[Qiao Han @qiaor]

@steipete @supabase @neondatabase If you are interested in supabase branching with prod data, I can actually enable it for you under a feature flag.

Feel free to DM me your email for supabase account.

[Qiao Han @qiaor]

@nkgoutham @supabase Last but not least, some users want to version control all code changes in a repo. This is where GitHub integration comes in. You can externalise your database schema to supabase/migrations directory so that new branches are always created from the same files in your git repo.

[Qiao Han @qiaor]

@nkgoutham @supabase If you don't want to spin up a new environment with every change, another alternative is to use a staging persistent branch. Changes to staging branch can also be merged to production. When something breaks, you can use PITR to restore staging to a previously working state.

[Qiao Han @qiaor]

@nkgoutham @supabase Supabase branching is very similar to git branch. When working on a new feature, you want to

1. checkout a new database branch
2. modify the branch for your new feature
3. merge the branch to production

This way you always test new changes on a separate environment than prod.