These days, you can’t turn around twice without someone trying to teach you how to code. So why the heck did I write my own book?
When my daughters started learning to code, I discovered that most tutorials were as dry as dust. If you wanted something more fun, you could play a coding game and write commands to move a character around a maze (like a princess, a zombie, a turtle, whatever). But unlike real programming, there was no chance to be creative. There was no freedom. There was no invitation to build your own programs.
I wanted something different. Something…
- Hands-on. If you want to learn a new skill, you need to practice. Otherwise, it’s just a bunch of theory swimming around in your head.
- No setup required. The world is full of amazing frameworks, tools, and code editors. But who wants to install a bunch of software before you even get started?
- Tiny. I’m a programming nerd, so I like talking about things like Big O notation. But no one needs to be buried in theory at the start of their journey. In this book, every chapter is a bite-sized lesson that you can usually finish in one sitting.
- Kinda fun. Not everyone has the motivation to learn from an old-fashioned textbook. But who doesn’t want to play dice with a cheating goblin?
So I decided to make something of my own. Then I unleashed it on my family.
This is the result of those experiments.
Shouldn’t this be in Python or something? Well, not necessarily…
Can adults read this book?
Sure, we don’t discriminate!
Is this a coding game?
This is not a code simulation, game, code-themed activity, or coder cosplay. You’re going to write tiny amounts of Real Code™.
This is an important difference. Games can be fun, and they can teach people, too. But to start developing a programmer’s mindset, you need to write real code in an unbounded environment. Good luck!
How can I support the Tiny Introductions project?
Please enjoy this book guilt-free! Share it with your family! Give it to your friends! There’s no limit, so long as you don’t change it or pass it off as your own work.
If you find mistakes, please let me know. I greatly benefit from people pointing out problems I’ve missed, so they don’t frustrate other readers. Send me your complaints, comments, questions, and suggestions to email@example.com.