It's hard getting something that sounds consistently good in all listening environments - I've seen cases where music is offered in digital format either as 'play anywhere' loud .mp3s or 24-bit high dynamic-range .flacs for DJs, but most commercial music is mastered for the poorest environments (in the car, over the radio).
Getting a good master is very important - I'm reminded of a story I heard about an album that was mastered by the artist, and pressed to CD with a high-pitched whine over the top which the artist hadn't been able to hear - like Aphex Twin's Ventolin, but unintentional.
Yes - Go is full of concepts like 'aji' (lit. "taste"), thickness, influence, good and bad shape which are features that can only really be evaluated in terms of actual points dozens of moves later.
I think Go is particularly difficult for AI because you need fuzzy pattern matching and precise reading out of positions (life and death problems). as well as the judgement to know when to use which.
I think it's about mindset not skillset - games like these are about solving local problems ('tactics') to achieve a greater aim ('strategy'); people who are attracted to them are generally people who like the sort of problem solving that comes up in programming, hence the cross-over.
Your question, however was whether or not the skills translate - I don't think that solving daily chess problems or tsumego will do as much for your programming than solving programming puzzles (e.g. codewars), but the discipline of thinking through all possible paths ('reading') definitely helps.
I got some very interesting results from feeding fractal images into a program like this a few years back - unfortunately, I don't have the resulting sounds, but you pick less busy images with filaments, and adjust the contrast - the result is very organic. Must have a go with this ...
Do you really need to debug events from 3 and half years ago?
Full logs only really need to stick around as long as you're likely to want to debug them. Log rotation is a must (I've seen debug logs nobody reads sitting in the gigabytes ...)
Past that, you can cherry pick and store metadata about the events (e.g. X hits from userAgent Y on this day) with enough information you'll need to do trend analysis, although it's generally a good idea to keep backups of old full logs in case you need to reload the logs to find out that one thing you forgot to add to your metadata ...
If you do genuinely need all of the data back that far, you should look at partitioning the data so you're not indexing over millions of rows - how you do that depends how you're intending on using the data.
$ converge in.png -negate out.png