Learning Ruby- From Mistakes

Someone once remarked that you can wake up one day and find yourself great..True it happens, but to one person in a thousand. Contrary to his remarks, my narrative is that life is a series of small progressive steps. When making this steps, you need to know that you are making them, otherwise, it will be fate that can lead you to unknown lands. Hello, I am writing from Kenya, my name is Samson Chege, I am currently in my day one of my Andela Remote Boot-camp. In the next few lines, I am going to share with you my most recent and challenging learning experience.
So I decided I had to Ruby on Rails. Then I downloaded some book from the scary web, and indulged into serious “rubying”. It Is two months down the line, I am almost done reading a book on ruby, I still cannot figure it out how to get a web page running using this language. Then there are this words that keep ringing in my mind; “when things are not working bro, change your tact”. I should remember who whispered these words to me so that I can give them credit next time. I had to change tact, I rushed to my usual place Quora and made some searches. In the end, I came out with a jargon…” learning by doing”.
I first set my eyes on Ruby on Rails Tutorial by Michael Hartls, the recommendations were on the wall: ‘Deploy your app after every major step’. Despite that, I found myself contradicting this before long,(after all am just human- humans are built atop imperfections). I was so eager to see the app working on my local machine that I choose to just move and move, ignoring deployment, ignoring any tests. A common human mistake, valuing the end product at the expense of the process. After all, is “the end justifies the means” such a common phrase?
Now the app is working on development mode, its time to push it to Heroku . And all manners of errors are showing up. Particularly, Execjs is throwing an error. All answers from the web are not working, it seems my problem is very isolated. On the other side, Windows is throwing a “This App Cant Run on Your PC” error. Spent a lot of time on it and made little progress. Honestly, I cant tell where the problem is. All my attention is now on the Boot-camp, I will revisit this sooner or later.
In mitigating the damage a mistake does to you, you must not let it go before you extract a lesson from it. Never let it go. There are things that at first don’t seem important. In my case, those were tests, incremental development and other things that seem small until you run into a stopper. Am hoping to implement these on my next app. Meanwhile, I will soon be abandoning Windows, Linux here I come.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.