Inspiration
We wanted to know when smore pizza and lamb chops would grace our presences, stomachs, post-digestive system events, and midterm depression.
What it does
It downloads data from UCLA menus up to 25 days in the future (normally, you can only go a week in the future but we figured out how to get data past that) and converts the data into a searchable form so you can find when and where dishes with the keyword in it can be served
How we built it
We found a python slithering through the hackathon grounds, and we could not in good conscience let it bite anyone. So using dark magic, we managed to convert this said python into a programming language, which we then retooled to download the data off of the UCLA dining website and into a form that could easily be searched.
Challenges we ran into
Our first project was too ambitious. Also since there was one main source file collaboration was hard.
Accomplishments that we're proud of
We actually came out of this with something. And we can add it to our resumes.
What we learned
Make sure you know about web development and front/backend stuff before going to a hackathon; you ain't got time to learn anything else.
What's next for UCLA Menu Crawler
Collect dust, and get occasionally taken out to please potential employers.
Log in or sign up for Devpost to join the conversation.