On Fri, Jul 13, 2018 at 2:02 PM Vojtech Szocs <vszocs(a)redhat.com> wrote:
Thanks for sharing!
As with everything in life, there should be some degree of balance.
Extremes are not good, and every single person is different - one might
give great results when working uninterrupted, while other might excel at
doing various things in & out of the usual-work bubble.
The key to a productive team, in my opinion, is getting to know the people
and guiding/leading them to utilize their individual strengths. You'll
likely end up with a diverse skill set & way of working for every person in
your team. Getting from zero to a very productive team takes time and
everyone getting to know each other. It's important not to try to make
every single member of your team work in the same way - instead, identify
the strengths/weaknesses and adapt accordingly.
Mm, I love that point! This is definitely something I'm trying to remember
more as I grow in my career :)
For example, when you have a Vojtech on your team and you need an amazing
API created, it's best to just put the Vojtech in a room for a week, don't
let him be interrupted, and in a week you'll have a flawless API!
When it comes to asking for help when stuck on some problem, the key
create an encouraging environment where people assist each other. If one
team member gets stuck, it hurts the team as a whole. People with lots of
knowledge and experience should share it with others and help them become
better. It's not a competition on "who's the best developer" or
"who can do
tasks in the shortest timeframe", it's about evolving your team into a
productive unit where people help each other out.
And there is no shame in saying "I'm stuck on this problem, please help
me". People eventually get better at what they do. Eventually, there's only
one difference between a beginner and a master - the master has failed more
times than the beginner has even tried.
Shame is all about not respecting cultural norms. Since our cultural norm
is to ask for help, there is definitely no shame! This took me a while to
be comfortable with, but I think it's an important concept. Thanks for
referencing the word "shame"!
On Thu, Jul 12, 2018 at 2:19 AM, Greg Sheremeta <gshereme(a)redhat.com>
> wanted to share :)
> "Software folk are very good at putting their headphones on and living in
> their own little bubbles. This reinforces the idea that software
> development is some sort of mythical or sacred practice that should never
> be interrupted, and it makes people second guess whether they should ask
> for help. This isn’t what you want in a team. You want people to be
> comfortable asking for help – that can be the difference between a
> successful & productive team who ask for help as soon as they’re stuck, and
> an unproductive team who struggle with their work in silence."
> from https://wildlyinaccurate.com/becoming-a-team-lead-a-survival-guide/
> I love helping everyone, and I know most people love to help, but my
> usual first reaction to needing help is to resist asking. After 5 years on
> the team I'm starting to get more comfortable lol :)
> GREG SHEREMETA
> SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
> Red Hat NA
> gshereme(a)redhat.com IRC: gshereme
> Devel mailing list -- devel(a)ovirt.org
> To unsubscribe send an email to devel-leave(a)ovirt.org
> Privacy Statement: https://www.ovirt.org/site/privacy-policy/
> oVirt Code of Conduct:
> List Archives:
SENIOR SOFTWARE ENGINEER - TEAM LEAD - RHV UX
Red Hat NA
gshereme(a)redhat.com IRC: gshereme