I'm not quite sure how to place this. For general app telemetry there's https://opentelemetry.io and for tracking user behavior similar to how it's explained in your docs it looks like https://segment.io would be the closest competitor.
How is telemetry.sh different from the above-mentioned?
That's very fuzzy. What about e-mail? Or the phone network? Or the internet in general? Yes, there can be some social aspects to it. But that by itself does not make it into a social network.
Networks have topologies and paths. The social graph matters on facebook because you get connected to your friend's friends which is a core feature of the platform. This is not the case with chat platforms.
The big problem in academia very often is that you cannot simply take your research and finish your PhD elsewhere. With jobs you mostly can switch without losing much. Obviously depends on the situation.
Relatively minor. Most senior people I know who leave with bad blood end up with equally senior roles, and often "fail upwards" to even more senior roles in another company.
Bonuses/Vesting: Very common to get good vesting at a new company to make up for what you're losing. Of the people I know who've moved, it's the exception that didn't get decent replacement for vesting.
Resume damage: What? Person spent 4 years at a company and left. What resume damage? Your experience still counts.
Contrast with a PhD who leaves in the middle of a program: The years he spent are 0. Generally, the experience/knowledge accumulated is not factored into it when he applies elsewhere for a PhD - unless he has some fantastic publication.
Still, this is the good outcome - I've often seen students leave an advisor or school and succeed elsewhere. The real danger is when you get your PhD and the advisor will not write letters of recommendation. Unless you've made some really special connections, it means your academic career is over. You won't get a post doc. You won't get an academic position. You won't get into a national lab. And depending on your field, you won't get a research position in industry either.
> Contrast with a PhD who leaves in the middle of a program: The years he spent are 0. Generally, the experience/knowledge accumulated is not factored into it when he applies elsewhere for a PhD - unless he has some fantastic publication.
When I relised this kind of power inbalance during my PhD resulting docile behaviour of my collegues and partly myself, I even did not even wanted to chage my supervisour nor make a protest as the power inbalances are normalized. This awareness made my PhD easier as I did not put false hopes and did not invest my leisure time into becoming more specialised or come up with my own ideas which could latter be turned down to not allign with funded project as my collegues did. I found the remedy in fight for a better tooling and investing my leisure time in completely different field in which papers were still not been written by robots.
Those are a thing but probably not as bad. You may gain seniority. The second is unavoidable. The last can be dealt with and there are levels of ethics around that.
In terms of complete house power - Batteries are fantastic for a small size use case, but economically difficult in large size. I have 42kwh of battery storage (Enphase), plus 20kw of Solar generation, but that combined is not enough to cover a complete power outage longer than 24-36 hours in stormy weather. The cost of that system is well more than 10 times the cost to get a generator that can do the entire house (22kw Generac for example).
They basically killed off all the other minority languages they had in their country (like oxitan) and homogenised on standard French. Some irony in that.
I've checked in America before and came to the same conclusion. There's an idea that COBOL programming pays vastly more than other languages, but it's just a myth. It might pay a little more, but more like 20% more. Certainly not enough to warrant a COBOL career.
And I'm sure some consultants can earn vast sums fixing old COBOL code, but that's just because they're consultants. Consultants always earn vast sums.
I don't understand why people are claiming this sets your career to only ever write COBOL. I know plenty of people who started their careers with perl, but have been Java, JavaScript, TypeScript, Go, or Rust programmers at different points as their careers progressed.
Someone overseeing a project migrating a COBOL monolith over time to a set of decoupled services in some other language would easily have a strong story for the timeless need of improving application architecture.
