@TylerFCloutier devs are fine. i just wish you'd focus less on others and share more about your product and real use cases (not pointless video call through DB).
I really like how you guys choose to do staff diff, focus on that. πππ
@dshukertjr@supabase inspired me to start building Narflow, i noticed that the dev experience could use some love. simple setup has you bouncing between multiple sections and when things get more complex you're stuck in code input wiring code manually
https://t.co/5I52dNy1fr
Hot take: every "fast" backend tool either treats you like a junior or holds your code hostage.
So I'm building NarFlow visual setup, real code output, zero lock-in.
Here's an early look. Roast it or request features, either works.
#Xano#Supabase#Backend#code#developertips
Hot take: every "fast" backend tool either treats you like a junior or holds your code hostage.
So I'm building NarFlow visual setup, real code output, zero lock-in.
Here's an early look. Roast it or request features, either works.
#Xano#Supabase#Backend#code#developertips
I keep noticing this over engineering mistake:
For tasks the user_id comes directly from the authenticated context.
Frontend doesnβt send it.
Backend doesnβt validate it.
The creator becomes the owner by definition.
And honestly this is exactly as it should be.
@dshukertjr I see ... itβs valid and makes sense to have a secure layer at the DB level.
In my case, I prefer using a Zod schema to handle validation and formatting before any interaction with the table (as a user input parser) while keeping the ORM and DB layer simple.
@dshukertjr can you elaborate on that?
What is the point of checking an enum or a condition like x > 0 both in the backend logic and in the DB?
Why involve the DB at all?