Don't buy at IPO. Buy after the lockup expires.
How do one check this?
Its usually 6 months. But there may be an alternative 'limited' lock up triggered earlier if the stock price is above a certain level continuously for a certain period of time.
HashiCorp IPO today
191–200 of 206 posts
Re: HashiCorp IPO today
#192Earlier quoted context omitted.
Cloudflare(NET) was ~$18 at IPO. It was ~$19 at lockup expiration 180 days later(versus nasdaq being a few percent down). If you bought at IPO you'd be up 734% but at lockup you'd be up only 688%.
Oh come on. NET stock was and is so volatile that a 5% difference is hardly anything to go by for future decisions
Right. My point was that timing of @IPO or at the end of lockup was largely irrelevant
Re: HashiCorp IPO today
#193Earlier quoted context omitted.
Employees who own shares before the IPO are often prevented from selling them right as the company IPO, that's the lockup period. After this period (often 6 months), they are allowed to sold their shares. The reasoning of GP is that a lot of shares will be sold right after the lockup expires (because employees want to cash-in/diversify), artificially depressing the price.
Are the executives included in these measures?
Yes. However, a significant portion of Tech IPOs have a modified lockup which allows selling of a portion of lockup shares based on some event triggers (earnings release + stock performing +x% from issuance price). Lockup agreements are negotiable and can vary from one IPO to another.
Re: HashiCorp IPO today
#194Re: HashiCorp IPO today
#195Earlier quoted context omitted.
The employees' shares are tax based on the IPO price, not the price at which shares beginning trading. So with a large bump (like 100% on Snowflake for example), you defer a lot of tax to the future. And if you hold out 1 year until selling, you change a lot of that gain from income into long term capital gains (which has a lower tax rate)
Any actual shares an employee owns at the IPO will not be taxed until they sell them. You might be referring to the synthetic RSUs that companies have been issuing that convert to real RSUs at the IPO (or acquisition) which does incur taxes.
Sure, "synthetic RSUs", or "double trigger RSUs", or such. But people call them RSUs when discussing the details of their job offers.
Re: HashiCorp IPO today
#196Earlier quoted context omitted.
I don't know a single person who prefers HCL over literally anything else, but still, it's a happy day for them so I won't air my entitled little complaints and instead say: thank you hashicorp! You made life as a cloud infra beard better for a while, and I wish you all success going onwards.
I've come full circle on this and actually like HCL now. It's so limiting that there's often only one (or a few at most) way to feasibly do something. This is kinda painful when your team is small, but becomes a net-positive in a larger team.
The real pain comes from when there's zero ways to do a thing.
I'm tired of config languages. Just be a library.
Re: HashiCorp IPO today
#197Earlier quoted context omitted.
"we" as a company as opposed to the authors spontaneous feelings. I don't know about the nerd thing though
Does that mean that 0des is speaking as a Gitlab employee here? I'm sorry if the question is stupid, the whole thing sounds very confusing to me.
As far as I understood, the criticism is that OP as a chairman of Gitlab used 'we' to refer to the whole company as opposed to his own opinion. The criticism then refers to an appeal or sympathy grabbing with an economic motivation.
I couldn't care less to be honest, just clarifying what I understood.
Happy for Hashicorp, also love Gitlab.
Re: HashiCorp IPO today
#198Earlier quoted context omitted.
I would have preferred HCL
I don't know a single person who prefers HCL over literally anything else, but still, it's a happy day for them so I won't air my entitled little complaints and instead say: thank you hashicorp! You made life as a cloud infra beard better for a while, and I wish you all success going onwards.
HCL is bizarre, but I'd take it over writing configuration in yaml or json any day.
Re: HashiCorp IPO today
#199Earlier quoted context omitted.
I would have preferred HCL
I don't know a single person who prefers HCL over literally anything else, but still, it's a happy day for them so I won't air my entitled little complaints and instead say: thank you hashicorp! You made life as a cloud infra beard better for a while, and I wish you all success going onwards.
I prefer HCL over everything else that's currently in use. Especially over YAML.
Re: HashiCorp IPO today
#200Earlier quoted context omitted.
If you're at a large company, the only thing worse than dealing with processes is dealing with the chaos you have in the absence of processes with everyone running around doing their own thing. (Obviously there can be bad process as well.)
Those aren’t really related everyone can be running around doing their own thing (but slower) with a process - that’s usually a sign of leadership vacuum not absence of the process.
This is why self-leadship is vital to “agility” - individual interaction before process and tools.
Someone wrote, perhaps Tom DiMarco: “a process is per definition not agile”.