What made it interesting
Most school projects hardcode one form per table. This one reads the schema on boot and builds the UI from columns and types. Adding a bus-routes table meant updating SQL: the nav and forms appeared without new Tkinter code.
Caveats (on purpose)
Early project: string-built SQL in places, pickle session file, desktop-only. Treat it as a pattern demo (runtime UI from schema), not a production admin.
What it demonstrates
- Preferring data-driven UI over copy-paste screens
- How far a small introspection loop can go for CRUD
- Knowing which corners were cut and why they mattered later