The question often gets interpreted as "what's your favourite tech stack to work in"...hence the knee-jerk "ALLTHETHINGS" answers below without really considering the requirements given.
I'd love to see a solo dev implement a stack that requires an acronym, one of which being Typescript
It would need to be a well informed decision based on budget, resources, product market, product longevity.
Given the little information provided -
I would start with a Rails + Hotwire + Tailwind stack for MVP/product market fit and potentially consider a client side framework once it outgrows it's use, which may be a long time.
Put the horse before the cart
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The question often gets interpreted as "what's your favourite tech stack to work in"...hence the knee-jerk "ALLTHETHINGS" answers below without really considering the requirements given.
I'd love to see a solo dev implement a stack that requires an acronym, one of which being Typescript
It would need to be a well informed decision based on budget, resources, product market, product longevity.
Given the little information provided -
I would start with a Rails + Hotwire + Tailwind stack for MVP/product market fit and potentially consider a client side framework once it outgrows it's use, which may be a long time.
Put the horse before the cart