Why Looping over files and directories in Bash Scripting? - Purpose & Use Cases

The Big Idea

What if you could tell your computer to handle hundreds of files for you in seconds?

The Scenario

Imagine you have a folder full of hundreds of photos, documents, or logs. You need to rename, move, or check each file one by one by opening them manually.

The Problem

Doing this by hand is slow and boring. You might miss some files or make mistakes. It's like trying to count grains of sand one by one -- it takes forever and is easy to mess up.

The Solution

Looping over files and directories lets your script automatically visit each file, one after another. It's like having a helper who quickly and carefully checks every item for you without missing any.

Before vs After

✗ Before

mv photo1.jpg new_folder/
mv photo2.jpg new_folder/
mv photo3.jpg new_folder/

✓ After

for file in *.jpg; do
  mv "$file" new_folder/
done

What It Enables

It lets you handle many files quickly and safely, saving time and avoiding errors.

Real Life Example

Say you want to resize all images in a folder for a website. Looping lets you apply the resize command to every image automatically, instead of opening and editing each one.

Key Takeaways

Manual file handling is slow and error-prone.

Looping automates repetitive tasks over many files.

This saves time and reduces mistakes in file management.