Try / Catch
Repo ||
Deployed
Collaborative error-handling app for aspiring programmers
React frontend, Ruby / Sinatra backend, SQL database. Create issues that describe a problem, invite other users to work with you, and choose which issues you want to share with your collaborators. Users can post notes offering tips and guidance to issues they own or that have been shared with them. Users have full CRUD on issues that they created.
Try Catch: Case Study
There are many places on the web where people can make posts and get help on programming issues, with StackOverflow being one of the most respected and widely used. However, posting about an issue in such a public matter is daunting, especially for people new to programming. That is the audience that Try / Catch is geared toward.
Of course, choosing to make an app about solving errors in code meant that I was tempting fate. Development went smoothly until the last few days, when I realized that the app was not always updating the display immediately in response to user input.
This seemingly minor issue proved to be a real nightmare, popping up in several places and resisting simple fixes. Fully debugging the issue required more than 40 hours of tireless, relentless coding in the two days leading up to deployment, as I delved deeply into React in order to get the app updating responsively in real time. At 3 AM on the morning I was scheduled to present, I achieved a final, fully functional version of the app I had envisioned.
As stressful as the situation was, I learned a great deal. User interaction (via collaboration on issues, in the case of this app) is exponential in its contact points with Murphy's Law — and will take longer to get right than you plan for it. Thorough bug testing should start early, and never stop. What seem like minor and "quarantined" problems will spread.
And you should never tempt the gods of code (and irony) by making an app designed to help people solve errors.