What a week. What a week, indeed. I'm in an emotionally odd place right now because after nearly 20 years with my current employer, I tendered my retirement notice. Throughout my career, I've striven to prove my worth and do whatever was necessary to keep my job and to keep my family fed. In my quest to remain financially solvent and be the provider I was raised to be, I never voluntarily left a job unless I was already hired by another firm. In all but one case, I left on great terms. There was one company whose bridge I burned to unrecognizable ashes, and I did so with no regrets. That's a story for another entry.
As the title of this entry states, I'm retiring, effective June 30th. It's the culmination of a five-year plan that I set into motion in 2020. But the realization of that plan is the result of two prior decades of financial discipline and focus in the background while I carried out my job responsibilities. To be honest, I really didn't get my financial savings shit together until I was in my 40s. Bills were paid and there was usually breathing room at the end of the month, but retirement savings was not a priority to me. After my paper route years (12 to 13 years old), I have worked nonstop; earning a real paycheck, and paying taxes since I was 14 years old.
![]() |
RF-4C ECM Systems Check Flight at Bergstrom AFB - Austin, TX |
I joined the U.S. Air Force at 18 years of age in the fall following my high school graduation. Despite (regrettably) never taking school seriously, I was an adept test taker, which yielded military entry exam scores that qualified me for any career field the Air Force offered. Ever the optimist, I selected the longest electronics-based course with the highest dropout rate. I never planned on making the Air Force a career and my thought was that the more complex training would have more value in the civilian world. The Electronic Countermeasures (ECM) field was heavy in radio theory and practice, and was at the top of the complexity pile alongside cryptologic analysis. I had never applied myself before like I did for that course, but my efforts paid off as I completed 48 weeks of tests, acing all except one. The one question they scored as incorrect referenced the result of removing the trigger current from a Zener diode, and none of the answer choices were correct. How anal am I for remembering this crap? I challenged the question and was informed several months later that I was indeed correct, and was subsequently given credit for having aced the entire course. It meant nothing to anyone but me. 37 of us started the course together, eight of us graduated, two of us were honor grads, and I was told that I was the first to ace the entire curriculum. I give credit where credit is due; to the instructors. Forty years later, I'm still proud of that. Honor grad afforded me the choice of any assignment worldwide and I opted to go back to Bergstrom Air Force Base in Austin. I stayed at Bergstrom until I separated from the service in 1989. The details of those years are worthy of their own series of stories, but not here.
My ECM radio training teed me up for nicely a role as an Associate Engineer with the Japanese company NEC in the burgeoning field of cellular telephony. NEC offered me a whopping $25k annually and I remember wondering how I could possibly spend that much money! From NEC, I bounced around using companies and roles in them as stepping stones for my career. I've been laid off a couple of times and outright fired once. I was self employed for five years, the last three of which led me to IBM. I joined IBM as a Senior Wireless Network Architect after successfully completing a few technically complex engagements for them as a subcontractor under my company Spectrum Concepts Wireless, LLC. I formed that company, not with ambitions of being huge, but as a means of keeping more of the money that I earned.
My specialty at the time was hospitality Wi-Fi, and I had some pretty compelling case study documentation to present whenever I was bidding a new gig, and then eventually in my IBM interview. I was the engineer, sales guy, accountant, project manager, janitor, and chief bottle washer; all in one. Essentially, I was a hired gun handling projects that were too small for large system integrators like IBM, yet too complex for the customers to handle using internal resources. One year working solo, I installed and commissioned T-Mobile Hot Spot services in over 1,000 Starbucks locations. I would fly into a city, rent a van, pick up a pallet of T-Mobile network hardware from a nearby warehouse, and drive all around the area, hitting every Starbucks on my list before flying or driving to the next cluster of stores. I had it down to a science and was turning up eight to ten stores every day. My pace was crushing that of their other suppliers and T-Mobile eventually (unofficially) used me as their sole Hot Spot integrator for Starbucks stores. I should have included juggler in my list of roles above because it was a Ringling Brothers caliber job to pay all my travel expenses up front and wait for reimbursement. True to the entrepreneurial spirit I inherited from my mother, I had built a well-oiled machine that was actually making money, and I had a six-month backlog of upcoming engagements. I was proud of it, but I didn't do it all alone. I had a mentor.
I had a background in radio from my Air Force training, but I cut my teeth in Wi-Fi working projects for a guy named Ed Suor in Rochester, NY. Ed was (still is) a brilliant engineer and entrepreneur who gave me not just an an opportunity, but genuine guidance and motivation. Working his projects for IBM got my foot in the door and essentially launched my new career. I believe that everything I have now, I have because Ed Suor had my back when I needed it most. I dissolved Spectrum Concepts Wireless so I could focus solely on IBM's work as a true blue-blooded IBMer.
IBM recruited me because of Ed and he gave me a stellar referral. It didn't hurt that I already owned and was fluent with the complex and somewhat pricey tools that were essential to successfully design the new generation (at that time) of Wireless LAN (Wi-Fi) networks that were proliferating hospitals, manufacturing plants, mega hotels, and educational campuses. I had demonstrated my expertise with the tools, an ability to manage complex projects, and to create the ridiculously detailed deliverable documents that complied with the IBM "method". Another thing that helped was my grey hair and beard. My age and experienced look gave me an advantage over the young bright-eyed college grads in the eyes of prospective clients. Project sponsors looked at me and saw a seasoned practitioner who knew how not to break things. This was paramount in live production networks where network uptime was the prime metric. Decades later, it's not lost on me that I am clearly the oldest guy in the room when I'm attending client and staff meetings. I'm not sure where the crossover point between seasoned and just old is, but I'm pretty sure I've passed it. But I digress.
IBM's recruiting pitch to me was "if you're between projects (on the bench) while working for us, we still pay you". Add that to four weeks paid vacation, lots of Federal holidays, a great salary, and a cool-sounding title "Architect", and I was sold. On top of all that, the manager to whom I would report was stand-up guy who to this day has proved to be the most uplifting and supportive manager I have ever worked for. My blood ran blue for 16 years until 2022 when IBM divested me and 80,000 others into our own fully-independent company called Kyndryl. I wanted IBM to be my last job. As I see it, Kyndryl is an offshoot of IBM, so my last job goal is essentially realized.
My original plan was to discuss my retirement plans to my leadership in early October of 2024, and to offer to work through December. My motorcycle trip to Mount Everest Base Camp and a potential knee surgery made me rethink my timeline and quietly extend my retirement disclosure to early May, with plans to work through June 30, 2025. I figured it was smart to continue with my corporate health insurance until after I returned from Tibet, and June 30th was the end of the financial quarter...a tidy time to sew up loose ends.
Making the decision to retire was easy, putting a date on it was tough, and notifying my leadership was easier than I thought it would be. What was tough was not disclosing it to anyone at Kyndryl before my formal discussion with my VP. I don't have any real friends at Kyndryl, but I do have some work associates with whom I am close. I trust them and I believe most would have kept my secret, but it would have been unfair of me to burden them with the knowledge of my retirement when their daily job tasks depend on my continued participation. In our weekly team calls, we would typically discuss upcoming projects, roles and responsibilities, which resources will be responsible for what, etc. Anyone aware of my retirement plans would have to bite their tongues, which would have been a lot to ask, even of a casual associate.
The conversation with my VP was positive. We agreed upon a date that supports my customer, allows time for me to offload company-owned hardware, facilitate knowledge transfers, and to sew up loose ends. So it's official. I will be unemployed and unemployable on July 1st, 2025. My daily focus will be on caring for my homestead, my livestock, and becoming a better beekeeper. I also want to pursue improving my drumming and step up my game playing in my band. I will focus on staying busy and engaged to the point that I don't pull out the gray hair that possibly facilitated this retirement opportunity in the first place.