- Don't build your CI/CD pipelines; use Vercel or something similar
- Don't use message queues, crons and anything that can by design cause race conditions until absolutely unavoidable
- Use a framework if you and your team know one well (e.g. Django Rest Framework), otherwise use whatever you know inside out even if it doesn't have all the features you need - or you'll end up slowing down painfully at every other complex bug
- Using TypeScript for both backend, frontend and the domain simplifies a bunch of things (configuration, types)
- Unless you're building ML pipelines in parallel to a web app (or some similar clear technological separations exist, e.g. web interface and an UE5 game), you should use one programming language. All your developers should know the app A-Z in the early stages.
- Your product is unlikely to succeed overnight but likely to die because of overengineering. You should worry about scaling, but only a little bit.
- Forget using JWTs if you're in some sort of regulated field. Any sensible white/greybox certification for insurance (and that's often a requirement for running a business) will require you to have "log out all devices" option.