Maintaining Sanity and Code
summary
Compares a fallen scientific assumption to everyday tech debt and gives concrete fixes: use a hand‑rolled Python linter plus clang-format to auto-fix style, require header docs (Spotify UI had 25% comments), track work in Trello/GitHub and chat in Slack/HipChat, prefer flat APIs and protocols to reduce touch points, and black-box a black‑boxed UI framework that runs atop common networking so each layer is testable. Built a live prototyping tool for designers that lets them tweak UI on-device and it speeds iteration.
AI-written summary · about
chapters (39)
- 0:00Introduction
- 0:44Things not going to be part of todays presentation
- 1:23Science
- 1:37Ether
- 2:21Luminiferous
- 2:53Newton
- 3:18Romans
- 3:31Michelson Morley
- 4:23Physics and Science
- 4:39Physics
- 5:28Culture of people
- 5:39Your constraints evolve
- 5:49Newton and women
- 6:11Developer
- 7:30Code Standards
- 8:50Header Documentation
- 9:05Comments
- 9:31Request for opinion
- 10:06Show your tasks
- 10:22Have clear understanding
- 10:46Relationship between designers and engineers
- 11:35Bring the designer on board
- 12:24Culture of craft
- 12:55Australia
- 13:26Contact Sport
- 13:47API
- 13:59Image
- 14:10Dead Image
- 14:36Minimize Contact Points
- 14:58API Documentation
- 15:51Black Boxing
- 16:44Broken Windows
- 17:58Lack of deriv
- 18:15You dont know where to start
- 19:03Ask questions
- 19:26Open Source
- 20:36We should strive and aspire
- 21:14Thank you
- 21:35How to grow a team
related talks
50mThe Effective Developer - Work Smarter, Not Harder
01h 01mFixing the Ultimate Legacy System: You
01h 03mHow To Do Kick-Ass Software Development
46mCode is not important... or is it?
37mPersonal Developer Productivity Tips It's the small things
48mThe Effective Software Architect - Work Smarter, not Harder
01h 12mKeynote: "Am I A Good Programmer?"
44mHow do you think when you're coding?