BLUF: 20 years a Chief, 1 week a junior. What my first week as a developer actually taught me

BLUF: My first week as a junior developer at 42 was humbling, a little embarrassing, and the best career decision I ever made. A year and change later, here's what I wish someone had told me. Long post, grab coffee.

Background for the new folks. Born in Olongapo, joined the US Navy at 18, retired as an IT Chief after twenty years. I ran networks on ships, I ran sailors, I ran a division. Then I did a 16-week bootcamp at 42 and got hired as a junior full stack dev at a defense contractor in San Diego. React, Node, Postgres.

Day 1: Nobody salutes a junior

For twenty years when I walked into a space, people knew who I was. Day 1 at the new job, I couldn't figure out the badge reader, I didn't have repo access, and my team lead was 29. Good guy. Sharp. Younger than some of my old sailors. I'll be honest, the ego took a hit. By lunch I had a talk with myself in the parking lot: you chose this, Chief. Now be a good junior.

Day 2: "Ask more questions"

In the Navy, a Chief who asks too many questions looks like he doesn't know his job. So on day 2 I spent four hours stuck on why my local Postgres wouldn't connect before I asked anybody. Port conflict, I had a second Postgres still running from bootcamp. My lead fixed it in ninety seconds and told me something I've repeated to every career changer since: "Rule here is fifteen minutes. If you're stuck for fifteen minutes, ask. You're not bothering me. You're costing us." Same lesson as Walt's Dolores post on here, by the way. Calling for help early is arithmetic.

Day 3: My first PR got 23 comments

Twenty-three. On a forty-line change. Naming, a missing test, an unhandled promise, a "why is this a class". I took it personal for about an hour. Then I realized: this is just an inspection. We did inspections in the Navy constantly. Nobody took a zone inspection personally, you fixed the discrepancies and passed the reinspection. So I fixed all 23 and the second round had 2. Code review is a zone inspection for your code. Once I framed it that way, I started looking forward to it.

Day 4: What I actually brought

Thursday we had an incident. Prod API throwing 502s, and the room got loud. I've been in rooms where things were actually on fire. I said, calmly, "Who has the lead? Okay. One person on comms, one on logs, one on the last deploy." People just... did it. My lead told me afterward that was the most useful thing anyone did in that incident. I didn't know any of the code. I knew how to run a room.

Career changers, hear me: you are not starting from zero. You're starting from zero on the tech. Everything else comes with you.

Day 5: Friday

Merged my first real PR. A date formatting bug in a report. Tiny. I texted my wife a screenshot. She sent back a thumbs up and "what is a PR". I printed it. Yeah, I know. It's on my cubicle wall next to my retirement shadow box.

What I'd tell any vet (or anyone) making the jump

1. Leave the rank at the door. Keep the discipline.
2. Fifteen-minute rule. Ask.
3. Treat code review like an inspection. It's about the work, not you.
4. In a crisis, your calm is worth more than your code. Use it.
5. Write things down. Your notes are your new qualification card.

Bravo Zulu to everybody here making a jump right now. Never too old.