Communication is a Technical Skill
summary
Argues that communication is a technical skill with concrete results: a workshop model that moves local meetup attendance from 2% to 18% in six months; a developer-experience focus on the first 15 minutes that shapes docs, repos and hackathon wins; the Rack idea defined as a call method returning a three-element array that scales by gradual adoption; examples include a real-time Firebase hack that worked and a 33‑commit repo launched in days.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:53Why Day
- 4:38Sharing
- 7:03Software
- 10:36Rails Bridge
- 14:35Firebase
- 19:03RAC
- 23:49Conclusion
- 26:19Language Learning
- 27:44Communication in Government
related talks
23mCommunication is just as important as Code
34mCommunication Strategy for OS Projects: Get Engineers to Think About Comms Channels
25mCommunication and Convention
25mCommunication Is Important, Damn Important!
28mBuilding Culture through Communication
31mHow to Effectively Communicate Technical Ideas to Non Technical Audiences
15mGrowing at Work with Community-oriented Development
37mComms & Social Media - Why Does a Project Need It