5 ms·
I find the opposite. I'm fairly new at a company, and worry about not looking bad. Sometimes, things stall. The next morning, I can explain where I got stuck, a
by shubb 12y ago
I find the opposite. I'm fairly new at a company, and worry about not looking bad. Sometimes, things stall. The next morning, I can explain where I got stuck, and get someone who the group trusts involved. If it's a hard problem, and the best programmer gets bogged down as well, I look okay. If they solve it in 10 seconds, I'm unblocked. Either way it's way more comfy than sitting on it for a week wondering when I'll get in trouble.
- jkaunisv1 12y agoTotally. I think it depends on the group - especially group size. The intimidating standup I was describing was I think around 15 developers, mostly working on separate issues. It worked for them because the majority were very self-starting, skilled devs. And I was speaking more to the general idea that OP shouldn't expect everything to bubble up to them automatically, because different people work and behave differently. Learning about that is an important aspect of being a manager.
- undersuit 12y ago>sitting on it for a week wondering when I'll get in trouble. Mandatory participation in a meeting isn't going to stop that. You take the proactive approach and ask for help, but you're asking in the meeting. Why wait? Fire off an email to the last person to look at the code? Send a chat message to the person who wrote that segment of the spec. Flag down your favorite senior developer on their way back from the restroom. The question or problem can always wait until the daily meeting to be resolved, but it can't be answered until you ask.