What I Wish I Knew Before I Learned to Code

The questions that held me back

Keri Savoca
Feb 13 · 7 min read
Photo by Chris Ried on Unsplash

I’ve been “coding” since I was a child. I didn’t think I was doing anything remarkable; I thought HTML was common knowledge back in the era of AOL 3.0 and Geocities. I used to spend hours creating websites (and graphics to adorn them), even though my AOL account had a time limit (thanks, parental controls) and I could only work on my websites for an hour a day.

If I couldn’t figure something out, I created a workaround. I had a workaround for everything. Looking back, I really pushed HTML to its limits.

HTML made sense to me because I could see my work evolving as I added new lines of code. It was self-explanatory.

But like many children, I eventually forgot all about this hobby and moved on to other ventures.

As a teenager, I worked a summer job in IT… by accident. I had been hired to remove staples from documents to prepare them for scanning, but I always had free time, so they would throw extra projects my way. My supervisor would print out pages and pages of SQL and ask me to find the mistakes and correct them manually. It felt self-explanatory, too, so I did it with ease. Looking back, I have virtually no memories of what the code was expected to do, but I remember learning the syntax and finding typos all over the place.

And then I moved on to other ventures.

As an adult, I built websites for my own projects, but never thought of doing web development as a career, until I began to see advertisements for coding academies. I had no idea what coding was, so I ignored the ads. At some point, though, I saw an ad for a coding academy that included a video… and then realized that “coding” is something I already had experience with.

I breezed through the pre-bootcamp coursework, but on day 1 of the class, I found myself plagued with questions that would eventually prevent me from internalizing anything.

I knew right away that this would hold me back.

As the first day progressed, I filled a notebook with questions.

  1. Why JavaScript? What sets it apart from other programming languages?
  2. Why do people use Ruby for the back end and JavaScript for the front end? Could you theoretically use Ruby for the front end? Why or why not? Could you use JavaScript for the back end? Why or why not?
  3. How do you create a programming language? Don’t you have to program it in another programming language?
  4. Each project on the syllabus has a checklist of requirements. Is this just to force us to use certain languages so that we can be assessed? Wouldn’t it be better to assign a project and make us use critical thinking skills to figure out which languages and frameworks we should be using?
  5. Where exactly do I PUT the code when I’m done? Where do I put the JavaScript?

I bombarded the instructor with these questions before we had even opened a text editor. I needed to understand the bigger picture before I could focus on the programming concepts. I knew that doing exercise after exercise wouldn’t help me retain anything. I needed to see the process from start to finish so that I could know what exactly I was working toward.

As the course went on, I memorized snippets of JavaScript to make pop-up alerts and other flashy features. I wasn’t really conceptualizing… I was just replicating what I had seen. I aced the object-oriented tasks, though.

I remember offering a suggestion: “I really think future cohorts should start with object-oriented programming because it makes sense,” and being told, “I’m pretty sure you’re the only one who feels this way.”

My learning style ultimately affected the way I progressed through the program. I found myself using a variety of apps to practice Ruby and being able to transfer what I learned to my real-world projects. I studied JavaScript by reading and analyzing other people’s code. It was almost like learning a spoken language; I had to learn to read before I could write.

Photo by Christopher Gower on Unsplash

I wish I knew that everyone learns differently.

I wish I knew that it was okay to ask questions.

I wish I knew that everyone brought a different skillset.

Ultimately, I ended up withdrawing from the program 2/3 of the way in because of logistics; it became harder and harder for me to go 4 months without any income, and a few emergencies popped up that made it difficult to get there on time (bye bye, car).

But the lessons I walked away with changed my perspective on education.

I developed a deep appreciation for sharing works in progress.

I know how I learn now.

I learned to appreciate collaboration in education.

I learned to be comfortable with the unknown.

It IS okay to spend time figuring things out. That’s the whole point. It IS okay if you finish an entire project today but then you spend all of tomorrow staring at your screen and wondering what you’ve done wrong.

It’s part of the learning process.

I wish I knew that this would be a lifelong journey.

Photo by Steve Halama on Unsplash

How did you learn to code? What were the biggest obstacles that you faced? Share your thoughts in the comments.

Connect on LinkedIn.

Coding in Simple English

Coding. Simply.

Keri Savoca

Written by

✨ serial questioner • technical writer • I write about everything but my voice never changes • thank you for connecting 👩🏻‍💻 kerisavoca.com

Coding in Simple English

Coding. Simply.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade