Week 1 of My Coding Journey with the Firehose Project
It was six o’clock. I got off work at seven. I still had stuff to do for my day job, but I had been working on building my first app for the past half hour. Everything was going swimmingly (aside from the usual constant fear that I wasn’t understanding anything), but I had just reached a road block.
After adding a bunch of html and css and performing a bunch of ruby actions, most of which I hoped that I understood, I refreshed my app to find nothing changed. I went through my standard debugging steps. Were there any typos? I triple checked and found none. Did I accidentally skip some directions? I reread the incredibly detailed directions. Nothing
That was when I started to lose it. I kept looking for issues; I rewrote code; I refreshed everything; I read every forum post. I was becoming incredibly frustrated, and, as is typical when frustrated, I began to despair for my entire existence on this mortal coil. I thought I was a fool to even think that I could learn to code. “This stuff takes YEARS for people to master,” I said to myself.
At 6:45, I realized that I was refreshing my web app from my heroku page, but I had made all of my changes on my local disk. I ran my local app, and, lo and behold, it worked perfectly. I had to take a step away and finish my day job work to decompress.
I had driven myself to the brink of quitting everything over an error that was entirely imaginary. In my experience, the hardest parts of almost any venture are summoning the will to start and fighting the urge to quit. I came face to face with the latter challenge over an issue that essentially didn’t exist. I find a strange comfort in that.
I am learning so much in the Firehose Project, and I’m incredibly excited to kickstart my career and develop a lifelong passion over the next few months.