Hello World: My First Year as a Developer
The first commit, the first bug, the first time I felt like I might actually belong in this profession.
The Beginning
My first professional commit was a one-line CSS fix on a legacy PHP application that I didn't fully understand. I spent forty-five minutes making the change, another thirty minutes figuring out how to push it to the staging branch, and the rest of the afternoon convinced I had broken something I hadn't found yet. The senior engineer who reviewed it approved it in under a minute with a single comment: "Looks good, ship it." That gap — between the weight I felt making the change and the casualness with which it was received — is the defining feeling of being a junior developer, and it doesn't fully go away until you've shipped enough changes to trust that the weight isn't proportional to the risk.
I came into the industry through a non-traditional path, which in 2019 still meant something. I had taught myself JavaScript through freeCodeCamp and a stack of borrowed books, built a handful of projects that nobody would ever use, and talked my way into a junior role at a company that built internal tools for the garments industry. The interview had gone well enough that they were willing to take a chance on me, and the first six months were a humbling reminder that building toy projects and building software that real businesses depend on are different activities entirely. The toy projects taught me syntax; the job taught me everything else.
Looking back, the most valuable thing about that first year wasn't the specific technologies I learned — it was the recalibration of what "good" looks like. In self-study, good means the code runs. In a professional setting, good means the code runs, is readable by someone who didn't write it, handles edge cases the requirements didn't mention, doesn't break existing functionality, and can be maintained by the person who inherits it after you leave. That bar is dramatically higher than "it works on my machine," and clearing it consistently is the real work of becoming a developer.
