I used to operate artillery systems.
Now I operate terminal windows.
That may sound like a wild shift—from field manuals to machine learning, from radios to regex—but really, the mindset stayed the same.
The journey from tactical to technical wasn’t easy. But it made sense the more I leaned into the skills I already had.
Here’s what that transition looked like—step by step.
Step 1: Recognizing the Crossover
At first, I didn’t see the link. I thought:
“What does an artillery guy have to do with Python or cybersecurity?”
But then I saw the overlap:
- Systems thinking
- Risk analysis
- Team coordination
- Mission execution under pressure
That gave me confidence: I didn’t have to start from scratch. I just had to translate what I knew into a new language.
Step 2: Finding a New Mission
The hardest part wasn’t learning code.
It was finding a sense of direction in civilian life.
In the military, every day has purpose.
In civilian life, you have to build that yourself.
I found mine in tech—specifically, in solving problems, protecting systems, and building tools that help others. That aligned with my military DNA.
Step 3: Treating Learning Like Field Training
I broke my learning into missions:
- "Understand Python basics"
- "Deploy a simple web app"
- "Complete a TryHackMe lab"
I tracked progress, reflected, and built feedback loops—just like after-action reports.
Learning tech was just like learning new field gear:
- Frustrating at first
- Slow and awkward
- But better with practice and reps
Step 4: Owning the Hybrid Identity
For a while, I felt I had to choose:
“Am I a vet, or am I a dev?”
Now I know:
I’m both. And that’s my edge.
Being tactical and technical gives me perspective, calm, and a deep sense of purpose.
Final Thoughts
You don’t have to erase your past to step into your future.
If you’re a veteran wondering if tech is “too different”—know this:
The skills are in you. You just need new tools.
Follow more at jameshenderson.online—where strategy meets syntax, and the transition never happens alone.