Hello everyone! After a summer hiatus, we are back and ready to finish our frontend. In order to do so, we need to discuss a few decisions I’ve made regarding how that’s going to happen.
Apologies for how long this took to turn around. A combination of family, work, and school have delayed me here, but fortunately, we are back on track. I hope you enjoy!
At the completion of Part 1, we established what routes we needed to construct for our API. …
Have you ever heard the phrase “you can rest when your dead”? We’ll those folks clearly have never implemented a RESTful API before!
In this article, we are going to dive into what it takes to build our very own API. As I began writing this article I thought we could plan and build in one big swoop but I realized that would be a veryyy long article. …
After Episode 3, we’ve successfully planned our database schema. While this is nice we now need this database to exist.
Before we solve this problem I need you to download one required app from the web: SQLite Studio. …
Before we can build our database it’s important that we take some time to design what our database will look like. This might sound tedious but when we start thinking about data, things can get complicated quickly.
For example, in our application alone we’ll be juggling admins, kennels, dogs, and more. Planning out how these will all fit and relate in our database will go along way towards preventing problems in the future. …
Let’s not leave it up to Fido on this one. Instead, we’ll rely on Express.js to get us up and running in just a few minutes!
According to its website, Express is:
… a minimal and flexible Node.js web application framework that provides a robust set of features for web and mobile applications.
The way we can think about Express is, it sits on top of our Node.js server and allows us to add bonus functionality that makes building our API much easier. …
For the purpose of this exercise, we will be building a dog adoption site where kennels (admins) can upload pups for adoption. Site visitors can view available doggos and submit requests to adopt them. Site visitors will not need to log in, but rather provide personal information to get in contact with a kennel. This will send a notification to our admins home page.
In programming, we use conditional logic for almost every problem we try to solve. Meaning that
if something happens
then do this,
if not either proceed as is or do something
This concept drives a lot of the logic in our applications but can sometimes a headache to track and manage. What if there was a way to write it neater, cleaner, and faster?
That’s where ternary operations come into play. A ternary operator is simply a shortcut way to write a
if/else statement. It generally condenses 5 lines of code down to 1–2 lines.
This post will review our traditional
if/else statement, how we translate that to a ternary operator and then conclude with some real-life example. …
I recently had a discussion with my older brother, Nick, about the progress of my personal website. While it was visually appealing, I feared the content was too generic… and in my brother’s eyes, it was as well.
The glaring issue to us was the lack of voice in the content. I think this is something a lot of young developers struggle with. While we learn these great technologies, we struggle to create content that reflects our unique characteristics.