When You Think There Is No Time For Learning Or Coding
summary
Claims that carving tiny, consistent slots beats “no time”: one hour a day via 100 days of code and 50-day challenges like daily CSS images produces concrete artifacts — CSS illustrations, small JS games (tic‑tac‑toe, Simon Says) — and a real client project from d3.js freelancing job. Uses Git/GitHub, YouTube for visibility, Pomodoro and Pareto for scheduling, and habit rules (make it obvious, make it easy). Gives numbers, tools, what was built and that it worked.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 1:55Why learning matters
- 3:39From engineering to coding
- 8:01Challenges shaped skills
- 13:49Habits and time hacking
- 22:22Priorities and time
- 27:18Uncommon productivity tips
- 29:03Community and accountability
- 30:27Frustration stress burnout
- 35:48Q&A
related talks
33mWhen you think there is not time for learning or coding
38mWhen you think there is no time for learning
42mWhen you think there is no time for learning or coding
08mWhen You Think There Is No Time for Learning or Coding
28mSelf learning is a marathon not a sprint
18mProgramming Workout
36mSharpening The Axe: Self-Teaching For Developers
27mStop overthinking and go create things