Apr 2025
w/ Sterling Smith
Apr 2025
w/ Sterling Smith
Project Description:
After changing our project idea halfway through the second day, Sterling and I decided to create a tool to help service workers improve the quality of their interactions with the people they encountered. In practice, what we thought this would look like is taking voice recordings on the job (e.g. bodycam recordings of a police officer interacting with a citizen), and using this data to create a summary of their interactions including strengths and weaknesses so that the worker could make informed decisions on what to focus on.
Final Web App Interface
During KU's 2025 hackathon (HackKU2025), I worked with Sterling Smith on our first ever hackathon. Our goal with this was to get comfortable in a hackathon environment and learn some basic skills towards the creation of a project. Although we set off with ambitious goals in mind, we ended up with no final product to be shown at the end of the event.
Stick to the minimum viable product! Don't get 80% of the way to your first MVP, and then start work towards the next one! This is how you end up with a rat's nest of half functioning code.
Commit changes to Git when you have functioning code, so that you can revert to the changes when you inevitably mess it up.
Using a new library always means lots of unexpected complexity, even if it looks like it will only be a few lines of code.
It's okay to build a fun project, it doesn't have to solve some huge problem.
Take live audio input from a user
Identify and tag each speaker (officer & civilian)
Run through LLM to generate a summary
Handle file management for easy access by end user
Use UI for easy access to info
More git stuff (dealing with conflicts)
Other lessons above