6,601 karma · joined November 26, 2008
github: https://github.com/rofrankel
[ my public key: https://keybase.io/rofrankel; my proof: https://keybase.io/rofrankel/sigs/7DPtXmkHbxS-4enOKOcWzFRZ7QEllKlnBUcYMO7tQPM ]
I started using jj a few months ago. I had used Fig previously when I was at Google, but then spent over 2.5 years just using git, and using jj was like riding a bike. It's more or less exactly what I want it to be and I use it as much as I can.
That said, here are some of my pain points (despite all of which I do still prefer jj to git):
* No GitHub PR sync for stacks. Managing stacked diffs locally is great, but (a better version of) Sapling's PR syncing would be a huge value add. This is somewhat of a pain point for me directly, but even more so a weakness when I've tried to evangelize jj internally as a viable "stacked diff" solution (e.g. to be blessed by our eng tools team). Someone familiar and comfortable with Sapling (or just skeptical of jj) can easily point to this feature gap in a way that pretty much ends the conversation.
* I wish the native backend supported pushing/pulling changes. I want to be able to switch between working from my laptop and my workstation, and doing that through pushing to and pulling from GitHub is obviously lossy of jj history. Manually copying the .jj directory seems to work if I'm careful and do everything correctly (i.e. make sure both clones have equivalent working copy state when I copy .jj), but this feels brittle and it's easy to mess up.
* If you forget to start a new rev before you (or your LLM) touch the repo, it's a little bit of a pain to go back and split the changes into a new rev.
* Some of the more mature repos I've worked with have tooling/scripts/tests/etc. that seem to look for or rely on the presence of .git (perhaps indirectly). Perhaps I could have gotten around this with colocated repos (i.e. `git clone` and then `jj git init --colocate`), but in at least one case I just gave up on using jj for a given repo and just made a separate git clone. I'm not sure this is really jj's fault so much as a practical compatibility gap with git (again, possibly entirely solved by using `--colocate`).
I actually attribute it to Ruth more than Sundar, but who really knows? All I know is I saw a major decline...and people were already saying similar things when I joined, and they were probably right too.
This isn't to say Google isn't still a great employer...but yes, perks and comp declined.
More seriously, for me it's the "likely".
Does that make line managers better or worse at being line managers? Probably not. But it may affect the experience of being managed if your manager is more or less stressed about fighting for headcount, figuring out who to lay off, fitting performance review ratings to a curve, etc.
I also found myself applying into a black hole. But when I used second degree connections to get someone at the company to acknowledge I existed, everything started moving, and I ended up with great offers from both the companies I had applied in.
Sometimes there are ghost roles, but sometimes recruiting is inundated or disorganized and you just need an internal champion.
Judaism is based on matrilineal descent, so depending on where the DNA comes from, yes.
I use Lyft 99% of the time (and multiple times a week) because I find it to be more reliable (as well as slightly cheaper) than Uber. It doesn't seem destroyed to me.
You are mixing up "quit -> best" and "best -> quit".
This has not been my experience at all.
(Disclaimer: I'm a Roblox employee, but speaking only on my own behalf, and don't work on anything related to age guidelines.)
Roblox pays very competitively (see levels.fyi). The apparent strategy is to try to hire lots of long-tenured L6+ Googlers (seriously, it's crazy how many former Googlers I work with).
Though in this case, in his defense, average people will never hear about Roko's Basilisk.