What Coding Actually Looks Like Day to Day
Okay so here's the thing. Before we install a single piece of software, I want to fix an image in your head, because I think most people walk in here with the wrong one.
You're picturing someone in a hoodie typing fast, lines of green text scrolling by, music playing, everything clicking into place in real time. That's a movie. That is not coding.
Here's what coding actually looks like most days. You write four lines. You run them. Something's wrong. You stare at it. You read the error message, which sounds like it's yelling at you in a language you almost speak. You fix one tiny thing. You run it again. Maybe it works. Maybe something else breaks now. Repeat.
That's it. That's the job. If you came here hoping for the movie version, I'm sorry, but the real version is better once you get used to it, I promise.
The actual daily rhythm
Most of my time writing a script breaks down like this:
- A little bit of typing
- A lot of reading what the computer tells me back
- A fair amount of just sitting there thinking
- Occasional small noises of triumph
- Occasional larger noises that are not triumph
I want you to notice that "typing" is a small slice of that pie. Coding is mostly reading and thinking. The typing part is almost the reward at the end.
Clever is not the goal
Here's an opinion of mine, and I hold it pretty firm: clever code is bad code.
I say this because I learned it the hard way. A while back I wrote this beautiful, tight, one-line solution to some little problem I had. Felt like a genius. Showed it to my son Jared, who does computer stuff for real, and he gave me a look. Not even a bad look. Just a look.
A week later I opened that same file to change something small, and I could not for the life of me figure out what my own code was doing. One line. My line. I had to sit there and basically reverse-engineer myself, which is a special kind of embarrassing.
So now I write boring code on purpose. Longer than it needs to be sometimes. Named things clearly. Broken into steps a stranger could follow, because that stranger is going to be me in three weeks, and future-me does not remember what past-me was thinking. Nobody does. That's not a flaw in you, it's just how brains work.
We're going to write boring, clear code in this class. If it looks a little unglamorous, that's on purpose.
What "figuring out why the computer hates you" feels like
You're going to hit a wall in this class. Probably today. That's normal, that's expected, that's most of the job.
Here's what it'll feel like: you'll type something that looks completely correct, run it, and get an error you don't understand. You'll stare at it. You'll change something at random hoping it fixes itself. Sometimes that works, which is a trap, because then you don't know why it worked, and it'll break again later in a different way.
The better move, the move we'll practice, is slowing down and reading the error message like it's actually trying to help you, because it is. It just talks funny.
One real thing I want you to hear now
You do not need to be good at math to do this. I know that's the thing everybody says about coding, and it's mostly wrong. What you need is patience and a willingness to read carefully. That's most of it. If you can follow a recipe, adjust it when your altitude messes with the rise time, and figure out what went wrong when the bread's dense, you've already got the actual skill set. Coding is a lot closer to that than it is to algebra class.
What we'll build toward
Over the next few weeks you're going to write small, dumb, simple little programs. Not because I'm limiting you, but because that's genuinely how this works. Nobody writes something big on day one. You write something that renames one file, or adds two numbers, or prints your name back to you, and you feel a small, real satisfaction that is honestly a little out of proportion to what you just did.
That feeling doesn't go away. I still get it. It's most of why I keep doing this.
Before next time: you don't need to do anything yet, just come with a laptop that turns on and isn't about to die on you, we'll get everything installed together next lesson.