sounds easy, but never is

i keep getting caught up in the little things while i'm working. what is the best possible variable name, what name will be easy to guess in the future when i need to remember it and i don't want to scroll around looking, what name will make whoever reads this code understand exactly what the variable is used for just by seeing the variable name and no context.
bash scripting is very promising. but i am new at it. right now it probably makes me spend more time than i normally would to get a task done. i converted all the jpg files from some test runs into ppm files. that was easy enough. now i'm trying to have it work with my ppm analyzing program written in c.
i spent a lot of time not knowing why it does not work. i have narrowed down the problem quite a bit though. right now i'm fairly certain the problem is that the original jpgs have errors, so the converted ppms have errors, and my code assumes that the ppms will have no errors. but i spent a lot of time thinking it was the bash script and that something was wrong with it. eventually i found that there was a typo. a typo had me frustrated for literally hours. in that time i learned a better way to do a directory listing.

i just remembered i need to get to campus. bye.