Notes

Troubles faced

• I should have integrated the linter into the commit chain. I was not disciplined in running the linter resulting in extra time spent refactoring and testing code.
• Getting features to work correctly that relied on time proved to be a road block. For example, a server call requesting Tournaments that have not started yet, would return different results depending on if the call was made on my local environment or a production environment. Syncing time between the database server and the express server was something that took time to do correctly. A Now() or a current_time() reference in the UI vs the server (local or production env.) vs the database server, was not consistent and needed to be configured correctly
• Figuring out how to best handle the issue of lost or forgotten passwords was a road block. Configuring a means of emailing a User in order to reset their password was not something I thought appropriate for the context of this project.
• Internet bots creating large amounts of fake accounts occurred. In turn, Google's recaptcha tool was integrated into the User registration process.
• Debugging the Express server was not always pretty. I am wondering if there is a tool that can be used to step through the Express server code similar to Google's developer tools.
• I could have documented some of the code that interacts with the database better. Whether through comments or dedicated documentation in the wiki, an improvement in documentation would help. Time could have been saved debugging some of the non-trivial database queries had there been better documentation.
• Error handling: sometimes they were logged to the console, sometimes they were sent to the client, sometimes custom messages were sent to the client, sometimes errors resulted in a 200 being sent to the client. More consistency with error handling would improve the application.
• Heroku changed their payment structure resulting in a migration from the Heroku platform to an Amazon EC2 instance