Search for a command to run...
I'm a life-long, self-directed learner with a love for libraries, documentation, and all things tech.
Currently serving the people at the Carnegie Library of Pittsburgh 📚 Formerly @ Codédex 👾 and Codecademy 🧑🏻💻
Extracurriculars (in no particular order): 🧑🏻🍳 Cooking 📖 Reading (mostly non-fic of all kinds) 🎸 Listening to/playing music 🎙️ Enjoying awesome podcasts. 🏃🏻 Running, walking, moving in general! :D
Thanks for reading!
No comments yet. Be the first to comment.
It's been a while... Hello! It's been a long time since I last published a blog post here. 2022 was an interesting year for me. A few of the highlights include: Moving back to my hometown in Pittsburgh, PA Helping bring in new contributors for Code...
Hello, #DEVCommunity! My name is Brandon and I'm a Content Contributor from the Free Team at Codecademy. For the past few months, we've collaborated in a company-wide effort and delved into the world of user-generated content (UGC) as it relates to c...
Is this the Description?
New Job! New Drive! New Ideas!
The Gatsby CLI Part of what makes Gatsby a powerful frontend framework is its list of builtin commands via the Gatsby CLI tool . Commands such as gatsby new and gatsby build allow for a smooth experience with development and deployment, respectively...
This is a supplement to a previous post about Fitness Tracker Sinatra app I built.
Upon submission of my project, I decided to do some styling to make the app a little easier on the eyes. However, I discovered a litany of underlying bugs that proved too detrimental to ignore. I'm writing this post to touch on what happened, what I did to fix things and why I made the changes I made.
I discovered two monumental bugs.
(1) Because an Excercise belongs_to a Routine, there's a one-to-one relationship and, coupled with the fact that each Exercise was unique by name, Exercises could inadvertenly be "taken" from one User if another User created (or added) an Exercise of the same name
(2) A join-table, RoutineExercise, was created to allow for an Exercise to be able to point to many routines (using a has_many through: relationship). However, this was cause a bug where a newly created (or added) Exercise would display twice because it was tethered to two classes.
After much thought and deliberation, I decided to simplify the model structure and do away with the Routine model altogether. This meant that a User now has_many Exercises and an Exercise belongs_toaUser`.
At first, I felt a little embarrassed about having to sort of scrap my original idea and work with a simpler one. But then I realized that the point of the project was learning about Sinatra and how you can build a simple web app with it, utilizing sessions, user auth and the seven RESTful routes.
The tough lesson I learned from this project was that it is really important to build out that minimum viable product as fast and well as possible before delving into extra features. For my sake as a developer who wants to strike out in the industry, I needed to mature professionally and this project felt like sort of a wake up call.
Thankfully, the refactoring process was simple and seamless. Feel free to fork and clone the repo and check out the site!
Happy Coding!