If someone has to think of something that remind them of you what will it be?
Why Showing Your Work Matters in Programming As developers, we often focus on perfecting our code in isolation, waiting for the day it’s “good enough” to share. But in today’s collaborative world, your growth, opportunities, and reputation can flourish when you let others in on your journey. Show Your Work! by Austin Kleon offers powerful insights that resonate deeply with programmers: sharing your process, challenges, and successes can not only improve your skills but also build a supportive network within the dev community. Here’s how you can tailor the book’s lessons to amplify your impact as a programmer. The 10 Rules for Programmers to Show Their Work 1. You Don’t Have to Be a Genius – Just Be a Contributor Forget trying to be the smartest person in the room. Instead, share what you’re learning as you go. Whether it’s a bug fix, a small script, or a feature update, your contributions matter to someone out there. 2. Think Process, Not Product Codebases evolve, and so should your sharing. Don’t wait until you’ve completed the “perfect” app or tool. Instead, show how you’re iterating and the thought process behind your decisions. > Example: Share your GitHub repository early, document your progress, and explain your challenges in the README. 3. Ship Small Wins Every Day Consistency beats perfection. Push daily commits, tweet about an interesting code snippet, or write LinkedIn posts about lessons learned. 4. Share Your Tools and Inspirations Openly share the libraries, frameworks, and resources that inspire your work. Other developers will appreciate your transparency. 5. Tell the Story Behind Your Code Every app, feature, or line of code has a story. Share why you built it, the problem it solves, and how you approached it. 6. Teach What You Learn Teaching is one of the best ways to solidify your knowledge and connect with others. Share tutorials, snippets, or explainers. > Example: Write a Medium post or do a video explaining the difference between server-side rendering (SSR) and static site generation (SSG) in Next.js.