Back End
Supabase
I use Supabase when a project benefits from a managed PostgreSQL backend, authentication, relational data, and generated APIs.
In Practice
How I use it
I use Supabase when a project benefits from a managed PostgreSQL backend, authentication, relational data, and generated APIs. It is useful for moving quickly while still keeping a structured data model and room for application growth.
Application logic
I use Supabase where an application needs real data, business rules, integrations, or automated behavior behind the interface.
Data and workflows
I focus on the shape of the data, how it changes, what should happen next, and how to keep application workflows understandable as they grow.
Reliable integrations
Authentication, validation, errors, external services, and edge cases matter just as much as the happy path when a system supports real business activity.
Connected Stack
Related skills
These are tools and capabilities that commonly sit near this skill in my project and video work, with the strongest shared relationships surfaced first.