What I learned my first year as a full-time programmer
summary
Claims that “superstar” coders cost companies citing a Harvard Business Review study and a concrete stat: 80,000 projected unfilled U.S. tech jobs through 2022. Practical fixes include building READMEs and a device lab that catch real bugs, changing company swag to fitted tees, and using Rails helpers like squish, pluralize, previous_changes, find_or_create_by. Ten Forward reports a team composition shift (about 70% women, ~30% people of color) and shows documenting wins and asking for targeted help actually improves hiring, retention, and product quality.
AI-written summary · about
chapters (16)
- 0:00Start
- 1:12Programmers Are Not the Most Important People in Tech
- 3:48Slow and Steady this Is Not a Race
- 6:44Documentation
- 11:30Diverse Staff
- 11:43Cross-Cultural Checklist
- 13:11Accessibility Testing
- 15:03Reframing Our Feelings
- 16:58Switching to Paper
- 19:44How Can I Help You
- 20:31Track and Celebrate Your Growth
- 21:43Document Your Success
- 25:29Your Voice Matters
- 27:40Company Swag
- 29:24Ask for Help
- 31:29Working Remotely
related talks
38mWhat I Learned my First Year as a Full-time Programmer
46mKeynote: What Happens to Everyone, When Everyone Learns to Code?
30mLessons Learned: A Developer's Perspective on Teaching & Learning
23mHow to hire the best for your startup
22mJunior Gems: Hiring, Valuing, and Empowering the Next Wave of Ruby Developers
22mIt Takes a Village to Make a Programmer
54mCareer Advice for Programmers
41mBooting Up: Hiring and Growing Boot Camp Graduates