An Engineering Culture Where You Matter

1. AN ENGINEERING CULTURE WHERE YOU MATTER @buri&ca
3. ENGINEERING CULTURE?
4. CULTURE IS NOT
5. A PING PONG TABLE
7. CULTURE IS
8. "The behavior you reward or punish" - Charles O'Reilly
9. Tuesday 10am in the #engineering channel of a startup w poor management
10. Can someone look at my pull request please? nhocki 10:03 AM
11. Can someone look at my pull request please? This should go to QA later today. nhocki 10:03 AM
12. Can someone look at my pull request please? This should go to QA later today. nhocki 10:03 AM nhocki 2:28 PM Hey team, some help ^ please?
13. Can someone look at my pull request please? This should go to QA later today. nhocki 10:03 AM nhocki 2:28 PM Hey team, some help ^ please? buri5ca 4:16 PM Anyone watch GoT last night?
14. nhocki 2:28 PM Hey team, some help ^ please? buri5ca 4:16 PM anyone watch GoT last night? sebasoga 4:17 PM dude... it was sooo goood!
15. nhocki 4:20 PM Some help please.... buri5ca 4:16 PM anyone watch GoT last night? sebasoga 4:17 PM dude... it was sooo goood!
16. nhocki 4:20 PM Some help please.... sebasoga 4:17 PM dude... it was sooo goood! guilleiguaran 4:21 PM lol 4:20
17. nhocki 4:20 PM Some help please? guilleiguaran 4:21 PM lol 4:20 philsturgeon 5:30 PM Sorry @nhocki, was checking on my cider. I rejected your PR, not RESTful enough
18. nhocki 4:20 PM guilleiguaran 4:21 PM lol 4:20 philsturgeon 5:30 PM Sorry @nhocki, was checking on my cider. I rejected your PR, not RESTful enough
19. "punish"
20. Can someone look at my pull request please? nhocki 10:03 AM
21. Can someone look at my pull request please? This should go to QA later today. nhocki 10:03 AM
22. Can someone look at my pull request please? This should go to QA later today. nhocki 10:03 AM nhocki 2:28 PM Hey team, some help ^ please?
23. Can someone look at my pull request please? This should go to QA later today. nhocki 10:03 AM nhocki 2:28 PM Hey team, some help ^ please? buri5ca 4:16 PM @channel not cool, please check nhocki's PR
24. nhocki 2:28 PM Hey team, some help ^ please? buri5ca 4:16 PM @channel not cool, please check 's PR sebasoga 4:17 PM Sorry, was busy. Added nits. I'm +1
25. nhocki 4:20 PM Checking. buri5ca 4:16 PM @channel not cool, please check 's PR sebasoga 4:17 PM Sorry, was busy. Added nits. I'm +1
26. nhocki 4:20 PM Checking sebasoga 4:17 PM Sorry, was busy. Added nits. I'm +1 guilleiguaran 4:21 PM +1 too
27. guilleiguaran 4:21 PM +1 too philsturgeon 4:30 PM Rejected, needs more REST.
28. guilleiguaran 4:21 PM +1 too philsturgeon 4:30 PM Rejected, needs more REST. buri5ca 4:36 PM @philsturgeon mind being more explicit & helping @nhocki out please?
29. philsturgeon 4:30 PM Rejected, needs more REST. buri5ca 4:36 PM @philsturgeon mind being more explicit & helping @nhocki out please? philsturgeon 4:30 PM Oh yes, my bad. @nhocki Screenhero?
30. "reward"
31. Can someone look at my pull request please? nhocki 10:03 AM Can someone look at my pull request please? This should go to QA later today.
32. Can someone look at my pull request please? This should go to QA later today. nhocki 10:03 AM sebasoga 10:17 PM Sorry, was busy. Added nits. I'm +1
33. Can someone look at my pull request please? This should go to QA later today. nhocki 10:03 AM sebasoga 10:17 PM Sorry, was busy. Added nits. I'm +1 guilleiguaran 11:21 PM +1 too
34. sebasoga 10:17 PM Sorry, was busy. Added nits. I'm +1 guilleiguaran 11:21 PM +1 too philsturgeon 11:25 PM Checked, I think we can make it more RESTful. Wanna pair @nhocki?
35. guilleiguaran 11:21 PM +1 too philsturgeon 11:25 PM Checked, I think we can make it more RESTful. Wanna pair @nhocki? buri5ca 4:16 PM to @sebasoga, @guilleiguaran & @philsturgeon for helping @nhocki get this out
36. WHY IS CULTURE IMPORTANT?
37. A HEALTHY CULTURE MAKES US AND OUR TEAMMATES HAPPY
38. IT DETERMINES HOW WE WORK
39. WHAT DOES HEALTHY CULTURE EVEN MEAN?
40. DEPENDS ON WHAT WE VALUE
41. MAYBE WE VALUE:
42. BEING ON TIME
43. BEING RESPECTFUL
44. BEING EXPLICIT
45. BEING TECHNICALLY EXCELLENT
46. SHIPPING FAST
47. USING THE LATEST TOOLS
48. HELPING OUR CUSTOMERS
49. DIFFERENT TEAMS VALUE DIFFERENT THINGS
50. CODE AS CRAFT
51. MOVE FAST AND BREAK THINGS
53. BE THE BASS ENGINEERING
54. "A SKILLED BASSIST SUPPORTS THE GROUP BY PROVIDING A GOOD-FEELING, STEADY PULSE." - Andrew Pouska
55. BE THE BASS - SUPPORTING INSTRUMENT - LOW EGO - CARRY THE RYTHYM - MAKE OTHERS SHINE
56. EASY FOR YOU TO SAY BURITICA ...
57. ... YOU'RE THE VP OF ENGINEERING
58. nhocki 4:20 PM
59. WHAT IF I TOLD YOU YOU CAN HACK THE SYSTEM
60. HOW TO INFLUENCE CULTURE WITHOUT AUTHORITY IN AN INDUSTRY WHERE POOR MANAGEMENT IS COMMON
61. DISCLAIMER: YOU MAY NOT BE $$$ FOR IMPROVING YOUR TEAM'S CULTURE
62. I'M NOT A FAN OF UNPAID LABOR BUT QUITTING A TOXIC CULTURE IS NOT ALWAYS AN OPTION
63. LATIN-AMERICAN JOB MARKETS DON'T OPERATE LIKE THOSE IN SILICON VALLEY
64. DISCLAIMER 2: BE REALISTIC ABOUT YOUR SCOPE OF INFLUENCE
65. INFLUENCE WILL WORK WITHIN YOUR "CLOSURE"
66. STEP 1 : BUILD OR EARN TRUST
67. INDIVIDUAL CONTRIBUTORS: TRUST > AUTHORITY
68. GIVE VISIBILITY INTO YOUR WORK
69. PUBLIC TASKBOARD
71. BROADCAST YOUR STATUS - INTERNAL BLOG - SHARED DOC - RECURRING NEWSLETTER - CHAT STATUS UPDATE - TODAY I MUST ... - TODAY I SHOULD ... - TODAY IT WOULD BE NICE IF
72. START DOING IT FOR YOURSELF
73. OTHERS WILL CATCH ON
74. BE ON TIME (EARLY)
75. DELIVER ON YOUR PROMISES
76. SIDENOTE: CONSTANT MANDATED DEADLINES SUCK AND ARE THE RESULT OF POOR MANAGEMENT POINT ESTIMATION CAN'T FIX POOR MANAGEMENT... DON'T BLAME YOURSELF SOURCE: I'VE BEEN A BAD MANAGER
77. OPTIMIZE YOUR "SUPPORT" TIME - SCHEDULE OFFICE HOURS - PAIRING - DEBUGGING - MENTORING - CO-STUDYING - BLOCK TIME TO UNBLOCK OTHERS - READ EMAIL - REVIEW PULL REQUESTS - WRITE DOCUMENTATION - HELP QA OR ACCEPTANCE
78. IF ALL THE ATTENTION GOES TO THE CODE YOU WRITE, NONE OF IT IS LEFT FOR THOSE WHO YOU WRITE CODE WITH
79. STEP 2 : FIND ALLIES & COMMON VALUES
80. CREATE PATTERNS AROUND COMMON INTERESTS
81. IF PEERS VALUE:
82. LEARNING / MENTORSHIP LOW EFFORT/$$/TIME: - ATTEND A MEETUP - WATCH AN ONLINE TALK TOGETHER - SHARE AN ARTICLE AND DISCUSS AT LUNCH HIGHER EFFORT || $$ || TIME: - START A STUDY GROUP - GIVE A TALK - TAKE ONLINE COURSE TOGETHER - START A SIDE PROJECT TO LEARN
83. CODE QUALITY - PAIR W SOMEONE TO ADD FIRST TEST - FIND A CODE REVIEW BUDDY - ADD LOW EFFORT/$$ QUALITY TOOLS - PAIR WITH QA/PRODUCT ON ACCEPTANCE - GIVE VISIBILITY INTO SUPPORT EFFORTS
84. COLLABORATION - SUGGEST DELEGATION COMMITMENTS - INCLUDE PEERS IN YOUR DECISIONS - PREVENT SOLO PROJECTS OR CHANGES - TRUST PEERS WITH THEIR DECISIONS
85. HELPING CUSTOMERS - GET INVOLVED IN CUSTOMER SERVICE - TAKE CUSTOMER SUPPORT ISSUES SERIOUSLY - FIX BUGS WITH LOW EFFORT HIGH IMPACT - ENCOURAGE CONSTANT USE OF YOUR PRODUCT
86. STEP 3 : GROW YOUR INFLUENCE
87. WHEN YOU HAVE SUCCESSFULLY CREATED UNOFFICIAL PROCESSES
88. FIND WAYS TO SHARE YOUR RESULTS TO A BROADER AUDIENCE
89. RECRUIT OTHERS INTO YOUR NEW FOUND AWESOMENESS
90. PROCESS IS A PRODUCT YOU CAN SHIP, MARKET & INCREASE ADOPTION OFF
91. UNDERSTAND YOUR "MARKET", "SHIP" & "ITERATE"
92. PROCESS UX WILL MATTER
93. YOUR PROCESS CAN "DISRUPT" POOR MANAGEMENT
94. THE SAME WAY THAT TINY COMPANIES DO IN EXISTING MARKETS
95. YOU CAN ONLY BUILD AN ENGINEERING CULTURE WHERE YOU MATTER...
96. Can someone look at my pull request please? This should go to QA later today. nhocki 10:03 AM sebasoga 10:17 PM Sorry, was busy. Added nits. I'm +1
97. ...BY SHOWING OTHERS THAT THEY MATTER TO YOU
98. GRACIAS ques&ons: @buri&ca