It's Dangerous To Go Alone Lesson From The Tech Wilderness
summary
Seven concrete career rules with anecdotes and a real outage: adapt to change by swapping tools as needed, share early and often to catch feedback (example: a quarterly Ionic webinar broke when a YouTube link changed and the retro fixed the process, not a person), run user research so projects aren’t just cool ideas, treat mentorship as temporary lifting not permanent crutch, learn from failures (failed classes led to oceanography), say no to overload, and prioritize psychological safety and growth so work actually helps real users.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:49Adapt to change
- 3:37Share ideas early
- 5:24Embrace failure
- 7:11Build for users
- 8:58Work impacts people
- 10:05Mentorship and solo work
- 11:55Learn to say no
- 12:58Cut yourself slack
- 13:42Prioritize safety growth
related talks
13mYou know nothing, tech lead
28mLessons learned after more than 20 years working in IT
26mAll the things I learnt as a junior developer (so you don't have to)
18mRemember the pain...
37mWhat I wish I knew when I was a junior developer that I would tell as a staff software engineer
01h 01mLessons from a lifetime of doing, teaching, managing, and leading technical development
08mWhat Stan Lee taught me about working in tech
51mTeaching and managing for technologists