My Tech Pivot

One of the most interesting parts of my DevOps journey so far has been seeing the command line go from something intimidating to something I genuinely enjoy using.

At first, it felt unfamiliar. I knew it was important, but I did not yet understand how people could work so quickly in it. Every command felt like something I had to carefully think through.

Now that is starting to change.

The more time I spend in the terminal, the more natural it feels to navigate directories, create files, and organize projects. What once felt technical and awkward is beginning to feel practical and efficient.

A small example: with a single command I can create a parent directory and four subdirectories at once. Doing the same task with a mouse means opening windows, right-clicking, naming folders, and repeating the process several times. It may seem simple, but moments like that are showing me why the command line matters. It reduces friction and makes repeatable work faster.

I have also learned that becoming comfortable does not mean knowing every command from memory. It means understanding how to think through a problem, knowing where to look for help, and getting more confident through repetition. The terminal itself has become part of that learning process.

What I appreciate most is that I am no longer approaching the command line with hesitation. Instead, I am starting to see it as a tool that gives me more control over the system.

That feels important because DevOps is not only about learning individual commands. It is about building habits, understanding how systems work, and developing confidence with the tools that make automation possible.

A few weeks ago, the command line felt intimidating. Now it feels like the beginning of a very useful friendship.