lots of musicposting!!! mostly rock and metal
whenever i write a program and i want to post about it here, i fear that i'm trespassing into a small group of Real Programmers who are more skilled than i am. what could possibly interest them about my scripts and apps?
i know it's nonsense, but the fear remains.
Speaking as someone who's been at this (professionally) for almost thirty years, we're all making it up as we go, so lean into the shame and ignore anybody who has a problem with it.
The big difference (for all of us) is that we generally only see other people's finished products, and not the day-to-day mess and struggle that it takes to get there, but our lived experiences are almost the opposite.
Yeah you should see the hot nonsense codetraption I cooked up this week. It mostly works after several iterations but has no error handling and deletes files without asking and uses multiple languages to achieve its goal. It’s a genuine cognitive hazard and I am a Respected Professional with twenty years of professional experience and people reporting to me and everything.
oh, that sounds cool! i'd like to see it, if that's okay with you.
my concerns are less about the "quality" of my code and more about its relative simplicity. my programs are fairly small and simple, and i don't know who'd be interested in my explanations of them.
i want to work on things that are more interesting and ambitious, and i'm figuring out how to do it.
Unfortunately it’s work-related so I can’t/shouldn’t share the code (even though there’s nothing “important” in there). But it’s some C# code that I wrote in LINQPad (because I’m most comfortable in C# these days), that runs Git commands to navigate a repository, runs additional commands to compile and launch a web app within that repository, and then launches k6 to run performance tests against the app. k6 itself is scripted using JavaScript to send JSON payloads, and it produces CSV output, which a different C# script parses to create a new, summary CSV.
The upshot is that I can launch this thing and leave it running for anywhere from fifteen minutes to 24 hours, and get a graph in Excel showing how our application performance has improved/degraded over time. Which is super useful, and gives us valuable information that we didn’t have before, but the code is a barely-functioning nightmare.
wait, did you get a notification for my reply to your comment's reply? i intended for it to reach both of you.
