If everybody gets promoted because of "memorable" work, maybe nobody actually deserves the promotions, and they're just handed out at the whim of whoever remembers your work?
Pretty common in companies these days, I suppose big companies just turn it up to 11.
It's certainly an interesting choice of name!
Should you say "TRY-no" to rhyme with Rhino or "TREE-no" to rhyme with Arduino?
I would do the latter, but I'm a debauched expat. My guess is that half the people in America will do the former.
Because I overthink this stuff I had to go see what's on trino.com and it's an impressively old-school unfinished personal website.
Also, if anyone is reading this wondering which version Athena comes from, it's a release that was common to both Presto and Trino before the fork. However, more recently we've worked with the Athena team on getting the newer Trino features that aren't in Presto today in Athena. So it's starting to become more based on Trino.
I'm confused -- does Facebook not have similar code review infrastructure as Google, etc. That is: nothing -- I mean nothing -- gets "contributed" at Google without it going through code review.
Were FB engineers able to commit directly without review? Or is it that they were given some kind of "owners" privilege to fast track reviews? This all sounds bad.
Typically if a company wants to contribute to open source, you have to create a PR and have it be reviewed and merged by the maintainers of the open source project on top of internal review. Facebook management decided to circumvent that process.
I even remember some of my internal commits making it into FBs open source code on GitHub, even though at the time I had no idea that this specific area of FBs codebase is open source.
Any two people are in a less-extreme but similar boat: if someone puts up a bad diff and someone without a stake in the code accepts it, they had better hope to hell nothing goes wrong.
SEV review is a remarkably enlightened process for what it is, but you do not want to sit there explaining to extreme-seniority people why you YOLO'd something into Presto without buy in from a Presto hacker with your manager sitting behind you already thinking about how much this is going to get harped on in calibration.
The `OWNERS` file at FB is in `hg log`, but it's there.
They finally added a "final review" step to ensure that someone eventually takes a look at these changes after the initial accept, but that still occurs several days after the commit.
https://trino.io/blog/2020/12/27/announcing-trino.html
Months after this consolidation, Facebook decided to create a competing community using The Linux Foundation®. As a first action, Facebook applied for a trademark on Presto®. This was a surprising, norm-breaking move because up until that point, the Presto® name had been used without constraints by commercial and non-commercial products for over 6 years. In September of 2019, Facebook established the Presto Foundation at The Linux Foundation®, and immediately began working to enforce this new trademark. We spent the better part of the last year trying to agree to terms with Facebook and The Linux Foundation that would not negatively impact the community, but unfortunately we were unable to do so. The end result is that we must now change the name in a short period of time, with little ability to minimize user disruption.
(IMHO, PrestoSQL also looked maybe a little too much like PostgreSQL in this space.)
I'm imagining an unusually efficient brandstorming session. "OK, folks, idea hats on, there are no bad ideas... we've got Presto..." "Uh... new Presto... New-o..." "Neutrino..." "Trino?" "Trino!" "Searching it now!"
Although, in this case it was code changes and features that only suited Fb
Starburst spun out from some contributors working on Teradata’s Presto distro in 2017.
The Presto creators left Facebook in late 2018 and worked on building the new community and fork for most of 2019. They joined Starburst around a year later.
I asked these same questions in my last company and it seems like nothing was correlated between starburst and the new fork. After talking with Martin T. (One of the creators of Presto) about it and a few other long time contributors and my concerns went away.
I ultimately started to contribute to Trino and over the years I’ve only seen a community dedicated to making a successful query engine. You can see that by the activity and growth of the project.
Feel free to remain a skeptic but the best way to know is joint the community and make your own assumptions. :)
> Presto, a distributed SQL query engine for big data analytics
> we were forced to rebrand and changed the name to Trino
