i didn't like vibecoding my app and ended up with one db instead
i got fed up with being unable to export my daily calories from "lose it!", so i ended up making my own app. it was hilarious.
first, i wanted to vibe code an app since i just wanted to get something running fast. vibecoding quickly ended up being too messy, i felt that claude was making bloatware + going with this approach would make it impossible (or very difficult for me) to troubleshoot. it's easier to do things myself at this point.
i am not good with frontend, but who needs it? it's a small internal app anyway. so i decided to go with a small python app, literally just a backend with a database connection.
i was thinking of hosting it on my raspberry pi, then ssh'ing into it, and making a post request with food info.
then it dawned on me.
why have backend at all? isn't the only thing i want just a place to write down calories? so long story short, i have postgres running on my raspberry pi. this seems really funny, ending up with a simple database after having started from an idea of a beautiful frontend, nice backend, e2e / unit tests, a README... i suppose the initial idea had been more perfomative, i thought that it might look nice on my github. what i had really wanted though was basically a notepad with numbers and dates that i won't lose lol
i wonder if this is a common thing that happens with people who can / want to program? do people program things with frontend for themselves, or do they keep it as bare bones as possible? i wonder if such simple apps are now less common because of ai?
drew the little thing myself, it's an artistic interpretation of me thinking. i don't actually have pink hair in real life but this seemed fitting. i don't know why the resolution of the drawing is so low, but every time i try to polish my post i end up not posting anything so please enjoy my low-res drawing!