Faasos — Surprises Under Wraps
In any coding bootcamp, working as part of a team at some point is to be expected since professional software development is typically a result of team work. This time I had the chance to work as part of a team to clone https://www.faasos.com.
The Life Cycle of the Project
This is the phase where we went about figuring out how to go about the project we were handed. Constructive criticism and making people heard were significant at this stage. We made sure to contribute to ideas to make our initial propositions stronger. Working as a team enabled us to spot potential downfalls in each one of our ideas. We were also able to stress test and improve upon them.
We had to determine what the end product would feature and look like since we realised that one week was hardly sufficient to clone and build a fully functioning website incorporating every single feature.
The Creation Phase — Leg 1
- A landing page for the website
- Login and signup features
- Product page with the ‘add to cart’ functionality
- Checkout page
- Payment page
We would meet in the mornings in order to prioritise the tasks that were the most important, discuss any obstacles, then go back to work on said tasks individually, and then gather again in the evenings with the objective of syncing up all of our individual tasks. We also made sure to work out the things that needed to be accomplished by the next meeting. This was repeated until the end of the project. Working this way also meant that each member of the team had the opportunity to contribute to all aspects of the project.
The Creation Phase — Leg 2
In leg 2 of the project, the expectation from the team was to divide the website into two parts: frontend and backend. The goal was to rewire the inner workings of the website such that it would function more like the websites we see today. This meant writing scripts to allow the frontend to make requests and fetch the appropriate response from the server side of the website.
Any data that would have earlier been stored in the local storage, meaning the user’s system, would now be stored in a cloud database. We used MongoDB for this purpose and everything from information about the user to product details are stored and retrieved from the database through corresponding API calls as per requirements. The server side code was written using Node.js and Express.
The melding of the client side code with the server side code, while not especially difficult, did take us quite a bit of time and came with its own obstacles, all of which we were able to tackle head-on with our combined efforts.
The Final Presentation
Getting to present the project as a team was great practice for communicating in a professional environment. Being able to deliver information about the functionalities of the website in a simple, succinct manner as a group required us to be relaxed and focused on our would-be audience’s needs.
This project was a chance to learn and apply new skills with each one of us moving forward together. Working as a team while ensuring that there is agreement on the end goal, open communication, and mutual respect amongst teammates takes us farther than any one of us can go.