Overthinking Learning to Code

Learning to code is daunting. It’s not so much understanding what it does that’s the problem—it’s trying to figure out why they wrote what they did.

Looking through another persons code always gives me too many questions and I know deep down the answers are irrelevant.

Questions like:

  • Why did they decide to name the variable that? (A: It popped up into their head?)
  • How would I come up code like that? (A: You don’t. Write it your own way)
  • What if I do mine the wrong way? (A: The wrong way is it not working)

I need to teach myself to find my own way and to find my own little style.

These developers have written this code because that’s the way they thought about it. Their brain and thought processes are different to mine. I code differently.

Doesn’t matter whether that’s better or worse, as long as I can understand and communicate with comments. As long as it doesn’t cause customers pain because it’s incredibility slow or buggy.

As long as it works and does the job it’s intended to do.

So it’s time for me to stop worrying about being ‘bad’ at coding. I need to do the best I can with the knowledge I have.

It’s time to learn by breaking, fixing, and pushing.


I’m writing about something that interests me every day for a year. This is day 71 of 365. ✌️