its_a_random_ac

I'm not accusing the author of doing this, but providing a simple base64 encoded blob at the end to run to enable everything would be a pretty easy attack vector, wouldn't it?

edit: just decoded it and touché

Yeah, I'd like to know too, from everything I can see it's just a cloud-hosted notebook with a spark backend, which does have some benefits, but I can't tell why they got as big as they did.

Also from a more cynical side, I've interviewed at a lot of companies that ask if I've used it before, and I'm really temped to just lie, since it feels like something that could be picked up really easily.

Yeah, I thought it was a reference to the DIY assisted suicide book, Final Exit.

As an ethical-vegetarian, these are very much not for me, but I've also noticed this weird thing where some restaurants (Sushirrito's the most recent one I've seen) drop their traditionally meat free items and replace it with something that is just a meat item with the meat subbed out.

I get why they want to do this for streamlining purposes, but it doesn't make any sense to me. People that want to avoid eating meat will still avoid it, but also the differences need to be taken into account regarding texture and seasoning, which it doesn't seem like they do.

Pretty good overall, except for a nit pick:

> Person B: “…. Hey, sorry to interrupt, but the story in my head is that you think owning that number is part of my job, and now you’re upset with me, or you think I’m incompetent at my job.”

Depending on the exact phrasing and group and company dynamics, I'd be worried a bit by saying something like this because Person A might think I'm trying to push off work or responsibility for some metric that I'm tangentially responsible for.

Kinda of crazy, my first computer had a million times less ram than this.

Something I've run into is that a while ago, there were "Type A" ("Analysts") and "Type B" ("Builders") data scientists [1] , but most job postings now are just looking for "Type A" data scientists, and the "Type B" openings have been renamed to "ML Engineer" or "Data Engineer."

Took me for a bit of a spin because when I was first interviewing this year, I'd apply for DS roles and only get interviews that were very stats heavy with a leetcode easy, but started getting further when I basically stopped applying for DS roles and went straight for MLE roles.

[1] https://medium.com/@rchang/my-two-year-journey-as-a-data-sci...

Spoiler alert: be prepared to spend a ton of money of gas, and hours for driving to any kind of doctor's office beyond a GP. A friend of a friend commuted for 4 hours each day to go to school as a kid because her family lived so far out.

I still agree with the general sentiment though. I'm happy with living in a 1br condo and taking public transport, but I had coworkers that "needed" a detached house with a back yard and a moderately expensive car.

Great, now I'm thinking of my edgy teenage days calling them Micro$oft or just M$ on Gamefaq's forums.

Yes, that's mostly been my experience (6 years + masters, Bay Area/remote positions.)

A few other things I've noticed:

1. Yes, I've had the "candidates with perfect skill/experience matches get the same generic rejection" but I've also had times when I'd apply for something that I had only a little bit of a match for, and still get pretty far through the interview process.

2. Related to #1, I can't get a good feeling of how qualified I am for these listings. Sometimes I'll apply to something that is in the low 100ks with a customized resume that echos all of their reqs and get rejected, but other times I'll just blind fire out my standard resume to something with a base in the mid 200s and get selected for a full interview loop.

3. It feels like some places still have the same "standards" for each part of the interview process, leading to a lot of candidates getting to the end, which then leads to some weird "you did well but we chose someone else" responses.

4. Sometimes I'd have an interview lined up, but then right before it I get a "due to shifting requirements, we have to postpone this by a bit" email. This has happened several times now (and they never have actually un-postponed it.) Same thing with spending a day or two interviewing at a place, not hearing back, and then reading of a large layoff at that company a few days later.