Stack Developer Basilio Bazan III Full Stack Developer John Mills LeMaire Full Stack Developer Pierce Kotarski Full Stack Developer Tyson Smiter Full Stack Developer
◦ We were able to split up work evenly and got plenty done in a short amount of time. ◦ We made the website as modular as we could, keeping our code short and organized • What did we learn? ◦ Increase gunicorn timeouts for websites that don’t load ◦ Use tear up and tear down classes for the unit tests ◦ SQLAlchemy queries are very powerful tools • What can we do better? ◦ We could have gotten more data from previous season’s of basketball in the NBA. ◦ Split the frontend and backend into microservices • What puzzles us? ◦ Why we ran unit tests (typically a dev dependency) in production mode
well? ◦ Search implementation was well done as it updated in real-time with correct results. ◦ About page was well organized and dynamic, member cards that flipped, git commit pie-chart. • What did we learn from their website? ◦ We learned all about different characters and events in the marvel universe • What can they do better? ◦ Reduce some unnecessary information on the tables like ID and last modified. ◦ Distracting backgrounds take away from the data. • What puzzles us about their website? ◦ Why ‘enter the site’ as the main page? Would like to see a better looking first page or the home page right off the bat!