TCOC was such a long project that we hardly know where to start from. We were just 3 doe-eyed sophomores that decided to be in a group. This was our first hackathon, and we were all in the same fraternity, so why not! We started browsing ideas, but they all seemed to be coming back to the idea of scheduling. Then, we all started to compare our own schedules, complaining about how hard ours was and whatnot. Then it hit: this is our idea! And so it begun!
We are most proud of the fact that it looks like a legitimate website. We came in expecting that we would just goof off for a while, but the fact that we had 2 projects to present in the end is absolutely incredible.
The project is split into 2 main parts: the website and the CLI. The website, which Ryan spent over a dozen hours straight on, is the meat and bones of the project. From the website, you can see how everyone else is ranking classes at tufts, and you can even contribute yourself! One might not notice the immense amount of detail paid to design on the site. Several hours were put into designing the website, logo, about me/contact pages (which we highly recommend reading), to name a few. The combination of thoughtful design and practical, innovative programming involving all sorts of programs really shows through in the website.
The CLI (command line interface), on the other hand, was a very rudimentary way of creating the initial skeleton for the project; however, David took things a step farther and spent several hours making sure that the command line interface would be as snarky and clever as possible. While it ended up not being essential to the website, it is still a fun way to see how difficult one's schedule is.
To conclude, there's really just one anecdote that perfectly describes the night. Around midnight, Ryan suddenly came to a horrifying conclusion, saying "there's no way I can integrate flask into a heroku app, I don't know either of those at all!" And yet, he managed to do it. Justin was able to do the impossible and learn how to integrate Parse into a language he had no idea how to use. David was able to find ways to connect all of the aspects of the program together to make one great program. In the end, it was never about what we couldn't do, but rather what we could learn how to do. After all, it's fun to do the impossible!
-David, Ryan, and Justin