I'm surprised these models haven't picked this up yet in the training data. Both Claude and ChatGPT missed that one when I posed the question to them last year.
>The main reasons to drive such a short distance would be if you're bringing the car specifically to be washed, carrying something heavy, or the weather or walking conditions make it impractical.
>If your goal is to get your car washed, you'll need the car there—so driving makes sense. If you're just going to talk to someone at the car wash or check it out, walking is probably faster.
There's meaning in the term "car wash" that it understands. But I don't suspect anyone has taught it that for 99.9% of people, going to car wash ONLY means that you're going to wash your car and that it should make that implicit assumption.
What if you're the car wash owner? Or a maintenance technician? Pretty easy to just walk over there if you're just 50ft away.
to your point, when my Aussie friends first mentioned a "car park" to my north american born self, i wondered _momentarily_ what that was, then realized it's sort of a fun name for what i would call a parking lot.
yeah but syntactically "car park" gets used like a noun phrase, not verb phrase, which was (to your point really) what had me think "huh?" momentarily.
This 100%. An actual honest answer got me my first post-academia job. I had originally tried the "I'm introspective, so I actively work on any problems I find." When I could tell the interviewer was not impressed with that answer, I just fessed up. "I'm impatient." Not only was the honesty refreshing, but the interviewer shared the same problem. It was a nice bonding moment.
Notice that the blog post author did not provide exact quotes. In fact, they explicitly state they do not remember the wording. It's very likely that they did, in fact, ask about biggest challenges, and the author misunderstood.
Keeping in mind the context of the original parent comment, yes it is 100% standard to ask about the "hardest day of your [working] life." I wouldn't ever put it like that, but asking about difficult challenges and how you overcame them is completely normal. The blog post reads to me as someone who is oblivious about the subtext of these questions.
When I ask that kind of question, I'm not asking you to share about a breakup, or death of a parent, or some other non-working issue, and I would think it very inappropriate for you to do so (thus, the quick rejection email). Instead, I'm asking about how you navigated losing all your code due to a backup issue or how you dealt with a difficult client or coworker or even some problem at work that threw you for a loop for weeks. That's the subtext of these questions, as the original commentator also made quite clear.
> Instead, I'm asking about how you navigated losing all your code due to a backup issue or how you dealt with a difficult client or coworker or even some problem at work that threw you for a loop for weeks.
Cubicle drama, hey?
Easy stuff. I've got a million+ SLOC behind me, no real cubicle stories worthy of note resulting, just had a few days at work clearing air strips at high altitude in Papua, had to work for a couple of weeks at gunpoint after one of our lovely clients detonated a nuclear device near enough our plane for the shock wave to affect the flight dynamics, nearly lost a whole boat to a fire under the kerosene filled float cables in the Spratly Islands region (after getting boarded constantly by various gunboats).
I think I didn't quite catch the layout here. I thought you were responding to KaiserPro above, so mea culpa. I agree that asking about one's personal life is not (or rarely is) appropriate. I think the blog author thought that was the case, but was mistaken.
You are paying restaurants for food to be prepared in the way you want. But this is not the same. Someone created some content the way they want. You haven't ordered that content. And you complain it's not prepared the way you like.
I was feeling like sneering as well about how my emacs setup never caused any issues until I remembered emacs packages have zero protection whatsoever and can run anything anywhere, are ALL authored by some guy in Nebraska or Slovakia or something in their spare time :) but we don’t see any attacks since there’s so few of us still using emacs.
reply