music-explorer VS FizzBuzzEnterpris

The article might describe a common scenario, but there are plenty of outliers. I hardly listen to music I liked in my teens and early twenties. I love discovering new music.

Many comments here are very insightful and discuss phenomena like high music diversity, music proliferation and easy of producing music, and automated recommendations.

One thing that has been occupying me is that curation is still harder than I'd like when using streaming tools like Spotify, YouTube Music, Apple Music, Tidal. Pandora had good roots with its music genome project, and have built on that. (I can't use it without a VPN since they discontinued supporting the country I mostly live in). It's probably a function of how I consume my music today - no longer desk-bound at work, but on the go, so iPhone (and Apple Watch) are primary tools. Being able to select/skip/preview/tune what I'm listening to is nowhere near as powerful as I'd like. I've written library curation tools in the past, these always expected me to spend significant dedicated time in front of a screen (e.g. a similar tool like the cool looking https://github.com/kristopolous/music-explorer, I think).

This has strong parallels to how older people consumed music - either totally passive curation (radio), or very deliberate (find music in record stores, at a friend's place, and/or select records/CDs in your own shelves). Today's ephemeral digital libraries are much lower effort, are huge and curation/selection tools are not easy enough to use, so I tend to fall back onto old favourites or recommendation engines that usually don't satisfy me.

A solution would be a much more configurable curation assistant that is also super easy to use (and, in my case) very accessible on a mobile device with 0-1 clicks (because I'm busy doing other things).

Might as well drop what I use for my music discovery, my fairly poorly documented hacker-friendly set of tools:

https://github.com/kristopolous/music-explorer/

I'm a big fan of not posix bit instead modern bash and to all the complainers about dash and ash, I say "tough cookies".

Sometimes I'll even use zsh

Here's some example of a modern tool I have written for a subject I call "music discovery"

https://github.com/kristopolous/music-explorer/tree/master/t...

You'll see many languages in there.

If you don't like my practice then I guess don't use it. I've been using/developing these particular tools nearly every day for over 3 years and it works well for me.

I'm not going to say bash is awesome but it's pretty great for programming.

I use zsh as my interactive though

Sure. Related. It's an art.

Here's some code I wrote earlier, probably a good example

https://github.com/kristopolous/music-explorer/blob/master/w...

It's self contained, not very big, not trying to be fancy, as direct as possible

> I'll answer your question with a question: Have you seen https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... ? :)

You can write that kind of crap in any language, including C++.

There’s a difference between complexity that’s inherent to the problem, and complexity that’s added by developers who have drunk architectural cool aid.

This is an example where all of the complexity is caused by rigid adherence to the most popular architectural patterns of about 10 years ago.

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

It looks completely ridiculous to modern eyes, but during peak OOP it was just how you should do it.

If you like simplicity then your fizz buzz implementation would be a few lines.

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris... isn't too far removed from some of what I've seen in big tech, especially architecture-wise. Certainly less costly absurdity.

What you need is Fizzbuzz, Enterprise Edition

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

It's been a decade since I used C# but the corporate design pattern culture of that language back then turned me off of it forever.

Everything looked like this: https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

Maybe it's better now but the Java/C# practice of shoveling largely empty classes around with an IDE isn't something I'd point to as a good example.

```

With your example I had to think for about 1-2 min before it made sense. If the codebase is full of clever stuff then I have to spend hours understanding all of the clever things before I can make changes. If everything is simple then it's easy to change.

If you want to see where overengineering leads you then take a look at this project. https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

It is satire but I have absolutely worked in places that write code like that.

Good programmers know that it's 10x times harder to read code than write it, so they deliberately keep it simple so that they can read it later.

I did something similar a 4 or so years back. I wrote something in a month (+ a couple of working with stakeholders to make sure it did what it should). I did it in a legacy tech stack that the architects didn't like, on the side of the main activity, as the deadline was coming close and some hireing processes were slow.

A team of around devs 5 (some coming and going) having been trying to solve the same problem since, but they're still not being close to finished.

In other words, the productivity is in the order 50x to 100x slower than when I did it. Rather, the main reason was that I knew how to write code like that, while they were set up to fail.

Basically, some architect was making all sorts of unnecessary demands for how to wite the code, and the programers were not familiar with much of the tech stack that was introduced.

Also, coding standards were really verbose, easily 10x-30x what I wrote, in lines of code. The current state of what they have look suspiciously like FizzBuzzEnterpriseEdition:

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

TLDR; Incompetent tech leadership prone to cargo-culting, can slow down productivity to virtually zero. In some cases, productivity can go up by ~100x if ignoring their demands.

I swear I've worked with people who if they were shown FizzBuzzEnterpriseEdition wouldn't be able to see the joke as that's how they naturally write all code.

https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

Reminds me of FizzBuzzEnterpriseEdition . https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

You never know when you might need to change the implementation of how the "Fuzz" string is returned, so you need a FuzzStringReturner.

And you never know when you might need multiple different ways of returning "Fuzz", so you need a FuzzStringReturnerFactory.

And that barely scratches the surface of what you need.