Developer under influence
summary
Claims that influence comes from disciplined reasoning, repeated experience and social pairing, not charisma; interviews of developers with 15–25 years experience show they become "usually right" by logging patterns and refusing to voice ideas without facts → analysis → outcome. Practical tactics include building quick prototypes to prove an approach (do a safe experiment, then scale if it works), training juniors to contradict twice daily, using personal projects to learn, seeking informal access to decision makers and always start with the conclusion in short meetings.
AI-written summary · about
chapters (14)
- 0:00Start
- 3:22Being influent
- 7:02Logical reasoning
- 7:50Can't find one?
- 15:55Rules for Healthy Debate
- 25:58Train yourself at being wrong
- 27:23When positions are blocked
- 28:45Work your self awareness
- 31:04Tips: get a sidekick
- 39:39Never go underground Get the others in your refesion, even by symbol
- 42:13I want to change everything
- 43:10What's my position ?
- 44:28Self Help: detect inner cynical spiral
- 44:52Self help: Auto-therapy
related talks
50mThe Effective Developer - Work Smarter, Not Harder
10mA great developer - how to be one, how to find one?
31mThe Effective Developer - Work Smarter, Not Harder
51mYour worth as a developer: not what you do, but why
15mThe Power of Persistence in Your Development Career
33mWhat it takes to become a great developer!
49mKeynote: Debug your thinking
52mThe Developer Rhapsody