Ruby provides programmers with many different iterator methods, which at first glance may feel overwhelming or counter-intuitive. What is the difference between all of them, and which should we use in certain circumstances? Does it even make a difference?
In mid-October I detailed the process of creating my first gem: Standings, a command line gem which allows users to see the current standings of the English Premier League. I recently expanded the gem's functionality to allow users to see the scores from multiple European soccer leagues.
A few weeks ago, I built a Ruby script to find the current standings of the English Premier League and display them in the terminal. I decided to turn my standalone script into a gem called Standings.
I recently redesigned scottluptowski.com to function as a blog and a portfolio of past work. My primary objective for the redesign was to work with a new (to me) technology which would let me create a dual-purpose blog/portfolio site while affording me maximum control and customizability.
Yesterday I wrote about how one of my favorite lessons so far from Flatiron is to treat error messages as hints, rather than as something to be upset about. There's another great piece of advice that we've been taught over and over again.
Until recently, I never liked receiving errors in Ruby. Compared with other programming languages, in which an error typically means that things simply don't work correctly, Ruby seems to go out of its way to bark at the programmer.