Just be careful of inventions assignments. If you live in the US you probably signed paperwork that says anything you invent or create is property of the company you work for.
If you signed one of these and hack on the side… successful business could be owned by your previous company.
You can always ask that they release the IP which requires the lawyers to officially sign it over to you.
Here’s what you do. Come up with an MVP that does one very common workflow for your target market. Choose any market you’re familiar with.
The MVP workflow needs to be good enough that cold outreach would respond. “Oh I do that in my day job, I’ll take a look”
Then demo to them.
They will tell you why they can’t or won’t buy. They will say it needs X or Y or they will ask questions, “can you integrate with Google sheets?” You’ll probably do 50 of these and most won’t buy… but they will tell you either directly or indirectly why not. Now focus on removing the road blocks.
Just keep implementing features until the questions people have are already answered in the demo. People stop asking about features and start asking about pricing.
That’s the path I’ve taken and seems to work well.
There are two types of serverless that most people reference. Serverless functions (e.g. AWS Lambda) and serverless managed platforms (e.g. AWS ECS Fargate)
Serverless functions are great if you have a lot of small services that need to be "on standby at all times".
For example if you have 5000 separate services, it doesn't makes sense to have them all running all the time if 4,000 of them have very low traffic. So one of the main benefits is that you get the ability to "increase your library of services at a very low cost". Serverless also really shines with quick stateless actions.
However, converting an app to all serverless is a huge task and for most apps it doesn't make sense.
Two major drawbacks:
1) You're bound to only the language versions that are currently supported.
2) You're writing code specifically for the platform so without a heavy lift you're "locked in"
If the goal is to go serverless and get rid of the server management, I'd suggest looking into containerizing your existing apps and deploying on a "serverless" managed service like Fargate (or your favorite cloud provider's equivalent). This approach is also lets you go to a different cloud provider if you want... or even move back to your own datacenter with no code changes.
Buying a bigger house just allows you to park more of your net worth in real estate. As a diversification it makes sense. But also as you make more money the payment becomes less and less of your monthly income.
It’s not absurd. It’s just a different reason for buying a house.
Then go to the company’s website and look for postings or email them and tell them you're interested.