Mihail Ivanov

Any no-code tool is a good start—for example, flutterflow.io.

I had experience with both approaches and monorepo works well in most cases if cooked right. The main problem of the polyrepo approach is scalability. It might work fine on a small scale (like a small team and 2-4 repos), but then it becomes hard to maintain all the repos. On the other hand monorepo approach solves the scalability problem but it requires some expertise to be implemented. For...

I did some outsource in one of my previous companies. It works great when you need to hire people quickly because it is much harder to find good specialists by yourself than to find a good outsourcing company that will provide you with good specialists. It also works well to outsource non-critical projects to focus the team’s efforts on important stuff. But it might be a bad idea to do things...

It is a good way to build something like a proof-of-concept. Then build a real product with proper technologies.

I would say it depends on the size of the project. If it is a simple monolithic service, VPS with Docker is more than enough. At least for my project, it works better than Heroku and DigitalOcean and was much simpler to setup.