Look at your favorite VC’s websites and they usually list their portfolio companies. Find some companies that interest you.

Then go to the company’s website and look for postings or email them and tell them you're interested.

You have to test restoration as part of SOC 2, so most companies with real customers do it at least once a year.

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.

Before you quit your job make sure you own it.

I think it would only matter for something that is quite significant. And in that case, you would probably quit long before it mattered.

Careful, you can still be sued by your past employer even after you quit.

How can they prove when where and what. Ive never seen this happen and largely think its FUD.

I mean if you have git commits from that period it’s pretty easy to track it

commit after hours or weekends

that's not exactly how those work (they can claim an invention if it's done during work hours, with company equipment, in the business area of operation. Might differ from state to state, but that's the gist of those contracts

It varies by state, what you described is California's rules, which are by far the most permissive of moonlighting.

Note that it's an "or", not an "and":

i.e. your employer can require you to assign the invention to them if it's done during work hours OR with company equipment OR related to the company's business.

The full text in the California labor code is here:

https://leginfo.legislature.ca.gov/faces/codes_displaySectio....

There’s only a few states (CA and few others) where the employer can’t claim IP developed on your own time and equipment. The other states absolutely can.

Most indie developers are not developing IP of interest to anyone other than the indie. Without marketing and continued development the IP is of little value.

Yes if you invent the next google in your spare time you could be in trouble. For this it’s best to get funding. At the lifestyle income level, your employer doesn’t have the time or money to waste on your passive income stream.

Obviously don’t be cavalier about it, but this will just get you fired not sued.

highly depends on your employer and your relationship to them. I've heard of cases of someone getting sued due to _an open source_ they maintained, simply out of pettiness.

wow

Honestly what you need:

vulnerability scanning of your images.

Fargate

RDS

I dunno. I've seen a _lot_ of business ideas fail, which could have much less expensively failed using PHP and MySQL on shared cPanel hosting than they did using AWS/Azure/GCP.

Yeah, that won't scale to a million QPS, or even 10 QPS. But way more businesses fail because they never achieve 100 Queries Per Day, instead of failing because they fell over at 10 or 1,000 or 1,000,000 QPS.

I mean, hell, Twitter (back in the day) was famous for The Fail Whale.

Getting enough traffic is harder and more important than your "web scale architecture" for your startup. Making actual cash money off your traffic is harder and more important than your "web scale architecture" (ideally by selling them something they want, but making cash money through advertising or by impressing VCs with stories of growth and future value counts too).

There is precisely _zero_ chance that if you ever get within 2 or 3 orders of magnitude of "a million QPS" - that the code you and your cofounder wrote won't have been completely thrown away and rewritten by the 20 or 100 person engineering department that is now supporting your "1000 QPS" business.

Agreed. I did the same thing and immediately closed the tab

ELB with WAF -> Fargate -> RDS

Why not use a single Fargate task?

All my teams infra runs on fargate + ECS so I'm pretty familiar (and happy) with it. Running in fargate requires knowlege of AWS: VPC's, public and private subnets, security groups, ECR, ALB's, Target Groups, IAM policies + roles. Then, when you want to add a databse, you're back into all of the above, plus the database specific ones like database subnet groups.

When it comes to health checks you have docker health checks, container health checks, load balancer health checks - all of which are configured separately.a Not to mention, doing it "properly" where your task doesn't have a public IP and is only accessible through your load balancer - [0] might be one of the most infuriating responses on stackoverflow.

Meanwhile, with DO droplets, it's pretty much "here's a registry URL, and some configuration in YAML, go for it".

[0] - https://stackoverflow.com/questions/61265108/aws-ecs-fargate...

Alpine is also based on MUSCL rather than glibc which generally has fewer well known CVEs which helps from a security standpoint.

Is that because it's got better security, or fewer eyes on it?

Both.

How many total shares have been issued?

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.

AWS Fargate connecting to RDS