auspex
Then go to the company’s website and look for postings or email them and tell them you're interested.
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.
Before you quit your job make sure you own it.
vulnerability scanning of your images.
Fargate
RDS
What’s the fully diluted number?
How many shares am I getting?
Those are the important questions.
Assume you get diluted for every fund raise.
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.
I’ve done both with no issues.
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.
It’s not absurd. It’s just a different reason for buying a house.
Environment variables seem to be the standard.
Direct dependency is usually bad and injecting files violates the immutable nature of a container.
You don’t have to create the wave. Find an existing wave grab a surf board and figure out a way to ride it.
X equals opposite of B + or - square root… b squared minus 4 AC all Over 2 A… yay!
Not using a library !== not vulnerable.
Like I want to shoot in the 80s in golf, run a 7 minute mile or whatever. It helped me find a love for it because it was a way to “train for my goal” rather than an everyday slog.
After about 4 weeks I started to look forward to it and really went down a rabbit hole optimizing workouts, sleep and food.
It can be really fun!
Teamwork, acting/thinking under pressure, detailed preparation, controlling nerves, performing in front of crowds (with high expectations), pride in your body and performance.
These are just a few high level/low hanging fruits learned from competitive sport.
They provide the facilities and a prescriptive plan to get the team where they need to be game ready. Drills, strategy and ensuring everyone is operating as a team on the field.
Tuning their body is the responsibility of the player. The teams aren’t sending them a list of what to eat, how to train or what exercises to do. That’s on the athlete.
Of course they do have specialists to help if the players needs but it’s not “total control for performance”
Frame it with “I can tell you what works for me, but everyone is different and there are a lot of ways to do things… <advice/>”