Minimum Viable Professional
summary
Argues that professionalism means consistently achieving good results and shows how to get there: take responsibility to explain what you care about, always agree on the problem before proposing solutions, own your learning and career instead of expecting paid training, and be dependable (no unhelpful complaining). Practical tactics include using short feedback loops to make decisions cheap, measuring impact with DORA-style metrics (lead time, deployment frequency) when negotiating value, and becoming a multiplier who raises others’ performance.
AI-written summary · about
chapters (21)
- 0:00Introduction to talk
- 1:10Professionalism in life vs tech
- 3:38Soft skills in software engineering
- 7:31Industry mindset on professionalism
- 10:25How it's done vs just getting it done
- 12:58Being a team multiplier
- 15:27Personal learning as professionalism
- 18:17Why industry lacks professionalism
- 23:57Mediocre vs excellent professionals
- 27:53Choosing the right job
- 30:25Regulating software engineering
- 34:02CEOs and professionalism
- 37:13Communicating value to leadership
- 41:08Key traits of a professional
- 42:15Never complain as a professional
- 44:21Being dependable and open
- 46:55Learning to say yes responsibly
- 49:48Well-being and professionalism
- 52:14Making cheap decisions
- 55:06Negotiating salary with impact
- 1:00:00Summary and closing
related talks
48mBeing fully you - to the workplace and beyond
49mCreating a Culture of Accountability, Diversity and Inclusion
49mExtreme Professionalism - Software Craftsmanship.
53mMVP, Innovation, Customer Centricity, Disruption, Agility...
05mHow to Succeed for Outsiders and Newbs
57mHow to be a problem solver?
34mYou're a problem solver
25mValues in Tech - Just a Buzzword or an Action-Item?