Teaching GitHub for Poets
summary
Kickstarter runs a 1 hour class that teaches the GitHub flow in browser so any staff can make copy changes, open pull requests, and rely on CI and staging to catch failures. About 110 employees have access, 29 nonengineers have merged PRs producing 1,100 commits (one person made 312). The practical wins are fewer support tickets from small copy fixes, faster deploys within minutes, and real cultural change toward transparency and shared responsibility.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 0:48What is Kickstarter
- 1:43Outline
- 2:09GitHub for Poets
- 3:46GitHub Flow Browser
- 5:47Open to all staff
- 7:43Tools and processes
- 9:36Everyone can commit code
- 10:15Lightweight process
- 12:05Avoid CMS
- 13:56Cultural Value
- 18:16Transparency
- 19:14Pull Requests
- 21:42Impact
- 23:11Getting Help for Poets
- 23:23Branches and Commits
- 25:02Always Be Learning
- 27:10Live Demo
- 31:54Common Concerns
- 35:43Pro Tips
- 35:58Poets in Git
- 36:21Continuous Integration
- 37:29thumbs up
- 38:22Kickstarter Poets
- 42:06Coding becomes more like writing
- 43:38Kickstarter homepage examples
- 44:16Hero graphic
- 44:31Dogecoins
- 44:46Library projects
- 44:58Outro
related talks
31mHow GitHub Uses GitHub to Build GitHub
32mGit yourself a leg up for student projects
45mHow GitHub builds GitHub on GitHub
17mGitHub Pull Requests for Everyone
18mThe story of GitHub1s - speed & familiarity matters
05mGetting 800 people to make a website
39mUsing Github for more than code
10mCollaboration Is Evolving