Soft Skills & Staff Topics
The non-code dimensions of the senior bar: code review as a force-multiplier, framing trade-offs in writing, mentoring and tech leadership.
Topics (canonical order)
-
What seniors look for, the difference between blocking and nit comments, async vs sync review styles
-
Writing decision docs (ADRs), framing options as comparable, the "good / fast / cheap" template
-
Mentoring patterns, "growing the next senior", influence without authority, picking battles
-
Trunk-based vs GitFlow vs GitHub flow, advanced ops (rebase, bisect, reflog, worktree), commit conventions
-
BLUF, Pyramid Principle, RFCs, status updates, escalation paths, design-review facilitation
-
Templates (Nygard, Y-Statements, MADR), supersede-don't-edit, ADRs as onboarding gold
-
TD ledger as a product artifact, Fowler quadrant, communicating debt to non-eng, sustainable budget
-
Five Whys / causal graphs / Cynefin, action item taxonomy (prevent/detect/mitigate), facilitation language
Why this section comes last
Technical depth must come first. These topics rely on having technical credibility to be useful — a code-review checklist read without first knowing what good code looks like is just bureaucracy.
Cross-references
- Code review references SOLID & Pragmatic Trade-offs.
- Trade-off framing references the system-design framework in Framework for .NET System Design.