Panel about lessons learned
summary
Argues that burnout requires concrete action not just rest and recommends close your laptop for at least a week or even a month to recover; suggests making work replaceable and removing Slack and notifications to stop constant interrupts; calls hourly tracking misleading and favors proof of work instead; accepts TypeScript for large codebases and flags Deno as lowering friction for TS adoption; gives practical recovery steps and tooling tradeoffs.
AI-written summary · about
chapters (5)
- 0:00Start
- 2:51Can Your Organization Work without You
- 7:05Do You Still Use Social Media during Your Breaks
- 10:19How Do You Find Time for for every Important Thing in Your Life
- 23:49Javascript and Typescript
related talks
05mBreaking Ba(l)d: How to Prevent Burnout and Thrive
37mHow to Survive the Burnout
36mPanel: Tech Community Share Out: Maintaining a Healthy Balance with Work
21mTales from the Field - How to Avoid Burnout
44mKeynote: Meditations on Software
29mFighting Burnout Incorporating Rest Into the Software Development Workflow
45m10 Things I Wish I Knew Before Experiencing Burnout
49mPanel Discussion: Care and Feeding: Burnout and Self Care in our Community