Wrong. The most important part of shell scripting is having fun

Bash scripting is such a great life skill. I helped a normie friend to clean up the tags of his mp3 collection. He spent hours getting nowhere. I wrote a script and finished the job in 15 minutes. He looked at me like I performed some kind of voodoo magic XD

Do you have a Discord, IRC, or similar community messaging platform? I really like your style and community. It's refreshing to see someone that doesn't pander or dumb things down for non-techies, but just makes content authentically. Cheers, we appreciate the effort you put in.

Love shell scripts. Though watching yours I feel like a total n00b. And I’ve been using Linux for a while now. (And MacOS which has a BSD component to it.)

I actually blew the mind of one of our IT directors because me, the girl who directs the news, wrote a shell script to bulk resize a bunch of images on our broadcast automation system. (The tl;dr was that large size images on the icons were causing it to crash. Everything had to be the precise size the manufacturer wanted them to be.)

I feel like Bread can read my mind sometimes. I have been looking into shell scripting to automate a bunch of stuff for me and she drops a video on shell scripting.

instead of killall ffmpeg, I would put kill $(cat /tmp/guitarpid), so it would only kill the ffmpeg for the recording. Otherwise you would be killing all ffmpegs, like, let's say, a background transcoding process of jellyfin or yt-dlp for youtube.

Nice vid as usual!
A few ideas for improvements:
- As already noted in other commands, in script 1 `killall ffmpeg` seems a bit dangerous as it might kill long-running ffmpeg processes that are not related to this script
- I think your `&& exit 0` in top-level logic of script 1is not needed here: any command run after an `&&` will only run if the return code of the previous is 0, in which case you then make it explicitly return 0 one more time. Also if you didn't know, I believe in this case since the `exit` is run within a subshell (a command in parentheses), it will not exit the script, but only the subshell, so would really not do anything in the case of the first script. You could say it makes it more explicit that you're exiting, so it could also be a matter of preference.

So darn cool, most of my shell scripts are related to bulk installation for apps after a system rebuild. Rare but still saves time. Added to that, replacing fstab and .bash_aliases. Your file management tools are awesome!

If you're going to loop over the positional arguments, you can just do `for f; do`

You very easily have become my favorite tech tuber; you explain very intricate things in incredible detail and in ways that are comprehensively understandable

As always: incredible work!

Maybe a small suggestion about script 2: you could use number formatting when printing "i" variable. Something like $(printf "%02d" i).
Simply because file browsers tend to sort like this: file1,file10,file2,file3,file4,... Adding a leading 0 will solve the problem. You'll have to add 2 leading zeroes when dealing with more than 99 files, etc... you get the idea :)

i really loved this, one thing i had in mind was instead of writing a file for the pid use exec -a, then later kill it via the name you set

edit seems i slightly misunderstood, however even in retrospect i think i personally would use the method i suggested because then if you happen to have 2 instances of ffmpeg for different purposes you can just kill the one you want to without having to worry about the 2nd

I learned so much from the first script alone x)

Your videos are great and I’m learning a lot from them. Also, your teaching style is excellent.

These are gems for anyone in the cloud eng industry aswell: Thanks!

Love this channel already

i love bash scripts!

Your last vid helped me fix my arch system after getting a kernel panic. Thanks. Never trying to display ascii art during boot ever again.

Let's goo!

The fact that i barely understand 😂 makes it even more interesting