News for hackers. Stuff that matters.
Re:Why I Quit Google to Work for Myself by meesles on Wednesday February 28, 2018 @01:35PM (#16485416)
A new repo, likely a new employee on a new project. I have to disagree with your statement since you don't know the context at all. If all they're given is a repo with inadequate instructions, there's not much more you can do than keep asking for general help.

Comment sounds like typical 'pull yourself up by the bootstraps', meant to put down new talent, ignoring that complex, modern dev environments have many parts that are completely out of reach for newcomers without adequate onboarding.

Like you said, why not both? The employee is already asking for help, that's their part. The manager needs to come in and assist, unless he enjoys churning his dev team.

Re:Why I Quit Google to Work for Myself by MadBohr on Wednesday February 28, 2018 @01:57PM (#16485644)
> I'm completely blocked for the last two days because I cannot run the repo, so I cannot run any tests and at the moment I'm doing absolutely nothing.

That is not asking for help. Asking for help would be "Can somebody please help me? ... rest of message here...". Even better is asking an individual (or individuals) directly.

Re:Why I Quit Google to Work for Myself by epicureanideal on Wednesday February 28, 2018 @02:42PM (#16486076)
Nonsense, this is asking for help. As a former manager of a tech team, if I had seen this I would've taken action, and as a team player individual contributor I would've taken action even if I were not a manager. I appreciate you sharing your perspective, but in my opinion you're leaning too far to try to find some way to blame this employee for processes that an employee should reasonably expect a competent management team to have solved already.
Re:Why I Quit Google to Work for Myself by sangnoir on Wednesday February 28, 2018 @02:56PM (#16486207)
> That is not asking for help.

Say what now? Mentioning you are blocked, in a stand-up, multiple times is a cry for help. What is the point of having stand-ups if you're not assisting blocked team members?

Re:Why I Quit Google to Work for Myself by dalore on Wednesday February 28, 2018 @03:13PM (#16486364)
He mentioned that he brought it up in the standup. The standup is when you announce blockers. Was no one else in the standup listening when he said he was blocked? That's when someone goes oh here is what you do.

The standup is for blockers to be announced. It's the 3 stage of the standup.

Sounds like poor management, don't blame the new guy, he did say he was blocked in standup. How is he to know who to ask. Whose time can he impinge upon. It might be he asks someone who helps him but he gets in trouble because he now took up that persons time from something else.

The manager should see oh he is blocked, I'll assign so and so to help unblock him.

Re:Why I Quit Google to Work for Myself by pyrale on Wednesday February 28, 2018 @05:45PM (#16487930)
"I'm blocked" is the strongest type of distress signal in terms of workflow. If you don't investigate that, what else would you investigate ?
Re:Why I Quit Google to Work for Myself by jimbokun on Wednesday February 28, 2018 @11:51PM (#16489764)
This person probably DID ask more specific questions. They were just describing the gist if the interaction. Not a literal copy paste of the exact messages.
Re:Why I Quit Google to Work for Myself by ManlyBread on Thursday March 01, 2018 @05:19AM (#16490916)
Having my blockers completely ignored for a significant amount of time was a major factor in deciding to find a new job. There are only so many times you can beg for libraries, source code, permissions and other essential tools before coming to a conclusion that maybe somewhere else there is a place where you don't have to deal with this bullshit.
Re:Why I Quit Google to Work for Myself by s73v3r_ on Wednesday February 28, 2018 @03:36PM (#16486615)
Only the most dense of people would think that isn't a cry for help.