GitHub

How I Got Into It

GitHub became necessary as soon as the work became real. Once code matters, once projects start changing over time, and once collaboration enters the picture, you need somewhere reliable for that history to live.

So for me GitHub was less of a novelty and more of a growing-up part of building.

The Learning Process

The difficult part was not the website itself. It was learning git well enough that I stopped feeling like I was moving files around with crossed fingers. Commits, branches, merges, pull requests, preserving history. That took some real repetition.

I still think that learning curve is healthy. It teaches respect for the work and for process without turning everything into ceremony.

How I Use It Now

GitHub is where I store code, track changes, collaborate, and connect projects to deployment. It sits right beside VS Code, and it is part of the normal flow into Vercel and the rest of my stack.

It also matters more now that Claude and Codex are part of how I build, because the value of AI help goes up when the underlying workflow stays organized.

What It Changed

It made my work feel safer and more legible. That is important when you are learning fast and changing a lot of things. You can move without feeling reckless.

It also gave me a better sense of continuity. Projects stop feeling disposable when there is history behind them.

Related

VS Code · Next.js · Node.js · Vercel · Claude and Codex