Why I’m Writing Junior to Engineer

Hi, I’m Hélène. I’ve had computers in my life for more than forty years now, which still surprises me when I say it out loud. I started out as an eight-year-old kid playing simple games on a family computer, before the NES, before “PC gaming” was really a thing. We loaded games from cassette tapes, listened to modems sing their weird little songs, and waited for desktop machines to slowly grind their way through a boot sequence. I taught myself to program as a teenager because I wanted to make the computer do more than just play those games. Later, I went through technical school, then university, and graduated with a Computer Science degree. I did a Master-level short program in project management. I worked as a software developer for years, and now I lead a team. Along the way I read piles of books, watched improv and theatre, devoured Choose Your Own Adventure stories — only to realize much later that all of that was quiet leadership training in disguise. But there was one book I never found: the one that explained how to grow from junior to a trusted, impactful developer in a way that felt honest and practical. Not just “write clean code” or “communicate better,” but how to actually do those things, day after day, with real people, real constraints, and real doubts in your head. When I started my career, there were textbooks on algorithms and operating systems. There were tutorials on whatever language was hot that year. There were business books full of buzzwords. What I couldn’t find was the in-between book: something written by a practicing software developer, talking to another developer, about the messy, human parts of this job. Junior to Engineer is my attempt to write that missing book. Who this book is for If you’re a junior or intermediate software developer and you’re wondering things like: “How do I become the person people trust with the hard problems?” “What should I actually focus on in the first 5–10 years of my career?” “Why does everyone else seem to have it figured out when I feel like I’m guessing?” then this book is for you. You don’t need a particular tech stack. You don’t need to work at a famous company. You just need to care about getting better at the craft and the human side of software. What this book is not This is not a coding tutorial. I won’t teach you a new language or framework. It’s also not a textbook. There are no formal proofs, no end-of-chapter quizzes, and no “one true way” to do anything. Instead, you’ll find stories, patterns, questions to ask yourself, and practical tools you can take into your next one-on-one, code review, or planning meeting. What to expect from Book Sprint Updates This category, Book Sprint Updates, is where I’ll share real-time notes as I write Junior to Engineer. You’ll see what I’m working on, what I’m wrestling with, and sometimes early drafts or half-formed ideas. Think of it as sitting next to me while I write, with permission to look over my shoulder. My hope is that by writing this in the open, I can make the book more useful to you — and maybe reassure you that nobody’s career path is a straight line, not even after forty years of loving computers.