Three months after finishing my first programming course, the edu center invited a small group of us — the ones who'd finished strong — to a free, one-month intensive. I assumed it would be more advanced coding. It wasn't.
The Real Curriculum
The mentor's first lesson had nothing to do with code: a real developer doesn't just write functions, they organize, lead, and communicate. We learned BPMN — business process modeling — and spent real time understanding how businesses actually operate before ever touching a keyboard. It was uncomfortable at first. I wanted to build, not diagram workflows.
Why the Discomfort Was the Point
Halfway through, we split into two teams to build the same project independently. I ended up leading a five-person team, most of them older than me, because my backend skills were strongest in the group. Suddenly BPMN and planning weren't abstract — they were the only reason a team of five different skill levels could ship the same thing on the same deadline as another team doing it their own way.
The Lesson That Stuck
Both teams finished. I was 15. What stayed with me wasn't the project itself, but the reframe: code is the output, not the job. The job is making sure a group of people with different skills and different ideas end up building the same thing, on time, without anyone getting stuck. I've carried that into every team I've led since.