Dun dun dun… the rails project is here, a moment of pride and anxiety. First thing first, read the directions and PLAN. Typically, I am wing it and improvise kind of guy. I tried to do that with this rails project.. I also restarted the rails project a couple times. However, messing up and restarting comes with a few lessons that I am glad to have learned.
The difficult part about projects so far is setting up the skeleton of the project. Do I do the same thing I did to make my CLI gem? What goes in a rakefile? What is the difference between a .md or a .txt file and how much does it matter? These are the simple questions that can take up a large part of your time before getting into the actual project. Once the skeleton is all set up, it becomes familiar territory.
The creation of a one’s first gem is an intimidating, confusing, stressful and completely fullfilling milestone for a software engineer in training. At first, the idea of a project is a bit overwhelming and the best way to deal with being overwhelmed is to break it into parts. Thus, it is time to begin creating a gem.