Refactoring Ourselves
summary
Refactoring ourselves stitches five stories pulled live from Twitter as input into concrete claims: software jobs barely change over 50–70 years, Electron proliferates at the cost of UX, teams ship multiple times a day with Docker/CI, C++/POSIX resurfaces, and ageism is real — one developer reports losing offers at 45. Cited evidence includes a 66% MacBook keyboard failure poll and three drivers killed delivering app food in Buenos Aires in one week.
AI-written summary · about
chapters (11)
- 0:00Introduction and welcome
- 1:08World in chaos and complexity
- 6:30Code and development struggles
- 10:52Tools and frameworks debate
- 15:31Ageism and career challenges
- 17:57Work environment and management
- 21:33Recruiting industry critique
- 23:42Unionization and fair labor
- 27:55Industry catastrophes and ethics
- 35:38Our power and responsibility
- 42:06Call to action and conclusion
related talks
36mScaling the Software Artisan
01h 01mFixing the Ultimate Legacy System: You
18m“47 Years Old: They Still Haven't Noticed …”
43mGood or bad - a key skill for developers
35mWhat I learned my first year as a full-time programmer
37mStaying passionate about your craft
22mDo We Need Software Craftsmen?
36mChange without changing: Keep your project healthy by refactoring your code