I'm sick of my club's equipment checkout system, and I know how to code. So, I'm rebuilding it.

Here are my biggest pet peeves about it:

  1. It's not built for our club. It is designed for a library checkout system, meaning that there are many features that don't suit our system. This pisses me off. Why? Why sort people based on their class period? Why do we write their names down on a paper? Why not just have them login? Why type the name of items instead of pressing buttons? 
  2. It's not fast enough. I'm not an efficiency king, and I don't want to be. But I see my classmates getting stressed because they need to get to class, but need to check people out before hand. That rushing causes equipment to break, people to make mistakes, and overall hurts the tranquility/unity of our space.
So, I'm fixing it. If the equipment managers this year agree to install it, great! If not, then at least I have the experience to add to my portfolio. Regardless, this system must be built to last years into the future. If it needs to be rewritten or replaced next year, then I have failed to contribute meaning to the club.

3/10/26:
A mentality that should be had when coding new shit is "what's the simplest, most fuck ass baby-can-do-it way of having the system?" in other words, just automate a simple process. I'm basically just writing code to automatically remove and add things to a spreadsheet.

Structure:

  1. excel spreadsheet (serves as a database and allows to manually check for things)
  2. python code (to make the system actually work)
  3. A simple CLI or GUI (because no one else is crazy enough to fuck around with code and look though the task box like a lunatic)

Steps:
- get excel working w python
- build the system logic (check in and out)
- have the system work
- implement the login
- add user friendlyness

3/16/26:
Hi! So I just finished building the system logic for everything. The amount of things I have left to do is kind of overwhelming me right now, but I think I just need to sleep is all. It's 11:30 pm, and I woke up today at 4 am for a flight. 
really helpful video: https://www.youtube.com/watch?v=zCEJurLGFRk


3/17/26:
K so I really need to rethink my discipline on school breaks because I didn't wake up at 6, and instead chose to sleep a total of 10 hours. Which, yay health, boo projects. It's currently 11, and I'm about to get started with the interface. 

Okay, coding the interface was not as hard as a thought. It's 4:40, and I need to stop neglecting my other work. So I'm going to stop for today. Here's what the interface looks like, I had Claude generate a dummy spreadsheet because I don't have access to the real one yet. So, ignore the numerical values and admire the pretty colors.


This is under the admin's login, which is wrong. The admin should have access to alter the other user's equipment status and such. I'm going to add the feature soon, but right now I need to focus on:
- having accurate data (fixing the dummy data I added before)
- making the IU nicer bc ts not touchscreen friendly


3/18/26:
Just fixed the spreadsheet, but it's not fully accurate since we have to re-log the equipment this year. Still, good enough for now.
I'm making the UI prettier, since I realized an issue with our closet is how stressful it can be. Thus, I chose a blue color scheme and a dark screen theme thing. It's only later that I realized I made the theme the bisexual flag. Oh well, nothing wrong with a little rep.

Before

After

The color scheme I based it on



3/19/26:
I just wanted to specify this, because I realized I haven't yet. I've been using Claude to check my code and help me work around issues, since I'm relearning programing (which is something I was never really insanely good at in the first place). I do, however, put effort to understand the code. And since the point of this project is to learn, I have written most of the code for this software. I just realize that AI is kind of taking over people's projects, so I should specify it's use within this project. 

With that out of the way, I've got the user interface almost done! I'm fixing a few issues I have with it, but I'm about to move into admin page. I'm gunna try to code the admin page without AI help just to reenforce what I already learnt. I will update if I do end up failing at my mission.

Here's a list of things I want to fix in the user interface before I move onto the admin:
3/20/26:
Writing this at 3 am, told myself I'd go to sleep at 2. I just finished the adjusting a few parts of the UI and incorporating a new feature in the spreadsheet. When I wake up I'll work on the login and scroll feature. Goodnighttt!

Hello! I didn't work on the project any further today. Instead, I choose to let Instagram captivate my attention for far too long. Boooo. Anyways, I'm upset for unrelated reasons, and the idea that I might die without having first lived makes me sick. They can mourn me all they like, I will not step inside their empty casket.

Holy shit! I just realized I never showed you my wire frame. Those of you who don't know, a wire frame is just a concept design for a program, it shows how 





3/22/26:
FYI, I haven't abandoned you or dropped the project. I just realized I haven't done ANY schoolwork this break, and fuck, I have a lot to do. Look at my fucking to do list.
I think I'm gunna pull an all nighter and sleep on the plane ride back to Florida.