2024 development journey

LOG 202412301721 #log

so i posted the recap yesterday, which was honestly too many words, but also barely scratching the surface of each project. it really wasn't satisfying to publish, and like a lot of the things i've put out on the internet, i want to delete it.

i'm going to resist, in the wise words of jon gold; don't let your fear of sounding stupid on the internet prevent you from publishing, or something along those lines. i remember i wrote that quote on a previous personal site that i deleted years ago.

this time i'm planning the hold the line. i've been getting better at building stuff a lot faster than i have at documenting it all. i want to get comfortable building in public. and that isn't going to change unless i practice.

i've said this all before.

i want to spend more time thinking about how i break that barrier down because, despite having a background in marketing, my online identity is intentionally absent. i've kept my personal and professional identities separate for so long that i don't know how to start blurring the lines.

anyways, i went on a long tangent there. this post was supposed to be about how after finishing writing the recap post, which featured a 2024 development journey app, because figuring out how many lines of code you wrote isn't something github has sitting in a dashboard somewhere, and claude wanted me to run a script, and at this point if you're going to run a script once, it only takes a little extra time to wrap it in a nice ui and make it re-usable.

so one thing led to another and we built a whole thing and it's pretty cool.

well, so long as you're cool with dox'ing your private repository names, language breakdowns, and commit activity to the world. i didn't actually deploy this because i don't trust mean peoples on the internet who could in theory nuke all my hard work.

one day, hopefully not after that happens, i'll be comfortable enough building secure applications that we can deploy publicly. until then, the next step for this is to wrap in a static site generator, and just pull all the api data during the build, as of midnight tomorrow none of this will be changing anyway.

then i'll fork to the 2025 version and continue building a realtime dashboard and dig into all the fun git analysis and visualization stuff i've got kicking around with claude. should be a good time.

not sure what comes next on log, have a bunch of stuff cooking at work that i need to ship so i may just chill and enjoy the ringing in of the new year after work this week.

hny 🎉