Actionable Tactics for Leveling Up Devs
We are told that junior developers are a secret weapon, but this alleged ‘competitive advantage’ is so elusive! Typical advice about evolving talent can be broad, un-relatable, and impractical. Aren’t there any specific and actionable tactics that teams can employ for leveling up new devs? (Yes, there are!)
April 19, 2018
| Making others better mentors |
Making code easier to change |
Making ignorance & vulnberability safer |
Tooling | Business Knowledge |
Retention | Promotion | |
|---|---|---|---|---|---|---|---|
| Questioning format | X | ||||||
| No private messages! | X | X | |||||
| Stupid questions | X | ||||||
| Remove or document prolific abstractions. | X | X | |||||
| Domain-level documentation | X | X | |||||
| Screencasts as documentation | X | X | X | X | |||
| Watch other devs work | X | X | |||||
| Affirm the hire. | X | ||||||
| Support time-wasting. | X | ||||||
| Better use of investment time | X | ||||||
| Long-form technical writing | X | ||||||
| Let devs “audit” extra meetings | X |