Code, Create, and Steal: Another way to Level up (A Programmer's Guide to Austin Kleon's "Steal Like an Artist")
Disclaimer: this is not about passing someone else work as your own or not giving credit to the original source
Hey Papafam! Ever felt stuck while staring at your code editor? Or wondered how the rockstar developers keep pushing innovative solutions? Austin Kleon's "Steal Like an Artist" offers a refreshing perspective on creativity that resonates deeply with us in the programming world. This isn't about copy-pasting Stack Overflow answers—it's about finding inspiration everywhere, remixing ideas, and building your unique developer identity. In our field where frameworks evolve weekly and new libraries drop daily, learning how to effectively
"steal" (read: draw inspiration and transform) is a superpower. Let's break down how this short but powerful book can transform your coding journey and help you build more authentic, creative projects.
Chapter Summaries
1. Steal Like an Artist
* NOTHING IS ORIGINAL – Every JavaScript framework, library, or that "revolutionary" app is built on previous ideas
* EMBRACE YOUR INFLUENCES – Study the GitHub repos of developers you admire; understand their design patterns and problem-solving approaches
* THE GENEALOGY OF IDEAS – Trace influential programmers back to their influences (Who inspired the creators of React or Python?)
* GOOD THEFT VS. BAD THEFT – Honor your sources, transform what you take, and contribute back to the community through PRs or blog posts
* THE REMIX PRINCIPLE – Take several existing coding patterns or libraries and combine them in ways nobody has thought of before
2. Don't Wait Until You Know Who You Are to Get Started
* IDENTITY FOLLOWS ACTION – You become a developer by writing code, not by waiting until you feel ready
* IMPOSTER SYNDROME IS UNIVERSAL – Even senior devs often feel like they're faking it
* START COPYING – Rebuild existing sites or apps to understand how they work before creating your own
* THE PARADOX OF LEARNING – First imitate others' code exactly, then gradually introduce your own modifications and style
* EVOLUTION THROUGH IMITATION – Your unique coding style will emerge naturally as you work through others' approaches
3. Write the Code You Want to See in the World
* CREATE WHAT'S MISSING – Build the tools, libraries, or apps that you wish existed for your own needs
* SOLVE YOUR OWN PROBLEMS – The best side projects address pain points you personally experience
* THE PERSONAL IS UNIVERSAL – That annoying workflow issue you faced probably bothers other developers too
* SIDE PROJECTS MATTER – Many successful libraries started as solutions to the creator's specific challenges
* CODE FOR YOURSELF FIRST – Authentic work resonates more than trying to predict what others want
4. Use Your Hands
* STEP AWAY FROM THE SCREEN – Solve complex problems with pen and paper, whiteboards, or physical diagrams
* DIGITAL VS. ANALOG THINKING – Different neural pathways activate when you sketch a system architecture vs. typing it
* EMBODIED COGNITION – Moving around physically can unlock solutions to stubborn coding problems
* THE POWER OF DIAGRAMS – Visualizing data structures and relationships often reveals insights IDE's can't show
* PHYSICAL PROTOTYPING – For UI/UX problems, paper prototypes can be faster than coding each iteration
5. Side Projects and Hobbies Are Important
* CROSS-POLLINATION OF IDEAS – Your non-programming interests can inspire unique coding solutions
* AVOIDING BURNOUT – Diverse interests keep your creative thinking fresh when facing tough technical challenges
* UNEXPECTED CONNECTIONS – That game design principle might solve your microservice architecture problem
* LEARNING TRANSFER – Skills from other domains (music, art, sports) often map to programming concepts in surprising ways
* THE DANGER OF SINGLE IDENTITY – Being "just a programmer" limits your creative potential and resilience
6. The Secret: Do Good Work and Share It With People
* BUILD IN PUBLIC – Document your learning journey through blogs, YouTube videos, or GitHub repos
* THE POWER OF TEACHING – Explaining concepts to others solidifies your own understanding
* OPEN SOURCE CONTRIBUTION – Small PRs lead to community recognition and larger opportunities
* PORTFOLIO OVER RESUME – Your public work speaks louder than credentials for most tech roles
* FIND YOUR COMMUNITY – Share specifically with people who appreciate and understand what you're trying to accomplish
7. Geography Is No Longer Our Master
* REMOTE-FIRST THINKING – The best programming communities exist online, not just in Silicon Valley
* CREATE YOUR OWN SCENE – Start the meetup, Discord server, or study group you wish existed
* GLOBAL COLLABORATION – Time zones are a smaller barrier than ever for finding your people
* DIGITAL GARDENS – Build your online presence where like-minded developers can find you
* THE IMPORTANCE OF LEAVING HOME – Sometimes physical relocation or travel provides fresh perspective
8. Be Nice (The World Is a Small Town)
* TECH REPUTATION MATTERS – The industry is smaller than you think; today's junior dev might review your job application tomorrow
* CRITICISM VS. TROLLING – Learn to give constructive code reviews that help rather than demoralize
* LIFT AS YOU CLIMB – Mentor others once you've mastered something; it creates a virtuous cycle
* COMMUNITY CONTRIBUTION – The most respected developers help others and share knowledge freely
* COLLABORATION OVER COMPETITION – Programming thrives on shared knowledge and standards
9. Be Boring (It's the Only Way to Get Work Done)
* CONSISTENT HABITS BEAT MOTIVATION – Commit code daily, even when inspiration is low
* THE MYTH OF THE 10X DEVELOPER – Steady, deliberate practice matters more than sporadic brilliance
* TAKE CARE OF YOURSELF – Sleep, exercise, and nutrition directly impact your ability to solve complex problems
* AUTOMATE THE MUNDANE – Create processes that protect your mental energy for the hard problems
* FINANCIAL STABILITY ENABLES RISK – Having your basics covered allows you to take creative chances in your work
10. Creativity Is Subtraction
* CONSTRAINTS ENABLE CREATIVITY – Limited resources often produce more innovative solutions than unlimited options
* CHOOSE YOUR TECH STACK WISELY – Mastering fewer technologies deeply beats shallow knowledge of many
* THE POWER OF SAYING NO – Focus means declining good opportunities to pursue great ones
* MINIMALIST CODE – Removing unnecessary features often creates more elegant, maintainable solutions
* THE COURAGE TO DELETE – Sometimes your best contribution is removing 100 lines of code rather than adding them
Conclusion
For us in the Papafam community, "Steal Like an Artist" isn't just about creativity—it's a practical framework for growing as developers. Whether you're building web apps, training machine learning models, or crafting elegant algorithms, the principles of thoughtful "stealing" can transform how you approach problems. Remember that every great programmer started by reverse-engineering others' work, gradually developing their voice, and then sharing what they've learned. The next time you feel stuck or uninspired, don't just stare at the blinking cursor—look around, steal like an artist, and build something that only you could create.
Keep coding, keep creating, and keep stealing like artists! 💻✨
4
7 comments
Raymond Adeniyi
6
Code, Create, and Steal: Another way to Level up (A Programmer's Guide to Austin Kleon's "Steal Like an Artist")
University of Code
skool.com/universityofcode
You'll get Exclusive Lessons & Content, Badass Community Support & More here to elevate as a Dev!
Leaderboard (30-day)
Powered by