What I Learned my First Year as a Full-time Programmer
summary
Harvard Business Review data show “superstar” coders hurt teams and converting them to average improves performance; an intern’s integration research actually speeds implementation; a device lab and virtual machines catch older-browser and mobile issues; color‑blindness checks find inaccessible palettes before release; failing to accept a hyphen in names causes real-world airline check‑in fees; keeping a learning journal directly leads to a promotion. These are concrete claims, tools used, and outcomes that decide whether to watch.
AI-written summary · about
chapters (40)
- 0:00Intro
- 0:27How did you get into programming
- 1:05What is this talk about
- 1:26Where Im from
- 1:38Early Career Programmer
- 2:04Who knows more
- 2:39Youre very basic
- 3:07Reframe things
- 4:02Programmer Culture
- 4:23Superstar Workers
- 6:42Harvard Business Review
- 7:07No one is an island
- 7:22We cant do everything ourselves
- 7:47Learning from others
- 8:17Questions to think about
- 9:04Playing catchup
- 9:25Doing some research
- 11:18We are not our users
- 11:46Exercise
- 12:01Frustration
- 13:56Examples
- 14:16Facial Recognition
- 14:56User Testing
- 19:06Accessibility
- 19:21Rubber Ducking
- 19:55Clearing Our Heads
- 22:50No Programmer is an Island
- 23:14How do we ask for help
- 23:55What have you already tried
- 25:49Learning new things
- 26:24Keeping a journal
- 28:39Fitting in
- 30:09Office style
- 30:52You still have things to offer
- 31:08Office culture
- 34:39Make it easy to say yes
- 35:23Explore other options
- 35:39Its not worth it
- 35:57Remote work
- 36:44Dont be pigeonholed
related talks
35mWhat I learned my first year as a full-time programmer
30mLessons Learned: A Developer's Perspective on Teaching & Learning
54mCareer Advice for Programmers
18mRemember the pain...
42mHumans are Hard, Code is Easy
40mThe Best Programmer I Know
22mIt Takes a Village to Make a Programmer
43mYou Belong In A Room Full of Wizards