Programming Workout
summary
Argument that practice beats tools: a structured regimen of tiny daily drills, measured goals and peer accountability. Examples are concrete: use vim golf and Ruby Quiz for repetitions, train touch‑typing to raise words‑per‑minute, run code katas to expose editor or design gaps. Habits form in about 65 days on average, a “three tiny habits” hack speeds that up, and a community site programmingworkout.com (≈500 interested) collects exercises and progress so practice is repeatable and trackable.
AI-written summary · about
chapters (5)
related talks
11mProgramming Like An Athlete
10mExplains 5 Steps to Get Better at Coding
41mWhen You Think There Is No Time For Learning Or Coding
01h 00mBuilding better developers
36mSharpening The Axe: Self-Teaching For Developers
28mSelf learning is a marathon not a sprint
33mWhen you think there is not time for learning or coding
31mThe Mediocre Programmer
