Advertisement
Guest User

Untitled

a guest
Apr 26th, 2015
211
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 0.92 KB | None | 0 0
  1. = Programming =
  2. Does the codebase look like it was written by a single person
  3. Leads need to code 30% of the time, 1.5 days week! (respect is the currency of the realm)
  4. consistency over cleverness
  5. How long does the build stay broken?
  6.  
  7. = Team Questions =
  8. Do people avoid conflict?
  9. Do people offer new ideas? (do people feel they can fail?)
  10. Do people flag when they need help? (reinforcing cycle: "i'm almost done, i don't need help")
  11. Do people feel okay to admit being wrong?
  12.  
  13. = On Teams =
  14. Trust developers
  15.  
  16. Expire processes as you get larger
  17. Invest in tooling
  18. Think about who knows who
  19. Having developers do the recruiting (have the recruiters stalk linked in an hour a week)
  20. Do unscalable things like: create a power point that shows exactly what every does
  21. Give a roadmap for individual team members
  22. Try to touch everyone on the team
  23. Do the unscalable
  24.  
  25. Show up with problem and how to measure...do not tell how to do (ymmv based on talent)
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement