2. About The Dungeon Master
• Brett Whittington
• Ranger
• Chaotic Good
• @BrettTheWhitt
3. This Quest
• Definition of a Team
• How to build a real team
• Effective questing with a team
• The types of people you may encounter on your adventure.
4. Definition of a Team
A team comprises a group of people or other animals linked in a
common purpose. Human teams are especially appropriate for
conducting tasks that are high in complexity and have many
interdependent subtasks.
5. Definition of a Team
• The purpose of a team is to get together in a basement with a
bunch of other nerds to eat pizza, get experience, and get
treasure.
6. Definition of a Team
• In software, the purpose of the team is to get together in a
basement, drink coffee, get experience, and get treasure.
9. Building a true team
HRT is pronounced as Heart.
• Humility
• Respect
• Trust
10. Building a true team
• Hire non-toxic people.
• Working with toxic people to change
• Let them
11. Classes - Barbarian
• Pillar Crushers
• Not the sharpest tool in the shed.
• Rages at the drop of a hat.
• Bull-headed as he is strong.
• Pillar Builders
• Loyal to a fault
• Purpose Driven
• Can carry a heavy load
13. Classes - Fighter
Slays bugs with the weapons of the trade.
• Pillar Crushers
• Laughs at lessor team members for their lack o f knowledge.
• Slays all who stand in their way.
• Pillar Builders
• Takes the brunt hordes of user requests.
• Mentor junior members of the team by teaching them the tools of the
trade.
• Able to back up other team members when they get into trouble
14. Classes - Paladin
Upholds the laws of Patterns and Practices.
• Pillar Crushers
• Dogmatic belief in patterns and practices
• Mutters rules by rote
• Expects others to do the same
• Pillar Builders
• Knows when to use the right tool for the job.
• Realizes that others have differing opinions.
15. Classes - Ranger
Jack of all trades; master of of none. Great at scouting out
problems before they occur.
• Pillar Crushers
• Unintentionally or purposely leads team members down rabbit holes.
• Gives less experienced team member all the answers.
• Pillar Builders
• Able to see potentional issues before they occur.
• Not scared to tackle new problems
16. Classes - Rogue
Problem solver; able to look at a complicated and disarm it so the
team doesn’t have too
• Pillar Crushers
• Back stabber -Quick to blame others for failings of the team.
• Steals credit
• HRT
• Excellent problem solver
• Able to build complex code with little difficulty.
17. Classes - Wizard
Masters of arcane and obscure knowledge
• Pillar Crushers
• Choose to keep their knowledge to themselves.
• Unwilling to learn new things
• Pillar Builders
• Domain knowledge is second to none.
• Can wave their wand and fix extremely difficult problems with ease.
• The google of the company.
19. Credits
Wizards of the Coast – D&D Theme
Background Image - Wenjun Mao
Team Geek - Brian W. Fitzpatrick, Ben Collins-Sussman /
O’Reilly Media
Conan – Universal Pictures
Hobbit – New Line Cinema, MGM
Editor's Notes
Brian W. Fitzpatrick, Ben Collins-Sussman
Talk why teams are important and about your team project in school
Talk about why assigned groups are bad but also talk about how they are actually pretty relevant.
Company Culture
If you know any former employees they can describe the environment.
Review the website to see what benefits the company provides.
Find some employees on social networks and invite them to lunch.
People who are in a team generally work together based on the 3 pillars of Humility, Respect, and Trust as described in Team Geek. I can also be pronounced as HURT because if you violate any of the three pillars. It can compromise yourself and your team.
Party members might work together but have no problem turning on each other when it suits their mood or the situation changes. Situation: Fully Unit Tested, Code Reviewed Code gets deployed to production. A couple of days later it fails? What is the sequence of events for a team? For a party? What happens when the bug is found?
A team will take responsibility for what happened as a whole and not blame the individual who caused the bug. The party will instantly turn on the individual and will leave them out in the wild.
Can you believe this film is 33 years old and it won the leading actress a golden globe?
Has a pillar crusher
Don’t have answers don’t pretend, defensive, opinionated
Stand ups are good
Stretch them but don’t break them
Are a pillar crusher
Constructive criticism, don’t be afraid to ask for help.
Is a Pillar builder
Monotonous tasks
A do’er
Great at doing maintenance/support.
A lot of junior people tend to fall into this class
Story about guy who spends most of Monday morning talking about the weekend.
Has a pillar crusher
Keep watch but don’t hover.
Have facts
Keep busy
Are a pillar crusher
Be mindful of other people’s time
Don’t lie to save face
Ask for more work.
Is a Pillar builder
Support your team mates
Gives direction
Usually a project manager.
Has a pillar crusher
Are a pillar crusher
Is a Pillar builder
Has a pillar crusher
Are a pillar crusher
Is a Pillar builder
A lot of senior developers fall into this.
Has a pillar crusher
Are a pillar crusher
Is a Pillar builder
Has a pillar crusher
Are a pillar crusher
Is a Pillar builder
I've had a long career as a Senior Software Engineer. I've got a few years to go till retirement, and I just wanted to request advice on how to deal with new grads. A lot of kids these days have no respect, and often will correct without professional courtesy. I also have a strong reputation at this company, and I've built up a large infrastructure that I have control over. These new kids, though often with better ideas, would undo what I've done, and possibly risk the hard work that justifies my position.
