VaultCLI

Inspiration ​I got tired of just following step-by-step coding tutorials where everything is just a flat script. I wanted to see if I could build a strict, logic-driven system from scratch. Managing real-world stuff—like a library's books—means you need memory that doesn't leak or mix up. So, I decided to drop the training wheels and try architecting a pure Object-Oriented Programming (OOP) system to handle the data dynamically. ​What it does ​VaultCLI is a Command Line Interface (CLI) tool. You run it in the terminal, and it lets you manage a library's inventory in real-time. You can check what books are available, borrow them, and return them. I also added some custom developer humor for the error handling—if you try to borrow a book that doesn't exist, the system literally tells you to go touch grass instead of just crashing. ​How we built it ​I coded the entire backend in pure Python, zero external imports. I created a custom Library class that acts as the blueprint. That class holds the inventory lists and the functions for borrowing and returning. By using the self parameter, the state of the library updates live in the system's RAM. To make it interactive, I wrapped the whole thing in a while True loop so the terminal session stays open until you choose to exit. ​Challenges we ran into ​The biggest headache was what I call the "Double Input Bug." At first, I put the input() prompts directly inside my class functions. It caused the main loop and the class to fight each other, meaning the user had to type the book name twice. I had to completely restructure the code to keep the Class as a silent processing engine, while the outside while loop handled all the actual chatting with the user. ​Accomplishments that we're proud of ​Honestly, just escaping tutorial hell. Building a working state engine in a raw terminal feels like a massive win. Getting the init constructor to work right made me realize that with this architecture, I could technically spin up a hundred different library databases at the exact same time without their data crossing over. ​What we learned ​OOP is a massive shift from normal top-to-bottom coding. I learned how to use the DRY principle (Don't Repeat Yourself), how to slice and append lists, and realized that figuring out why a program is still running in the terminal memory is basically half the job. ​What's next for VaultCLI ​The next big step is wiring it up to a real database (like SQLite) or adding File I/O so the inventory actually saves to the hard drive when you close the app. Once the storage is permanent, I want to turn the Python engine into an API and hook it up to a real web frontend.

Built With

• python