Weekend Warriors: How your side project can change the tech world
summary
A concrete example: a weekend project becomes a working Telegram bot that solves a messy employee shift matrix and is still in a public repo with issues and feedback; the project starts from a personal need, uses learned Java and iterative rewrites, collects pull requests, and reduces a manual 30–60 minute task to a few seconds. Advice: start tiny, commit small features, track issues as validation, and treat criticism as growth.
AI-written summary · about
chapters (10)
- 0:00Side projects impact
- 1:03Starting from problems
- 2:31First project motivation
- 3:55Side projects as learning
- 5:20Start small
- 6:24Focus and distractions
- 7:50Feedback and criticism
- 9:57First step imperfection
- 11:43Progress and confidence
- 12:26Final encouragement
related talks
32mOpen Source: When Nights & Weekends Are Not Enough
20mOpen up to Open Source
23mTake the Leap into Open Source Projects
49mCommunities Over Code: How to Build a Successful Project
52mCrafting Your Career, the Open Source Way
47mThe Great Adventure of Open Source Contribution
17mScaling Community, Code, Contributors
38mA beautiful arrangement: Gaining experience & giving back through open source docs