MusicGearShareis a Craig’s List style application where users can sign up and share their music equipment with each other, including anything ranging from instruments, accessories, sound equipment, and more. After signing up, users can search gear thats available to rent and messages each other to coordinate sharing and renting.
Using Git is a crucial part of most developers’ workflows, and so is writing committing messages for the changes they make. As a newer developer, I did some research into what make a good commit message and how I can improve my commits. Having clear, concise, and sufficiently detailed messages in critical when working on a project and even more so when working with other developers.
In this post I’ll do a deep dive into how and why I refactored each feature.
A great question that I see continually: Should I use a custom authentication system or use a pre-existing solution (like Devise)? There are a lot of arguments either way, but the answer is simple: it depends! For this discussion, I’ll use Devise as our example.
While working on my Rails Project Management application, I had an idea. If I can use Bootstrap’s gem to import CSS styles and JS libraries, can I make one?
During the course of any project there are often CSS styles, JS scripts, and other elements that I like to reuse. After some Googling, I found an excellent video on how to create a gem for front end libraries – and it’s super easy (like, less than 10 minutes of work if you’re already familiar with how to make Ruby Gems). In this post I’ll show you how to create your own.
A hash is one of the most frequently used data types in Ruby and several other programming languages. A hash is a collection of key-value pairs, like this: “car” => “red”. It is similar to an array, except indexing is done by keys in the hash, not an integer index. I’ve compiled this list as some of my favorite tips for using Ruby hashes.
Rails Project Management, (or just RailsPM) is my first full scale web application, built from scratch for my Flatiron School Ruby on Rails assessment. As a former project manager, I thought it would be fun to build an app based on the knowledge I acquired at my previous job. While realistically I wouldn’t be able to currently build an application that could complete with robust software on the current market (like Teamwork, my favorite PM application), I had a lot of fun in the process. There were a number of challenges I faced along the way but I also learned a lot!
In Rails, validations are special method calls defined at the top of the model class. Validations protect your database by preventing model instances from being saved to the database if they contain invalid data. Rails uses ActiveRecord to execute these validations. Keep in mind that AR validations are not the same as database validations, which check for things such as string length, data type, etc.
In the following post I’m going to cover implementing both basic and custom Rails validations. I had a tough time figuring out how to make the custom validations work since there was a lack of detailed information about them.