I smile when I think back to creating my Sinatra project, B.R. (Before Rails) time - oh, how times were simple yet unscalable compared to the world of Ruby on Rails. I entered Rails in naivety, thinking I would just switch some syntax and conventions around and transition to the Rails track with greater ease than going from my old 2000 Honda Civic to my 2017 Volkswagan Passat with an upgraded engine and Bluetooth for my convenience. However, unlike cars, frameworks require a bit more competence other than the muscle memory needed to drive any automatic car you get behind the wheel of. Lucky for drivers, we don’t need to know much about the automotive mechanics in order to be an efficient driver. As programmers, learning the technicality behind Rails magic is not only encouraged, but necessary while using this complex yet brilliant paradigm successfully.
I designed my Sinatra project to build off my first project, the CLI data gem. For the latter, I scraped a skincare website for different products, categorized them, and gave users further details for each product. I felt proud I was able to create synergistic class models, CLI logic and scraping methods to form a simple little functioning gem. But, I knew entering the Sinatra section, everything was about to come together and the power of coding, from the database and models, to views and everything in between, was about to leverage my ability to create real value.
Before beginning this project, I projected my timeline to be around three to four days, maximum. In reality, it took me a good five days to code my CLI gem, and currently, I still have the video walkthrough to record before submitting everything for approval.
The more I talk with the students of Flatiron, meet other programmers and read others’ blog posts shaped around the rhetoric of :