A letter to every developer starting out: it’s fine not to know, your hands learn slower than your head, choose people over perks, keep your promises and keep learning. One day you will be the one standing beside the bench.
Every Way to Learn, and Which One Fits You
There is no single best way to learn a technical craft. Courses, books, reading code, pairing, building, teaching and AI tutors each do one job well. Here is every way to learn, what each is good for and how to choose the one that fits you.
Employee Training Is a Promise Both Sides Keep
Employee training is a promise with two sides. The employer promises time, guidance and room to grow. The developer promises attention, effort and honesty, even on the way out. Here is what each side owes, and why keeping it matters.
Developer Training: The Day School Ends and Learning Begins
Developer training starts the day school ends. A degree opens the workshop door, but the craft is learned at the bench, with real code, real mistakes and someone beside you. Here is why companies and developers should both care.
Give It Away: Why Sharing What You Know Makes You Better
Sharing what you know does not empty you. Like a village well, knowledge fills faster the more people draw from it. A year of publishing every day taught me why giving it away makes the giver better.
Learning from People: Conferences, Meetups and Mentors
Learning from people is how a craft travels. Conferences, local meetups and mentors teach what no course can: questions, mistakes and the hallway conversations between sessions. Here is how to get real value from each one.
How to Give a Technical Demo That Doesn’t Break
A Technical Demo fails for a few predictable reasons, and most of them can be fixed before you start. This guide covers rehearsing on the exact machine, numbered scripts with a reset file, readable screens, an early room check, a recorded backup and what to say when something breaks live.







