My goal here is to share my experience attending Flatiron’s Online Web Development Program from October 2017 to April 2018. A lot of people ask about this, so here is my long answer.
Git gets a lot easier the more you just dig in and use it. There’s an inflection point on learning anything, where you can move on from just the basic fundamentals of understanding something to understanding something so well that you can start to think more creatively while using the new skill. Think of each commit as a a friendly ghost that you can conjure up to learn about the code’s past. Stay with me here.
Writing tests before you develop may help you write better code. I didn’t understand the full extent of the benefits of TDD until I actually wrote tests myself and then incrementally wrote code based on those tests. This post will share how I got started writing tests in Rails. I will walk you through getting started by creating a simple Rails API and then writing a test that determines whether or not requesting a specific resource will result in rendering the data you want.
One thing to consider when you start developing an application is the organization of your git repos. Monorepo is an organization structure where all of your code is one repo, and multi-repo involves organizing code across multiple repos. When I built Greenthumb Gardens, I used something similar to the monorepo structure because I nested the client in a folder inside of the Rails API. Typically, monorepos are a bunch of different high level folders in the same repo.