So here is my question, or one of them, as someone starting this whole journey: exactly what metadata do you want outside of artist, song title, album title? Because I can see there's a lot to be had. Embedded album covers, subgenre tagging, synchronized lyrics ... hyperlinks to Discogs and MusicBrainz, maybe? Tempo in BPM? Key?

ID3v2.3 or IDv2.4? Can you even do that to FLAC? And where do you get that metadata, using what tools?

I just don't want to be the guy who has to re-rip three thousand CDs because he did his workflow in a lazy or careless manner.

The cool thing about MusicBrainz Picard is that it puts not only an ISRC metadata tag on each file, but also a UUID for the MusicBrainz recording and for the MusicBrainz album id.

The idea here is that if you use something like MusicBrainz, you can actually retag all of your files in bulk if necessary because MusicBrainz Picard knows exactly what release each file belongs to. You can then configure MusicBrainz Picard to tag your files to your liking. It's a really great piece of software.

If you are tagging files manually, I think an ISRC tag is the bare minimum because it can allowed automations like MusicBrainz Picard to easily identify what each file is.

As for what version of ID3 or ID2, I'm not sure. It might depend on the software you use to play the audio files. The reason I personally use MusicBrainz Picard is because its MusicBrainz specific metadata is read directly by Plex, so even if the other metadata on the file is bad for some reason, Plex will match the MusicBrainz tagging with the correct release. I mean, Plex uses MusicBrainz internally for its metadata, so it's a safe bet for my purposes.

Besides artist, title, and album, I also make sure to include release year and genre (and I'm not really particular about genre definitions - about 90% of my music falls under "rock," "pop," "jazz," or "soundtrack"). I add album art, too. I started digitizing my collection 15 years ago, ripping from CDs and cassettes, and have never regretted not adding any more metadata.

I believe that this is a technical issue now. In a more ideal world, procedure, legislation, regulation, protocols would be followed to slow the growth of antibiotic resistance, but there are just too many Defectors for that approach.

It's in nerd hands now ...

I agree and will add in a few bits: although I will obey the language's idiom, in general, I like to keep the number of "things it does" per line of code to the minimum. Kind of an anti-code golf.

I also document (or comment code) when I am waiting for the flow to kick in. For me, the documentation starts at the appendices. One for input files or api source tricks or describing the input tables in a database. Another for the relevant outputs. Maybe a "justify overall design decisions" section. Just stuff someone would wish if they had to handle it in five years.

I wonder why people boast they can do ten things in one line. Less lines of code doesn't mean less bugs. The debugger just stops at each symbol instead of each line which I think adds to the cognitive load.

Documenting while waiting for the flow is like stretching before exercise. It gets you to that place :)

I got my experience/slaps by fixing my own code in the same codebase for more than ten years. I have empathy for the future maintainers :)

Multiple visualizations. A seed, a sprout, a tree. A baby, a child, an adult, an elder. And so on.

I am still a fan of vitrification and dumping the end results along the subduction zone of a tectonic plate, myself.

I was once given this ridiculously short deadline to provide a full project. "We're going to be Agile and run this through Agile processes." I hadn't met the stakeholders yet (I would in fact not meet them at all) or even seen requirements. "How soon can you show me something?" I eventually had to pull out the "How fast does ten percent of a Porche run?" question.

Nobody ever wants a prototype. They think they do, the prototype mysteriously has to have all of its features and so on. And then they'll attempt to shove it into production right then and there.

I finished it by the deadline, despite having the flu and a blowing a non-trivial portion of the allowed time on a work trip that wasn't even relevant to my job, one I hadn't wanted to go on.

And then it sat on a shelf, unlooked at by anyone, for seven months. A lot of goodwill was burned up on that move. Fake deadlines mean to me that the person setting the deadlines does not understand urgency, when anything is actually needed, how to prioritize, or anything. It's a big sign that says I Am Not a Good Manager.

I would say that, on balance, one must prove DNA to be not-junk.

The idea that you can have DNA of some critter and there aren't some errors, unused bits, and so on, after what must be trillions of copies, well, I would find it statistically unlikely. Like saying you have a program with millions of lines of code and it is completely error-free.

Oh, ultrasonics can definitely harm flesh if focused. Yes, I am the guy who tested it with a room humidifier. I knew it would hurt, I did it anyway.

Thanks for your contribution to science. On a related topic, I guess there are more than 1 person that tried looking directly into a laser, though. And multiple times.

I used to do a great deal of local mapwork. Google Maps tends to not do rural areas as well as urban or suburban areas, usually missing the existence of Road A and then assigning the name of Road A to Road B, that kind of thing.

The naive approach is to expect a Single Source of Truth for roads, address points, and the like, but this turns out not to be true. The road network and address points are usually done on a per-county basis, each with its own standards (and boundaries), and gods help you if you expect that a road in County A that proceeds to County B to "line up" if you import data from each county. Sometimes, parcels are separate. Oh, and they'll use different projections and fields and whatnot.

Meanwhile, the Department of Transportation for my state had its own road network: fewer fields, often skipping the tiny roads entirely, irregularly updated.

This doesn't even begin to cover how bad the plats of a new neighborhood are versus reality, how infrequently updated and checked data is, height and weight limits for stretches of bridge and so forth.

I recently saw one painted primer black and immediately felt like going home so I could watch Johnny Mnemonic.

It appears to be a triumph of aesthetic over function, needing only EL-wire underlighting to look like it escaped from the Tron storyboards and into low-poly life. I could only wonder if the entertainment system comes with a hidden Sirius/XM channel that only plays vaporwave music.

Man. Johnny Mnemonic. I get the urge to rewatch that movie once every three of for years, and I'm reminded of it's awful greatness. Like Hackers.

Need more William Gibson movies. I'm incredibly disappointed that The Peripheral was cancelled.

I set the ambient light in mine to neon purple and play a synthwave playlist. Definitely a fun mood to drive with on dark city streets.

That honestly sounds amazing. If I win the lottery, my first purchase will be a flat black CT with EL-wire to bump the Tron soundtrack.

Then you could replace the LLM with a much cheaper RNG and let it guess until the "bad math filter" let something through.

I was once asked by one of the Clueless Admin types if we couldn't just "fix" various sites such that people couldn't input anything wrong. Same principle.