Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- = Programming =
- Does the codebase look like it was written by a single person
- Leads need to code 30% of the time, 1.5 days week! (respect is the currency of the realm)
- consistency over cleverness
- How long does the build stay broken?
- = Team Questions =
- Do people avoid conflict?
- Do people offer new ideas? (do people feel they can fail?)
- Do people flag when they need help? (reinforcing cycle: "i'm almost done, i don't need help")
- Do people feel okay to admit being wrong?
- = On Teams =
- Trust developers
- Expire processes as you get larger
- Invest in tooling
- Think about who knows who
- Having developers do the recruiting (have the recruiters stalk linked in an hour a week)
- Do unscalable things like: create a power point that shows exactly what every does
- Give a roadmap for individual team members
- Try to touch everyone on the team
- Do the unscalable
- 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