u/UnwisePublic

[ Removed by Reddit on account of violating the content policy. ]

had a pretty simple SaaS idea and spent almost a week comparing databases, auth setups and different builders.

finally just picked one and started building lol.

got the ugly first version working in a couple days. still has plenty of stuff i wouldn't ship yet, but at least now i have something to actually test instead of another 40-tab research project.

honestly think i was just procrastinating by calling it "technical planning., no code tools like blink are the best way to deal with that"

had this rather boring saas idea for a long time but was postponing it thinking that back-end/database/auth part would turn into a separate project.

finally decided to build it in no-code platform instead of trying to design everything beforehand.

got the first working prototype in a couple of days. as always there is much to be done yet, but surprisingly for me the toughest part was to make the transition from an "idea in notes" to something you can click around in.

using mostly Blink for this and am surprised how far no-code has come, specially claude fable 5, can someone recommend me any ppt focused tools, can create consulting level slides?

after shipping the MVP I thought the hard part was over.

just finished another late night refactor, this time it was a new role based permission model.

of course the schema changes 15 user tables all need migrations without dropping live data.

just wondering what folks are using to handle schema changes at this scale, having flashbacks to midnight horror stories where migrations locked tables for hours.

started using blink database and it seems like it is managing on its own so seems promising.

has anyone solved table locks on live Postgres migrations or is this just the price of growth?

Built a simple PM dashboard for my team that everyone loved in the demo. Two weeks later and I'm dealing with auth bugs, race conditions on task updates, and performance issues with real data.

Turns out my blink environment handles concurrency completely differently than production and I'm honestly losing my mind. It's one of those "works on my machine" situations but it's my entire backend that needs to be rewritten.

How do you guys handle this transition from demo to actual production stress? It's like I built a toy and now I need to throw it out and start over with actual best practices.