I’ve learned so much in these past 3 months of school at Flatiron. Everyday, no matter if after work or early in morning on my days off, I login and start again on this path to becoming a web developer. To get to that goal of becoming a professional developer, I must learn and master these concepts and technologies that are part of that job.
This last week and a half I’ve been working through SQL (Structured Query Language) which has been a nice change of things for me since I’ve been entrenched with Ruby for the past 60+ days and getting to see something different and new was a nice change. I’ve also always wanted to learn about databases and backend programming since all of my experience prior to starting at Flatiron has been exclusively Front End. Luckily after some hard work and time SQL and ORM are starting to become a whole lot clearer to me.
After ten days of work, i’m finally at the last few stages of my CLI gem portfolio project and its been a journey. I have learned a lot over this last ten days and feel that i’ve definitely improved my programming skills. I feel better equipped on how to approach a coding problem and figure out a solution. I have to thank Avi from Flatiron for his daily_deals CLI walkthrough and approaching the design of an app from the entry point, and in my case that was the user interface. By starting with the design of the interface first I was able to define how I wanted my program to work and then it was just a matter of creating the objects, methods, and getting the data to make it function.
One of the most popular Ruby libraries right now is RSpec. It’s a tool for applying a Test Driven Development approach to application design where we first write tests and follow up with code that meets the test expectations. It is how our labs are structured at FlatironSchool. It allows us to concentrate first on writing a solution then going back and refactoring. It takes a lot of frustration and mystery out of what isn’t working with our programs.
If you are learning Ruby either from an online tutorial or book chances are you have worked with IRB. If you haven’t, IRB means ‘Interactive Ruby’, the RB is a reference to the .rb extension of Ruby files. It’s a Ruby shell and it allows us to experiment with code and receive an immediate response that executes our code and shows its return value. Below we open the ‘irb’ shell with the command
irb. Then we are free to experiment: