@mattturck @semil Yeah, we’ve had to let a handful of people go over the years for this. Other things that popped up: (1) someone joined while on paternity leave for another company, was working full time but collecting two paychecks, reckoning came when that paternity leave was up… @mattturck @semil (2) we had someone join and they were splitting the work with their spouse. This was a weird one to catch.

(3) we had someone join who contracted out the work to other people for cheaper.

Actually, these are all weird to catch. But, over 1200+ employees, super super rare haha

(1/10) I think it has been long enough that I can share a fun, interesting part of HashiCorp's history: In 2013, Armon and I were offered $50 million for HashiCorp. Note this is pre-Vault, pre-Terraform, and we still owned 80% of the company at this point. We said no. Read on! (2/10) This seems like an easy yes. $50 million is a flabbergasting amount of money (we were 23 and 21 years old at the time). And we genuinely liked the company that approached us. My immediate internal reaction was: hell yes. 🤑 💰

The force to remote for much of the workforce is going to be very positive but also create a ton of FUD. Lots will “get it” and it’ll work for them and they’ll be forever changed. Many will realize it isn’t as simple as pretending your at-home desk is your in-office desk. It also just isn't going to work for some people. Not everyone is compatible with remote and that's _okay_. We've had numerous people over the years quit HashiCorp saying "loved the work, loved the people, but I just need in-person social interaction." That's totally normal.

1/ When delivering software to enterprises, you usually must also provide support for all software used under the covers. Example: if you depend on Redis, you or SOMEONE need to support Redis. Makes sense, right? If your dependency causes YOU to go down, you need support. 2/ This seems obvious, but has surprising implications. One, you can’t shrug when a customer asks where to get that support. Either you provide it or you suggest someone because your own sales deal isn’t closing until they figure this out.

1/ An interesting part of HashiCorp history is that we’ve had over 8 years of experience supporting different configuration paradigms across well-adopted products. Vagrant is pure Ruby, Packer pure JSON, Terraform introduced HCL+JSON which we've adopted into Consul, Nomad, Vault 2/ And we've learned a lot in those 8 years. First, no one paradigm will make everyone happy and quite the opposite, you'll get continuous quite hyperbolic emails/tweets about how your decision was COMPLETELY WRONG, about every paradigm.

1/ Video conferencing software still has a long way to go and I think there is still huge opportunity there for newcomers. Its core tech for remote-first companies. Everyone seems focused on the core problem but as more companies grow remote its time to go higher level. 2/ Support video categorization, sync to Dropbox, Drive, etc. Some do this, but others just give you a giant video file at the end.