Thanks! Not sure how many are a handful, but your first 5 customers are free (no matter how many different contracts you send them). You're still welcome to download and use the contracts
While we certainly are using technology to help solve the problem, it's more about creating contracts in a way that helps you focus on the key changes from contract to contract. When you build on immutable terms, and the only changes are in the contract's cover sheet, you can focus on the changes and not hunt down for words inside of an inscrutable PDF.
Small startups don't need contract management until they reach a point and then they wish they started doing it from day 1. :)
"hyper-standardized contracts" I suggest you take a look at the app! While our terms are immutable, the contracts can be heavily customized. So instead of hunting down a random word in a PDF you can focus on the things the material changes from agreement to agreement.
1. We didn't model it after a specific open source project, but Jake worked on https://www.singer.io. We do take inspiration from Open Source licenses like Apache 2, GPL, MIT, etc.
2. Open source in the sense that the terms of the contract are open source and released under a CCBY license. Terms are available via versioned URLs, github markdown source control, and maintained by a committee of contributors (attorneys).
We've released our contracts API! The Common Paper API allows you to create and send new contracts while channeling alerts to the people and systems who need them. The structure built into all of our standard agreements enables programmatic access and a consistent data model. This opens up a world of possibilities for automation, compliance, and integration.
You have an idea for how a fair and equitable job search is supposed to work.
It does not work like that.
Almost half of all jobs are filled through referrals by existing employees, so if you're cold applying to a company you're at best, cutting your chances in half and wasting your time.
You're also forgoing important information _for you_ if you don't know anyone at the company you're applying to. How do you really know what it's like to work there?
"The whole thing makes me feel increasingly insecure..." Don't get discouraged! There are tons of really great opportunities out there.
I don't know. They've added a ton of underwater content, new structures, mobs (bees, foxes, llamas, phantoms, drowns, etc), sunken ships and treasure maps.
If anything, they've had a better release cycle since the acquisition.
1. Use RI's (like you said) and make sure your utilization is high.
2. Look at any under utilized EC2 instances and make them smaller. If they are very under utilized, consider moving what they do to Lambda, which is very cheap.
3. S3 for everything storage. Only use EBS volumes when you need to.
4. Someone mentioned multiple availability zones and it's a great tip. Turning it on is 2x the price for RDS, and it's probably not needed for anything but critical instances.
5. Make sure unused instances are terminated, not stopped.
6. For very expensive systems, use spot instances to strategically reduces your costs when ec2 instances are cheaper.
7. Try to keep your instance types down to a few types. This will give you fewer headaches when you go to purchased reserved instances.
I ignore stash completely by committing with -a and simply not worrying about the commit history so much, since they'll all be squashed anyway.
Never used the --oneline option before and I LOVE it. Thanks!