Learning How to Code
Learning How to Code
When I started learning how to code, I had no technical background at all. That is one reason I remember the process so clearly. It did not feel like moving naturally from one existing strength into another. It felt like walking into a language I did not speak and staying there long enough for things to slowly become less intimidating.
Most of that early learning came through long YouTube tutorials. I spent a lot of time pausing, replaying, testing things, and trying to understand what each part was doing instead of memorizing a surface pattern. HTML/CSS was one of the first doors in, then JavaScript, and later frameworks like Next.js. The only way any of it began to feel real was by building things, even when I only half understood them at first.
I also remember the physical side of it, which people usually leave out. Sitting for too long hurt. My body felt it. There were days when the learning process was not only mentally heavy but physically unpleasant. That matters because I do not like rewriting difficulty into something cinematic. A lot of serious learning is awkward, repetitive, and uncomfortable before it starts feeling rewarding.
The AI era changed the experience too. Coding became more accessible once tools like Claude and Codex could help explain, debug, and unblock things that would have stalled me much longer before. That did not remove the need to think, but it made the path less closed.
What changed most was my relationship to technical work. It stopped feeling like a foreign world reserved for other people. It became something I could enter, struggle with, and slowly make part of my own range.