Hacker News new | past | comments | ask | show | jobs | submit login

If the author didn't want to do the work to learn the ins and outs of the company she's being hired by (and yes, almost every company has a few quirks in their internal systems), why did she even apply?

Did she ask for a non-terrible laptop? Was she rejected? The article doesn't mention this.

Did she _ask_ for a desk? If they're onboarding many people at once, there's always a chance something can get missed.

I think a lack of communication was the main problem here.

Not defending her but 'asking' for a desk sounds ridiculous. Should she also ask for a chair? Power outlet? Access to toilet?

She ducked out of the onboarding early. When I onboarded at my current company, desk assignment was the last thing that happened- once they sat you down at your desk, HR was done with you and you were your manager's problem now. So if she peaced out of onboarding at noon and desk assignment happens at 3, I can easily see how she slipped through that particular crack.

Regardless, if there's a problem, it's the company's fault. If you don't try to fix the problem, it's your fault. It may or may not have been her fault that she wasn't assigned a desk on day 1. But it was definitely her fault that she didn't have a desk on day 3.

IMHO navigating bureaucracies and getting institutional stuff like this fixed is a really important skill that software developers tend to be awful at. My first "job" out of high school was in the air force- so navigating institutional garbage and persuading ineffectual people to do their damn job is something I'm pretty good at. But now I look around at frustrated young devs who don't know how to navigate the bullshit, and it drives them bananas. This article is a prime example. There are basically three kinds of problems:

1. Problems you fix yourself. 2. Problems other people fix, but only once you complain (loudly enough) about them. 3. Problems that are never gonna get fixed, no matter what.

Developers tend to be really good at the first kind, absolutely terrible at the second, and fixate (to their detriment) on the third. If you can't fix it, don't stress about it. And don't stew about something you can fix with an email.

I may have answered with a bias. In all jobs I had, on the first day you're given a desk, PC and everything you need and you spend half of the day onboarding, other half usually setting up accounts for various stuff.

So from that point of view not having a desk for first few days I'd feel lost and like a visitor, not employee.

I have no experience working for tech giants and large shops (100+ people per location), so I may be blind to usual practices.

It sounds like you read 'ask' as 'beg'. You shouldn't have to beg to be allowed to use the bathroom, but you can absolutely be expected to ask somebody if the bathroom is locked or you cannot find it.

You shouldn't have to ask for a desk, it should be there when you start. But if it's not, you should definitely ask for one, not wait in the corner until one magically appears.

So, how come no one greeted and guided her from her team? (Not friends from other teams.) The team lead, the manager? (Whatever those mean, of course.)

This whole company sounds like a sitcom.

> You shouldn't have to ask for a desk, it should be there when you start.

If the author decided unilaterally to skip the onboarding process and appear unexpectedly and unannounced at somewhere she assumed would be her workspace then she wasn't there when she was supposed to start.

Would it also make any sense if the author whined about the company not providing her with a computer if she happened to also skip that part of the onboarding process?

Of course they should be provided. The problem is that onboarding processes usually are so complicated that the organizers forget things. It's okay to remind them.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact