How to be a Happy Developer. Now!
summary
Practical tactics appear: check expectation vs reality by listing what work actually asks vs what was wanted; spend Friday slack time to learn or prototype; take a half day to try new tech even near release and measure whether it saves time; translate tech work into business numbers; observe users (paging vs scroll) with about 10–20 real users to avoid dumb assumptions; treat a 1960s/70s legacy system like a maintained cathedral (about 60 staff) and decide whether to refactor or sustain.
AI-written summary · about
chapters (21)
- 0:00Intro
- 0:30Status quo
- 1:15So what?
- 2:06Expectations vs. reality
- 4:06What are you actually looking for?
- 5:16Hobby vs. profession
- 6:47Know and understand
- 10:21Tailor your communication
- 12:33Introvert or extrovert?
- 13:49Don't lose your focus
- 16:01Legacy support vs. the latest fancy stuff
- 19:21Unknown heroes
- 23:11Career management
- 26:24Mentorship
- 28:57Pride and fear
- 30:29Workaholics
- 33:07Slack time
- 34:36Pressure
- 36:15Don't make all problems your problems
- 36:52Change is the only constant
- 38:48Being happy is a choice!
related talks
31mThe Effective Developer - Work Smarter, Not Harder
17mMake Work Not Suck Improving the Developer Experience
31mThings I Wish I Knew When I Started Playing 'Developer'
29mBuilding What Developers Actually Want: Lessons Learned
27mWhat Makes a Great Developer Experience?
41mPrinciples of developer experience
35mBuilding Effective Developer Experience
53mOn Being an Effective Developer