Inspiration
-Vibes, existing VSCode extensions, "hat", "banana", and
ACKNOWLEDGEMENTS
-ChatGPT was used throughout the process for questions, generating starter code, and debugging. -VSCode documentation was used for API calls and using functions -StackOverflow for answering general code questions
REFLECTION -We had a lot of different ideas for our project, but we thought this one was the most feasible given the timeframe and wanted to make a product that would benefit the Tufts CS community. We also thought that this would allow us to learn different technologies and tackle new problems, along with making a VSCode extension, which has been on the bucket list for a long time.
-There may be some edge cases we aren't aware of, and since the CodeClock timer is intended for long-term use, more testing would be necessary before adding it to the VSCode extension store.
-One of the biggest challenges was building the backend and having all the data we wanted in the same place. It was also a challenge to work in a group of 6, since everyone was working on a different aspect of the project and we wanted to efficiently combine our work. Using Git was very helpful for this, and we always stayed on the main branch to try to speed up this process even more.
-It was fun to work in a friend group and work on the process as much as we could. We also learned a lot about prompting AI models, their effectiveness, and how to work as a team to make an MVP (minimum viable product). We enjoyed this process throughout the weekend and with more time we could have developed it even more and improve the user experience. -->
Built With
- amazon-web-services
- clerk
- ec2
- extensions
- git
- github
- javascript
- mongodb
- next.js
- react.js
- tailwindcss
- vscode
Log in or sign up for Devpost to join the conversation.