cphiri.devBrowse aymeric's, an independent, searchable archive of readable snapshots from followed feeds, preserved in Git with aggr.https://aggr.aymericbeaumet.com/sources/cphiri.dev/2026-10-13T22:33:33+00:00aymeric'saggrurn:aggr:item:6cd033c3ae88e0392f754d8196f40baaebbf1621Recreational Programming2026-10-13T22:33:33+00:002026-10-13T22:33:33+00:00jslakroHacker News: Front PageYou guys are getting paid? Show of hands: How many of you learned programming because it was fun? Part 1 What is Recreational Programming? Definition Programming for the joy of programming itself - not for work, not for money, not for…<p>You guys are getting paid?</p>
<h2>Show of hands:</h2>
<p>How many of you learned programming because it was fun?</p>
<h2>Part 1</h2>
<h2>What is Recreational Programming?</h2>
<h2>Definition</h2>
<p>Programming for the joy of programming itself - not for work, not for money, not for external requirements.</p>
<h2>What it looks like:</h2>
<ul>
<li>Building things because you're curious how they work</li>
<li>Exploring new languages just to see what they feel like</li>
<li>Solving problems that only exist in your head</li>
<li>Creating tools for problems you don't actually have</li>
<li>Writing code that makes you smile</li>
</ul>
<h2>What it's NOT:</h2>
<ul>
<li>Side hustles or potential startups</li>
<li>Skill building for career advancement</li>
<li>Following tutorials step-by-step</li>
<li>Grinding through coding challenges for interviews</li>
<li>Building what others expect you to build</li>
</ul>
<p><strong>The key distinction:</strong> Internal motivation vs. external pressure</p>
<h2>Why it matters:</h2>
<ul>
<li>Prevents burnout by reconnecting with intrinsic motivation</li>
<li>Develops intuition through low-stakes exploration</li>
<li>Maintains long-term passion for the craft</li>
<li>Often leads to unexpected breakthroughs and learning</li>
</ul>
<h2>Part 2</h2>
<h2>The Recreational Programming Spectrum</h2>
<h2>Style 1: The Live Explorer</h2>
<ul>
<li>Builds in public through streams or blogs</li>
<li>Shows the messy process: dead ends, bugs, restarts</li>
<li>Community becomes accountability and energy source</li>
<li>Projects range from practical tools to pure experiments</li>
</ul>
<h2>Style 2: The Deep Diver</h2>
<ul>
<li>Obsesses over understanding how things really work</li>
<li>Builds toy versions of complex systems</li>
<li>Values learning over shipping</li>
<li>Often has multiple "educational" implementations</li>
</ul>
<h2>Style 3: The Creative Technologist</h2>
<ul>
<li>Uses code as artistic medium</li>
<li>Generative art, music synthesis, interactive installations</li>
<li>Technology serves creative vision</li>
<li>Often blends programming with other disciplines</li>
</ul>
<h2>Style 4: The Problem Solver</h2>
<ul>
<li>Scratches personal itches with code</li>
<li>Tools that solve tiny annoying problems</li>
<li>"Good enough" solutions that work for them</li>
<li>Often accidentally builds useful things</li>
</ul>
<h2>Style 5: The Language Explorer</h2>
<ul>
<li>Constantly trying new languages and paradigms</li>
<li>Implements same concepts across different languages</li>
<li>Drawn to unusual or experimental languages</li>
<li>Code as intellectual curiosity</li>
</ul>
<h2>Part 3</h2>
<h2>Common Patterns Across All Styles</h2>
<h2>Permission to Build "Useless" Things</h2>
<ul>
<li>No business case required</li>
<li>Curiosity is sufficient justification</li>
<li>Failed experiments still teach valuable lessons</li>
</ul>
<p><strong>Key insight:</strong> ROI doesn't apply to recreational programming</p>
<h2>Follow Energy, Not Plans</h2>
<ul>
<li>Switch projects when excitement fades</li>
<li>Multiple abandoned repos are exploration, not failure</li>
<li>Boredom is data about what interests you</li>
</ul>
<p><strong>Key insight:</strong> Boredom is data, not defeat</p>
<h2>Document the Journey</h2>
<ul>
<li>Share process, not just results</li>
<li>Teaching forces deeper understanding</li>
<li>Creates connection with others on similar paths</li>
</ul>
<p><strong>Key insight:</strong> Narrate your decisions</p>
<h2>Embrace the Learning Process</h2>
<ul>
<li>Beginner's mind in new domains</li>
<li>Comfortable with not knowing</li>
<li>Process over product</li>
</ul>
<p><strong>Key insight:</strong> Progress over perfection</p>
<h2>Part 4</h2>
<h2>Your Personal Programming Playground</h2>
<h2>The Environment</h2>
<ul>
<li>Dedicated "experiments" folder/repo</li>
<li>No production concerns: minimal setup, no CI/CD pressure</li>
<li>Quick project initialization scripts</li>
<li>Version control optional</li>
</ul>
<h2>Approaches You Can Try</h2>
<ul>
<li>Weekly Experiments (2-4 hours exploring one new thing)</li>
<li>Scratch-Built Challenges (Build toy versions of tools you use)</li>
<li>Itch-Scratching Projects (Solve your own annoying problems)</li>
<li>Teaching Projects (Build something while explaining it)</li>
<li>Cross-Language Challenges (Same problem, different languages)</li>
</ul>
<h2>The Mindset Shifts</h2>
<ul>
<li>"What if..." instead of "I should..."</li>
<li>Progress over perfection</li>
<li>Learning over shipping</li>
<li>Curiosity over productivity</li>
</ul>
<h2>Part 5</h2>
<h2>Real Examples in the Wild</h2>
<h2>Zikani Nyirenda - <em>The Practical Experimenter</em></h2>
<ul>
<li>Creates random but useful tools: browser automation, file organizers, Git utilities</li>
<li>Experiments across Go, Rust, Python, Vue, and React</li>
<li>"What small problem can I solve today?" approach to coding</li>
<li>Perfect example of scratching personal itches through code</li>
</ul>
<p><a target="_blank" rel="noopener noreferrer" href="https://github.com/zikani03">github.com/zikani03</a></p>
<h2>Jeremiah Chienda - <em>The Full-Stack Experimenter</em></h2>
<ul>
<li>Explores different architectural patterns and frameworks</li>
<li>Builds tools that solve real problems while learning new technologies</li>
<li>Shows how recreational programming can span the entire tech stack</li>
</ul>
<p><a target="_blank" rel="noopener noreferrer" href="https://github.com/liwoo">github.com/liwoo</a></p>
<h2>Tsoding Daily - <em>The Live Explorer</em></h2>
<ul>
<li>Streams 4+ hours daily building random projects from scratch</li>
<li>Built his own text editors, programming languages, ray tracers</li>
<li>Shows complete process including failures and debugging</li>
<li>"Let's see what happens if..." approach to everything</li>
</ul>
<h2>ThePrimeagen - <em>The High-Energy Problem Solver</em></h2>
<ul>
<li>Creates CLI tools and Neovim plugins for personal workflow optimization</li>
<li>Infectious enthusiasm for dev tools and performance</li>
<li>Reacts to and critiques other developers' code/approaches</li>
<li>Makes optimization and tooling feel like extreme sports</li>
</ul>
<h2>Casey Muratori - <em>The Systems Deep Diver</em></h2>
<ul>
<li>Handmade Hero: Building a complete game from scratch on stream</li>
<li>Explains every single line of code and system design decision</li>
<li>No libraries, understanding everything from first principles</li>
<li>Demonstrates that you can build modern software without frameworks</li>
</ul>
<h2>Ben Eater - <em>The Educational Builder</em></h2>
<ul>
<li>Builds computers on breadboards, explains every component</li>
<li>Creates video series on how CPUs, memory, and networks actually work</li>
<li>Takes months to build what you could buy for $5</li>
<li>Makes hardware fundamentals accessible and fascinating</li>
</ul>
<h2>Dan Luu - <em>The Deep Technical Investigator</em></h2>
<ul>
<li>Writes detailed blog posts investigating performance mysteries</li>
<li>Benchmarks everything: keyboards, terminals, programming languages</li>
<li>Turns curiosity about "why is X slow?" into multi-thousand word research</li>
<li>Demonstrates how recreational investigation can uncover industry-wide issues</li>
</ul>
<p><strong>Each represents a different path back to programming joy</strong></p>
<h2>Closing Challenge</h2>
<p>Pick one experiment:</p>
<ol>
<li>Build the worst possible version of a tool you use daily</li>
<li>Spend 2 hours with a language you've been curious about</li>
<li>Document yourself solving a small problem</li>
<li>Fork an interesting project and mess with it</li>
<li>Try live coding or streaming your process</li>
</ol>
<p><strong>The only rule:</strong> Stop if it stops being fun.</p>
<h2>Final Thought</h2>
<p>"The goal isn't to become any of these programmers. It's to remember why you started coding and keep that curiosity alive alongside your career."</p>