It was the summer of 1969…
No, just kidding this is a blog post about software engineering.
The application I built is made with React and Redux on the front end and Rails in API mode on the back end.
About the app
The concept of the application is that users can create an account and keep track of all of the items on their wishlist from a single location.
Transitioning right into the technology, Redux was definitely the most challenging aspect of creating this project. …
This project uses the fetch API to communicate asynchronously with Rails in JSON.
It’s probably not a surprise that getting the frontend and backend to exchange data was the most difficult aspect of this project.
On the backend, a major hurdle was formatting the JSON response to the GET request so each restaurant is passed as an object containing an array of its own dishes.
For this CRUD application I chose to create a website where users can upload and modify additions to their coral collection.
The database facing portion of the application is administered using Active Record and PostgreSQL as the database. I decided to use Postgres rather than SQLite3 because Postgres.app for Mac and Postbird make visualizing the data much easier than having to rely only on Tux.
My models consist of a User and a Post. Users can have many posts and Posts belong to Users.
I have 3 controllers: Application Controller, Post Controller, and User Controller. One of the…
This project is built in General Purpose Ruby
The Gems used are: curb, json, and require_all
Figuring out how to connect to an external data source was one of the bigger challenges in this project. I settled on using curb with json in order to connect to an API (https://docs.thecatapi.com/) and then have access to the properties.
Curb itself wraps the data as a string so I had to parse it in order to perform the manipulations in my class instance methods.
Being an object oriented project at its core, all data processing and presentation to…