TGS is comparable to Medallion. The two have competed for talent in the past, and TGS actually spreads higher AUM over fewer people. TGS just doesn't have satellite funds, so they're quieter.
No public data in recent years but if you dig a little deeper you can find bits and pieces here and there about their past. Not sure what name they trade under these days because I can't even find a 13-F.
The entirety of cpython’s runtime is exposed as a C api, so you can easily manipulate python objects in c or any language with a ffi. boost::python provides a c++ wrapper for cpython, which can be used to call both c/c++ in python and vice versa
hmm, from what I have seen, $400k is usually their de-facto salary that gets junior folks (L4/E4) from F/G to make their top of market and move to NFLX. Beyond that, do you know how the comp progression is?
Your best bet is to:
1st) request nicely from the CFO some updates
2) if that doesn’t work, flex some inspection rights to get him to give you the updates.
You don’t actually want the inspection, and for me it’d take a court order before I allowed it, so your best bet is to play nice and be less of a pain in the ass to get what you want then litigating it.
Let me stress this again, you are a supplicant in this, you are far better off begging and cajoling and politicking with the CFO to get what you want if it’s important to you. You have zero leverage.
If I got a request from some random ex-employee shareholder requesting info, I’d say to them “see you in court” guessing that you don’t have the $100k’s in legal expenses needed to actually force the issue
From what I have been seeing, the number of both Indian/Chinese students coming to the US for studying has gone down post the Trump administration. Also, I am seeing more Indian/Chinese folks going back home due to increase in engineering wages/opportunities. Of course, it's still not comparable to US but plenty-enough to live a very good life-style back home.
I’m not sure if it’s gone down during the last 1.5 years of the trump admin, but it has exploded in the last 10 years. Looking at the data. Looking at the change for any given year is a bit noisy.
China has really great wages for programming (I should know), but lacks in many quality of life factors. For example, many Chinese won’t go back once they have kids because of educatio, hukou, and pollution factors. They would have to pay a lot to get around those.
What was Github's current valuation? It seems that the last round valued them at $2b in 2015. Around ~3x multiple on the last round (~7.5b$). Hopefully, the employees are all happy!
As twk3 has said, we have examined multiple other options.
One big reason we've chosen to implement with Kubernetes is community adoption. You can now run Kubernetes on AWS, GCP, Azure, IBM cloud, as well as a slew of other platforms both on-premise and as a PaaS. With the expanding ecosystem, our decision has only been further confirmed, as the list of available solutions and providers continues to grow rapidly (https://kubernetes.io/docs/setup/pick-right-solution/)
Another big reason is far simpler: ease of use and configuration. A permanent fixture in our work for Cloud Native GitLab has been that this method must be as easy, if not easier to provide a scalable, resilient, highly-available deployment of GitLab at scale.
We can’t say, “This is our new suggested method. By the way, it’s harder.”
What we have found is that many other solutions require a much larger initial investment of time to understand and configure GitLab as a whole solution, as compared to the combination of Kubernetes with Helm. Helm provides us templating, default value handling, component enable/disable logic, and many other extremely useful features. These allow us to provide our users with a practical, streamlined method of installation and configuration, without the need to spend countless hours reding documentation, deciding on the architecture, and making edits to YAML.
At GitLab, we did evaluate Mesosphere DC/OS. What turned our focus to Kubernetes as our primary cluster install target was the speed at which it was developing, and after watching the space and talking to partners/customers we formed the opinion that Kubernetes was going to lead the pack.
We've been looking at these technologies for two years now, with our focus being Kubernetes for the last one.
GitLab has been investing significantly in Kubernetes, both because we believe in the platform but also because we see significant demand from our customers as well. It's ability to run on-premise as well as availability in a wide variety of managed cloud flavors is a huge benefit, and likely a driver of the demand.
We also try to use the same deployment tools for GitLab.com that we provide to customers, and this lets us offer a scalable production-grade deployment method that can run nearly anywhere.
