4 ms·
Was there until > ... you schedule meetings with... I get what the author is saying, but I think they chose a way that's likely to be misunderstood. A good >
by ethbr1 2y ago
Was there until
> ... you schedule meetings with...
I get what the author is saying, but I think they chose a way that's likely to be misunderstood.
A good >senior engineer:
- Understands the problem space
- Understands what the team has done
- Understands the value goal
- Has researched alternate approaches
- Finds and introduces the right people
- Guides the conversation productively
- Ensures everyone understands post-meeting
"The meeting" is a necessary but in no way solely sufficient component of that process. The staff engineer is providing value through all the other pieces.
tl;dr - Don't just schedule meetings: engineer productive exchanges.
- codemonkey-zeta 2y ago100% agree, but I think the author was try to keep their description concise. I have worked with people who will readily schedule a meeting when an issue arises, but won't do the actual work to run that meeting, and it just ends up being a huge quagmire. Effective meetings require work to run, and someone needs to do it.
- fsckboy 2y agoof that group of people who don't do the actual work to run the meeting, are an especially slippery group of people who don't intend to do any of the work that results from the meeting either; you can often identify them because the best of their breed will volunteer to handle communications with the bosses.