A Day in The Life of a Developer Bo$$
summary
Starts with concrete routines: code from six in the morning until noon and reserve afternoons for meetings, plus weekly no tech days and one-day “bits and bobs” for admin. Uses GTD principles, use Things and Boomerang to triage inboxes and do <2-minute tasks immediately. Prioritizes shipping over polishing — “if you’re 100% happy you launched too late” — and watches adoption curves before investing in shiny frameworks while tracking GraphQL React ES6 and CSS Grid trends.
AI-written summary · about
chapters (25)
- 0:00Intro
- 1:28Wes Boss
- 4:12Day to Day
- 8:11Contact Switching
- 9:04Structure
- 13:33To Due Process
- 14:43Sticky Notes
- 15:16Balancing Quality and Shipping
- 16:37Getting User Feedback
- 18:00Growth Challenges
- 19:54Early Adopters
- 20:56Business Acumen
- 22:24How do you overcome that feeling
- 22:46The 50 people rule
- 27:15Communication
- 27:27Stakeholders
- 28:25Burning Questions
- 30:15Lemon Lou
- 30:41Best piece of professional advice
- 32:29Community based learning
- 32:59Twitter and social media
- 37:47Whats on your radar
- 37:58Whats next
- 39:31What have you learned from teaching
- 41:06What about people that have a day job and also do a lot of freelance work
related talks
51m"Time Management for Developers"
17mBeing a developer: What the heck am I doing?
11mSS & BR: Productivity for ordinary developers
01h 01mDeveloper Happiness and Why it Matters
01h 09mThe Well-Balanced Programmer
47mCommunication for Developers: estimates, code reviews, and other hard problems
52mFocus in a Fragmented World: A Developer’s Guide to Staying Productive
33mThe Creative Developer