Reflecting: mapping cli commands to outcomes

This is a quick blog post to reflect on yesterdays blog post on custom commands because this has been life changing for me. 

Mapping an output to a cli command logically in my head was like a missing step for me. It was like a missing piece in my puzzle

Because suddenly I can see that I need to view the whole of the codebase in that way as well. Every line or lines of code has a desired output and a desired outcome. 

And it all makes sense.

Why it all makes sense 

I am bursting and exploding with gratitude for my former line manager who wrote this all out for me just before he left. Everything is all making sense

And combined with my git course this is supercharged. This is superpowered. This morning I checked out a new branch. And even my git course had made me more aware of my branch. This was good cos I had been on the wrong one. So I checked out a new branch and went

• This command is makeing a copy of all of the files and Folders as they are right now
• This branch name will allow me to see all of the copies of the files and folders as they are at any given time
• Every time I commit to this branch a new version of these files and folders gets updated and created
• If I for some reason want to revert back to a former version of this branch or to see a certain revised bit of it at once then these commits allow me to do that

I just want to add. Today I was working with some pretty big make commands. And I forced myself to read inside of the big huge make commands. And I could see so much more of what they were doing. I don’t understand them fully but I would like to know and understand more of them please thanks

I would like to understand more of the language they are written in

What is it called?