У нас вы можете посмотреть бесплатно Why Do I Code Only 10 Hours Per Week или скачать в максимальном доступном качестве, видео которое было загружено на ютуб. Для загрузки выберите вариант из формы ниже:
Если кнопки скачивания не
загрузились
НАЖМИТЕ ЗДЕСЬ или обновите страницу
Если возникают проблемы со скачиванием видео, пожалуйста напишите в поддержку по адресу внизу
страницы.
Спасибо за использование сервиса ClipSaver.ru
Why do I code only 10 hours per week — even while building software and learning full-stack development? In this video, I share the reasoning behind a constraint that initially felt counter-intuitive, especially in a culture that glorifies 60–100h workweeks, “grind,” and accelerated learning. I didn’t study Computer Science. I came into programming late, after years in a different profession, with real life constraints, limited time, and no interest in burnout as a strategy. This video is not about productivity hacks, discipline, or becoming a 10x developer. It’s about: why more hours didn’t help me learn faster how repetition beat volume why “right knowledge at the right time” mattered more than effort and how limiting my coding time became a sanity check, not a limitation I’m documenting what learning looks like for me — honestly, imperfectly, and in progress. If you’re learning to code later in life, juggling work, health, or uncertainty — this might resonate. No hustle. No grind culture. Just real life, observed carefully.