Solo dev productivity lessons

The video "Everything I Know as a Solo Indie Game Developer! *Sort of" is hosted on the zagawee channel (handle @ZachIsAGardner), which lists about 13.2K subscribers in its channel metadata. (youtube.com) The creator links the project SUPER DEBT and crowdfunding/support pages in the video description — the page references a Kickstarter for SUPER DEBT and a Patreon for the channel. (youtube.com) The clip distills three repeatable solo‑dev habits — batching similar tasks, documenting repeatable steps, and strict time‑blocking — and those themes recur across the channel’s devlogs and longer reflections on solo development. (youtube.com) The creator frames "context switching" as the primary productivity enemy in the video, a claim that aligns with industry estimates that each context switch can cost developers roughly 15–25 minutes of recovery time. (youtube.com) Those three tactics—batching, documenting, and blocking—map directly onto advice veterans give solo IT leads: a Spiceworks thread for solo IT leaders explicitly recommends blocking time for critical tasks and standardizing systems to limit reactive switching. (community.spiceworks.com) (community.spiceworks.com) Sysadmin guidance further elevates documentation as a practical "focus tool" that reduces cognitive load during maintenance windows, reinforcing the video’s recommendation to formalize repeatable steps before touch‑time. (focuskeeper.co blog) (focuskeeper.co) The channel’s adjacent videos — including a devlog series and a segment on generative AI for indie devs — suggest the creator is iterating on workflow tools and automation that solo operators might adopt to reduce ongoing maintenance overhead. (youtube.com)