Skip to content

Project Post Mortem

Polina Soshnin edited this page Feb 26, 2016 · 10 revisions

A list of good and bad decisions made in the making of MatchJS.

The Good

  • Before writing a line of code, we had our project thoroughly planned and structured across the full tech stack. As a team of four engineers working together for the first time, we considered it very important for everyone to be engaged in the product roadmap/decision making process.

  • We created mocks and detailed user stories to prioritize and come up with the best user flow for our application.

  • We planned our file structure very carefully, with a good separation of concerns. This led to highly modularized code that could be maintained on both the front and back end. In the front end we had a folder of each angular component. Within it you would find separate files for the model, the view and the controller respectively.

The Bad

Clone this wiki locally