music-explorer VS bash-modules

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

Bash is turing-complete, so it's possible to write automated test cases in bash. Example: https://github.com/vlisivka/bash-modules/blob/master/bash-mo...

Template in article is awful. It's better to use this one, which is a real CLI tool: https://github.com/vlisivka/bash-modules/blob/master/bash-mo...

IMHO, you are mixing TODO lists and task management/planning software. No, I don't know a good task manager or business process manager for command line. Instead, I created a simpler TODO list manager, called `td`[0], which supports flat TODO lists only, and use directories and command-line generators to manage todo's. `td` prints top item only, by default, leaving little room for procrastination. I'm keeping one `TODO.md` file per project instead of one large TODO file for all todo's.

[0]: https://github.com/vlisivka/bash-modules/blob/master/bash-mo...

Documentation: http://vlisivka.github.io/bash-modules/ Project home page: https://github.com/vlisivka/bash-modules

I'm preparing to release bash-modules 4.0 [0]. Can you give me feedback, please? I'm a non-native English speaker, so I need someone to help fix spelling mistakes, at least.

https://github.com/vlisivka/bash-modules

It works in my shell. :-/ It looks like you forgot to insert `false` command.

You are pointing to the problem with -e not working in subshell/deep functions, because of POSIX. Right? It's described in bash documentation: http://www.gnu.org/software/bash/manual/html_node/The-Set-Bu...

> I think just defining a die() function and using it after any command that must succeed is more verbose, but less error prone:

Yep. It's the style I developed 12 years ago, when working at Bazaarvoice, when I was lead of devops team. I created the whole library for bash, to use this pattern consistently. See https://github.com/vlisivka/bash-modules#error-handling