Steve Jobs · Principle of Excellence
"A small team of A-players can run circles around a giant team of B and C players."
— Steve Jobs

Become an
A-Player

A complete guide for software engineers

The Fundamental Shift

The Mindset
Difference

✕   B / C PLAYER

—Waits for tasks to be assigned
—Asks "is this good enough?"
—Fixes bugs, ships features
—Works within the system
—Learns when required
—Avoids hard, ambiguous problems
—Measures hours worked

✓   A PLAYER

→Seeks problems worth solving
→Asks "what would great look like?"
→Multiplies teammates' output
→Changes the system when it's wrong
→Learns relentlessly, unprompted
→Runs toward ambiguity & hard problems
→Measures impact delivered

The Five Pillars

What A-Players
Master

01
Deep Technical Mastery
Go one level deeper than everyone else
▶

A-players don't just use tools — they understand them. They know how their language runtime works, how the OS schedules threads, how TCP handshakes flow. This depth lets them debug anything, optimize intuitively, and design robust systems.

📚 Books
Computer Systems: CSAPP Designing Data-Intensive Apps The Pragmatic Programmer Clean Code – Robert Martin Structure & Interpretation (SICP)
🎓 Courses & Practice
MIT 6.004 Computation Structures Stanford CS143 Compilers Build a DB from scratch Implement an HTTP server Contribute to open source
02
Systems Thinking
Design for scale, failure, and change
▶

A-players see beyond the ticket. They ask "what breaks at 100x load?", "what's the blast radius of this change?", "is this the right abstraction in 2 years?". They think in systems, not features.

📚 Books
Thinking in Systems – Meadows A Philosophy of Software Design Site Reliability Engineering (SRE) System Design Interview – Alex Xu
🛠 Practice
Draw system diagrams weekly Read post-mortems (AWS, GitHub) Design systems whiteboard daily Grokking System Design
03
Communication & Leverage
Multiply others — write, teach, lead
▶

The highest-leverage skill most engineers ignore. A-players write docs that save 100 hours, give code reviews that level up teammates, and explain complex ideas simply. Communication IS engineering at senior levels.

📚 Books
On Writing Well – Zinsser The Staff Engineer's Path An Elegant Puzzle – Will Larson
🛠 Habits
Write a tech blog monthly Give deep, kind code reviews Write design docs before coding Present at team meetings
04
Ownership & Bias to Action
Ship it. Fix it. Own it completely
▶

A-players treat every project as if they founded the company. When something is broken, they fix it even if it's "not their job." They ship fast, learn from production, and never hide from hard conversations.

📚 Books
The Lean Startup Extreme Ownership – Willink High Output Management – Grove
🛠 Practice
Ship something every week Run your own on-call rotation Write weekly progress updates Never say "that's not my problem"
05
Relentless Learning Loop
Compound growth, every single day
▶

A-players run a tight feedback loop: build → observe → reflect → adjust → repeat. They learn from failure without shame, seek brutal feedback, and get 1% better every day. In 3 years, that's 10× growth.

📚 Books
Ultralearning – Scott Young Deep Work – Cal Newport Atomic Habits – James Clear Mindset – Carol Dweck
🛠 Habits
Weekly retrospective (solo) Ask for feedback proactively Read 30 min/day (tech + non-tech) Spaced repetition (Anki)

Daily Operating System

A-Player
Daily Habits

MORNING
06:00
Deep Work Block (90 min)
Hardest problem first. No Slack, no email. Phone in another room. Use Pomodoro if needed. This is sacred time for your best thinking.
07:30
Read & Learn (30 min)
Technical reading: papers, docs, books. Alternate with business/psychology books. Build mental models outside your domain.
WORK
09:00
Write Before You Code
For anything >2 hours: write the design doc first. Clarify the problem, constraints, and tradeoffs. This habit 10× your design quality.
NOON
Teach Someone Something
Code review, pair programming, or a Slack thread explaining a concept. Teaching forces clarity and multiplies team value.
EVENING
18:00
Side Project / OSS (45 min)
Build something for yourself. Contribute a PR. This is where skills compound fastest — no meetings, pure craft.
NIGHT
21:00
Weekly Retro (Fridays)
Answer 3 questions: What did I ship? What did I learn? What will I do differently? Write it down. Review monthly.

The Journey

12-Month
Roadmap

M1–3
Foundation
Audit & Rebuild Your Core
  • Read CSAPP + Pragmatic Programmer
  • Pick 1 language & go deep
  • Start writing daily (docs, blog)
  • Ship 1 side project
  • Build deep work habit
M4–6
Expand
Systems & Communication
  • Design 10 systems (whiteboard)
  • Give 50+ code reviews
  • Read DDIA cover-to-cover
  • Write 3 design docs at work
  • Present at a meetup
M7–9
Lead
Ownership & Impact
  • Own an entire feature end-to-end
  • Read High Output Management
  • Mentor a junior engineer
  • Run a project kickoff
  • Fix a company-wide pain point
M10–12
Multiply
Compound & Accelerate
  • Write engineering blog series
  • Contribute to OSS project
  • Drive a cross-team initiative
  • Interview at top-tier companies
  • Define your next 3-year arc
BE THE
A-PLAYER

The goal isn't to be better than others. It's to be better than you were yesterday.