What’s the first technical decision you lock in when starting a new SaaS product?
by•
For me, I feel like the hardest part isn't choosing between tools like React, Firebase, Railway, etc, it's really deciding which parts of the stack I should commit most of my time and tokens early and which ones may become painful to replace later.
Do you stick with a familiar stack and avoid overthinking it, design around expected scale from day one, let your coding agent influence the architecture, or start with the cheapest setup and migrate later? Also, curious which early technical choice has saved you the most time, and which one you wish you probably shouldn't have overthinked on.
188 views
Replies
@maxitencent Honeslty, I've learned that the easiest thing to migrate is usually infrastucture , the hardest thing to change is a messy architecture. I try to keep the codebase clean, pick tools my team knows well, and let actual usage drive the big decisions.
@maxitencent Have you ever picked a stack and regretted it a month later?
@maxitencent Do you optimize for speed or flexibility first?
@maxitencent Has choosing familiar tools saved you more than chasing new ones?
I always lock in the data model first because changing it later touches every feature. Does anyone sketch future relationships before writing code or do you reshape everything as the product grows?
@maxitencent Which technical debate do you think wastes the most time?
@maxitencent Has there ever been a tool that looked perfect but wasn't?
@maxitencent Have you ever picked a technology mainly because your team knew it well?
@maxitencent What's the earliest decision you still revisit halfway through a project?
@maxitencent Has shipping quickly ever forced you into painful rewrite?