I spent six months writing code that I thought was good. My process: Build a feature Test it locally Ship it to production Move on to the next feature What I never did: Get feedback on the quality of my code. The result: I got very good at writing bad code quickly. Then my company hired Elena, a senior engineer. Her first week, she instituted a new rule: “No code gets merged without a code review from someone senior.” ...
For six months, I wrote every SQL query like this: SELECT * FROM users WHERE id = 123; SELECT star. Get all the columns. Always. My reasoning: “I might need all the data. Better to have it than query again.” This worked fine for my bootcamp projects. Tables had 5 columns. Performance didn’t matter. Then I joined a company with real production data. My first code review: Senior Engineer: “Why are you selecting all columns?” ...
I spent my first year as a developer learning from the wrong people. Not bad people. Just the wrong people for where I was and where I wanted to go. My learning sources: YouTube tutorials from people who’d been coding for 6 months Reddit advice from anonymous strangers A bootcamp instructor who’d switched careers 18 months prior Other junior developers at my skill level What I learned: How to copy-paste solutions. How to feel productive while making minimal progress. How to stay stuck in tutorial hell. ...
Shane gets therapy. He stops drinking (mostly). He finds joy in chickens. He becomes, gradually, a person managing his depression instead of drowning in it. You helped. Your friendship mattered. But here’s the critical detail: You didn’t fix him. You were part of his support system. He did the work. And Emily? She’s on her own spiritual journey. Deepening her practice. Exploring crystals and meditation. Growing. Whether you befriend her or not. ...