About My Third Flatiron School Project

For this Flatiron School project unlike my last one, I stuck closely to the project design requirements and finished my MVP (minimum viable product) by Tuesday for this one-week project, which was due by Sunday evening. For my previous two one-week long Flatiron projects, each due ultimately on Sunday night, I finished their MVPs on Wednesday and Sunday, respectively. So, with this project, I was getting back to a preferred form of ensuring on-time completion of the project, by focusing on the customers’ (my instructors) requirements first, rather than doing anything that I really wanted to do first.

The focus for this project was mainly on the back end, as opposed to the front end, and it did not have to be hosted. So, I did not host my project, I had a very simple front end, and finished my back end first using the simplest possible one-to-many relationship between them. I also did not shy away from using much of the instructor’s example code that he presented to the class to get the project finished. I used the balance of my time working my two jobs and providing realism to my web app by taking pictures of items I would sell on it and improving the formatting of the project listings above the base case.

The app still does not look polished but that was not the point of the project — it was to demonstrate a working back end written just with Ruby and Rack. That’s just what my project does, thanks to my early completion of its MVP.