My Tech Pivot

At the beginning of my course, the instructor gave us a warning: Do not over-customize your command line too early in the learning process, it will distract you and take you away from learning.

It sounded like solid advice. Unfortunately, I became the exact person that warning was meant for.

When we got to Vim and command-line customization, we learned about using Starship to make the terminal look cleaner and more informative. Being able to display file paths, GitHub information, and customize the entire prompt looked amazing. And that is when I made a mistake. Instead of simply setting it up and moving on, I went straight to the Starship website and started going through customization options one by one.

“Oh, that looks cool.”

“I should try that too.”

“Maybe I can make it even better.”

Before I knew it, what should have been a quick setup turned into a day-and-a-half rabbit hole of tweaking, testing, changing themes, and experimenting.

A day and a half. Time that could have been spent actually learning the material.

The funny thing is, the instructor warned us about this exact trap. And I walked right into it.

But honestly, it taught me an important lesson about learning tech, especially Linux and DevOps:

It is easy to confuse customizing your environment with making real progress. A beautiful terminal does not make you better at Linux. Fancy prompts do not make troubleshooting easier. An optimized setup does not replace hands-on practice.

The real growth comes from learning the fundamentals: commands, scripting, containers, networking, troubleshooting, and understanding why things work. There will always be time to personalize your setup later.

So if you are early in your Linux or DevOps journey, learn from my mistake:

Do not let customization become procrastination disguised as productivity.

Learn the skills first.

Then go back and make your terminal look cool.

Has anyone else fallen into the “I’ll just customize one thing real quick” trap? Because I definitely did