About Me — Jack Herlocker
Husband & retiree. Former software developer, technical writer, & IT geek. Occasionally do weird & goofy things.
Updated July 2024. Addendum February 2025.
Biography
I grew up in an upper-middle-class slash upper-class northern suburb of Chicago in the 1960s and 1970s. I was odd as a kid. However, I was with the same group of kids from kindergarten through eighth grade, so I avoided the mess that middle school can be for many odd kids. I wasn’t weird, I was just Jack, as far as my elementary school classmates were concerned. Then high school came along, and a huge school full of strangers, and suddenly I was weird, and wrong, in so many of my choices and the way I talked about things and the way I dressed and almost anything that didn’t deal with academics. I was happy to move on from high school with only “some” emotional scarring before entering the US Naval Academy (USNA).
USNA was… different. If high school was like getting thrown into a pool to learn how to swim, USNA was like a pool with no shallow end. Plus people standing around the edge throwing rocks. However, I did learn great people skills, although by “people skills” I mean I learned to blend in and not attract attention. Also a great technical education, of course, plus leadership and management experience I cannot imagine getting anywhere else.
I graduated from USNA in 1980. From there I attended Navy Nuclear Power School, then served in engineering on a nuclear submarine out of Groton, CT, before being medically discharged from subs following incidents as a result of injuries¹ in a civilian plane crash. I got to stay in the Navy by demonstrating some skills with computers, specifically “microcomputers” (as PCs were known then), which were still new and strange.
As an IT guy, I served in Arlington, VA (Navy Recruiting Command HQ), and Seoul, South Korea (a joint command where I got to work with Navy, Army, and Air Force people); I was an instructor at Officer Candidate School and the Training Department resource (finance) officer in Newport, RI. Along the way, I married a nice fellow lieutenant. In 1990 I got passed over for promotion, was released from service, and went to live with my wife in California. We got divorced shortly thereafter,² however I found a job in Silicon Valley with an R&D group (Electric Power Research Institute); alas, I found I hated California and within a couple of years moved to Pennsylvania³ for a job with Sprint. After another two years, I left Sprint before local layoffs hit to work as a tech writer/programmer for a local company that did technical contracting projects. That job lasted a good four years before the company got bought out, so I worked as an IT manager for an international company (Voith), where I met Deb, my current (and final!) wife of 24 years (25 in February 2025) and counting. After almost a decade my job was eliminated in a reorganization. Still, I was lucky (at the advanced age of 51!) to find work at a small insurance company as a programmer/database administrator/tech support person; even better, it was near to where Deb had switched (Millersville University, Office of the President), so we got to commute into work again. That was good for eleven years before I retired in December 2019 — just in time for the pandemic! Deb retired the month after. I’d love to say it was great planning, but nope, just great luck.
My Writing
I liked to write in school, picking up some minor awards in high school and the Naval Academy. While I was with Navy Recruiting, I took over a monthly column, “Bits & PCs”, for the national newsletter (no, I did not pick the name); I wrote about Navy Recruiting Command policy toward PCs (there were hundreds at that point — yes, in the entire country), offered suggestions, fielded general questions, and occasionally shot myself in the foot. I found that incorporating wry humor helped encourage people to read my admittedly dry technical descriptions.
When I was the resource officer for the training department in Newport, RI, writing memos about the budget was a weekly occurrence. Writing memos that the budget folks in twelve different schools would read turned out to be a challenge. So I fell back on that wry humor thing again, although I was careful to only put smartass remarks and non-sequiturs in the footnotes (WordPerfect made it easy to add footnotes—yes, even in Navy memos.) I only got chewed out by one captain once for it… but another captain told me not to worry, he liked reading my memos (which was odd because they were addressed to his resource officer, but okay).
As a civilian technical writer, I found that humor and tech writing do not go together. Okay, so I wrote humorous pitch presentations for potential clients; after my boss’ boss sat in on one, I got reprimanded for unprofessionalism (even though the clients loved it and we got the contract) and got dinged on my performance review. Twice. Well, it wasn’t like I was going to be a career tech writer…
As an IT manager for Voith, I was writing memos with boring subjects again (emails, by this point), so humor was important. There’s nothing like the ego rush you get when somebody opens your email on nightly backups and you hear them laugh out loud!
I first became aware of Medium back in 2015 when I found it was a place that let anyone (more or less) post things. My first posting: September 2015, with recycled stuff from my rebuilt genealogical website. I had previously made a faint attempt at a blog; nobody read it, except family, but even then only when I sent them a link. I was moving the genealogical data to a new website, but I didn’t want to lose the blog posts (all three!), so hey, Medium, what the heck, y’know? I occasionally posted new stuff, but not with any particular attempt at a pattern.
And then I started actually reading stuff on Medium. It made me realize that there was interesting material, from interesting people. So… not just a place to dump junk?
I started leaving responses to posts. Just quick comments, at first. But then I started getting emotionally involved with the stories people posted and the unfiltered way they came across, and I started putting some of my emotions into the responses. There was a liberating feeling about it.
Conversations with My Wife/Chats with Deb
In December 2015, Deb and I had a conversation after a news snippet that came on the radio. I captured that conversation in text and posted it on Medium. The conversational format has evolved over the years (hint for those who want to create a series: come up with a format BEFORE you start posting [you’d think a tech writer would know this!]) and other people have similar things, but it’s still my main shtick because my wonderful wife keeps giving me material. People say they enjoy reading these because it makes them laugh, but I don’t really see the conversations as “humor”; it’s just life, is all, and sometimes life is funny.
“Conversations with My Wife” turned into “Chats with Deb” when Medium changed their format (again) so that long titles got truncated and subtitles frequently got dropped.



I Like Being Married (January 2016)
For a time I was in a hard patch, when Mom (Deb’s mom) was dying from cancer at home, and Deb was living there to take care of her. I was spending a lot of time on Medium, reading and responding and posting. I started posting more things from my heart.
And the oddest thing happened. People noticed. I got asked if I wanted to have my article published in a Medium publication. (A… what? Um, sure, whatever.) I got interesting feedback. People could relate. Or wish they would also find that One Person (I was 41 when I met Deb, with a divorce and a failed relationship in between — hang in there!).
And other stuff
I occasionally indulge in poetry, short fiction, and observations of things I’ve learned.







Other Things
I am on the tech team and webmaster at our church — I’m an agnostic, but (1) Deb isn’t, and (b) the church does good work in the community; plus it’s United Church of Christ, which is fairly laid back in their orthodoxy. I occasionally do odd tech stuff for friends.
Deb and I planned to go traveling in retirement (a big reason for retiring sooner, the other one being my failing brain that was making it hard to be a good programmer) but after getting postponed (twice) our big 20th Anniversary Alaska Trip in May 2020 was our big 22nd Anniversary Trip in May 2022. We still have more places to go!
Otherwise, I like being Deb’s husband. She’s awesome.
Addendum—I have a book!
Available in print (hardcover and soft) and Kindle on Amazon and electronically on Apple Books.
¹Broken ribs, broken nose, broken wrist, broken foot. Oh, and a traumatic brain injury that the Navy thought was okay but wasn’t, actually, so much. Yup, I’m brain-damaged. 😁 I managed to compensate for quite a few years, but lately, it’s been getting harder to function consistently.
²As I like to tell people, we were too much alike: I was in the Navy, Linda was in the Navy; I’m a nerd, she’s a nerd; I like sleeping with women, she likes sleeping with women… sometimes a good marriage just needs some differences, y’know? 😁 We’re still on good terms; Deb & I were invited to her wedding last year and got to meet her wife, who’s adorable.
³I picked the Pennsylvania job because (when starting from California) it’s on the way to New England, which is where I wanted to end up in civilian life when I took the Navy assignment to Rhode Island. Except my buddy Linda proposed to me while I was stopped off to see her on my way from Korea, so I ended up as a civilian in California instead. Strictly speaking, I could still end up in New England, but I’ve lived in south-central Pennsylvania for over thirty years now — longer than I’ve lived in any one area in my life — so the odds are pretty good that yes, I’m sticking with the Keystone State. Plus Deb likes it here.