Status Updates From Bash Cookbook: Solutions an...

I just got done reading it for a bit as a pdf on my desktop.

I'm on section 7.16, they are about to go over how to Show data as a quick and easy histogram.

I feel the same way I did the last time I read this, I feel like the majority of this stuff is way over my head. I'm debating how necessary this is for my career goals, I mainly am focused on blockchain development and web development.

I'm on section 7.14, he is talking about how to count string variables with awk.

I a lot of the information feels way above my head, I'm still taking the scraps that I can.

It feels like I'm in a video game, and I came upon an enemy that is higher level than me, so I just keep kiting and trying to chip away abt them bit by bit.

I did learn that

echo *

the command is basically the same as

ls

I just got done reading the pdf for 30 minutes on my laptop.

He is explaining how to create a command line calculator now.

I'm in section 6.9, he is talking about Changing Behaviors with Redirectories

Honestly, I'm lost and confused. I am taking notes on the few things that I do understand.

I'm in section 5.22 where he is talking about Using Alternate Values for Comma Separated Values

I'm on section 5.7, he is writing about how to use parameters in shell scripts.

I'm on Chapter 5, he is explaining why you shouldn't leave spaces around = signs when using a variable and why you shouldn't name variables with = signs.

If you put spaces around the = sign bash will have a hard time distinguishing if it is a command or a variable you are trying to use. It's the same thing when making the file name.

I don't understand everything that I'm reading and doing but I do take what I can.

I'm on chapter 5, he is now explaining why we shouldn't put spaces around = signs for variables, and why variables shouldn't have = signs in their name.

If you put spaces around the = sign when using a variable bash will have a hard time distinguishing if it is a command or if it is a variable.

I don't understand everything that the book is saying but I do pick up on a few things here and there. I

I'm on page 80

Section 4.2 where he is talking about Running Several Commands in Sequence

I just got done reading it for 30 minutes, I am on page 51.

He is going over how to input and output things in bash.

I'm at the part where he is going over the echo command and how to save a command.

I'm on page 13

I'm reading it as a pdf while I have bash overlayed on it transparently.

He just was going over

ls

options

I just got done reading the preface, I have it on pdf and I'm reading it on my laptop. I think it will be easier since I could overlay my transparent bash terminal window on it to copy the commands and scripts easily. I was going to get the physical copy, yet I was blessed with someone sending me a humble bundle package on LinkedIn and it had this book inside it!