I Learned the Terminal and the Code at the Same Time

A year ago, the terminal looked like a place where one wrong command could ruin an entire computer. Now it is where I begin whenever I need to move a website out of the system where I built it, open the files on my computer, run the site privately, and prepare the approved version for Vercel.

That change did not begin with learning how to code first and adding the terminal later. A friend taught me the terminal, the code, and the publication process at the same time, while giving me enough room to ask the same questions repeatedly until I understood how the pieces connected.

I learned how to pull the files onto my computer, run the site privately, review my changes, and send an approved version through to Vercel. None of those steps made sense in isolation, so he walked me through the entire sequence while I stopped him whenever I lost the thread, usually while hopping from one location to another.

I was a total non-coder

And no, I do not mean rusty, or returning to HTML after using it on MySpace and Tumblr.

I understood businesses, operations, clients, and the quiet failures that become expensive after nobody addresses them. I had also spent years in fashion production, where a missed approval, an unchecked measurement, or a delayed factory response can affect an entire delivery. I've been on enough 3 am phone calls to stress about deadlines before a project even begins.

That background trained me to watch the details, but I still did not understand how a website or CRM system moved from a platform, onto my computer, and then onto the internet under my control, or at all to be honest. Now I've successfully built multiple versions of both of those things without pulling my hair out in the process.

The terminal, with its black screen and blinking cursor, looked like a room where everyone else knew the dress code. And generally reminded me of the POS systems still so commonly seen in my previous industry.

The sequence was the lesson

My friend taught me the commands, the code, and the technical vocabulary together, then let me interrupt him, repeat the process, and ask the same questions as many times as I needed.

I was not learning isolated instructions. I was learning how the website moved through an entire system, what each step changed, and where I needed to stop and verify the work before continuing.

That sequence made sense to me because it followed the same discipline I had learned in fashion.

You do not approve bulk production from a sketch, and you do not send a website live because the edit looked correct in one browser window or in an AI system. You review the sample, check the construction, confirm the measurements, and address the problems before approving production.

A website deserves the same level of attention.

This is the first of three pieces. The next one covers the sequence itself: how a website arrives on my computer, how I run it privately, and how the approved version reaches the internet.