Improve your software development workflow by adding these five CLI tools to your toolbox.

The New Stack is a publication covering trends and technologies in cloud-native development, DevOps, and software delivery. Developers can learn about containerization, Kubernetes, and cloud computing, as well as explore topics such as microservices architecture, serverless computing, and continuous integration/continuous delivery (CI/CD) pipelines.

The New Stack

Discover five essential command-line tools to boost your productivity: SDKMAN for managing multiple SDKs, eza for an enhanced ls experience, ffmpeg for comprehensive audio and video processing, pueue for managing long-running tasks, and find for efficient file searching and processing. Learn how to install and use each tool with practical examples.

My 5 Favorite Command Line Tools

Finally some commands I didn’t know about. 
(usually such post are very basic, but not here)
Regarding the <code>find</code> command, I think using the <code>-delete</code> flag to delete files is more effective.

I missed eza, very nice (sdkman a must have!)

It’s an interesting enough article, but I kind of miss the point of <code>pueue</code>. In the example given, is that essentially equivalent to doing something like: <code>ffmpeg -i ./AtlantaTimeLapse.mp4 -vf scale=-1:480 -c:v libx264 -crf 0 -preset veryslow -c:a copy AtlantaTimeLapse-480.mp4 &amp;&amp; find . -type f -name &quot;*480p*&quot; -exec mv {} finished/</code>? You could also use <code>;</code> instead of <code>&amp;&amp;</code>, if you want the second command to run, even if the first one fails.
I suppose the idea is that <code>pueue</code> would (presumably?) allow you to continue typing in terminal, but…couldn’t you just do <code>ctrl + shift + n</code> and do something else while it processes? It seems a bit much to install additional programs over what’s already there. Again, I might be missing something though, I haven’t used that specific program.
Also, regarding <code>find</code>, personally I would recommend using <code>-iname</code> over <code>-name</code>. I frequently find myself looking for a partial file name, but don’t want to be concerned about the case it’s in, so I will put in something like this: <code>find . -iname '*some-text*.pdf'</code>