Wednesday, December 31, 2025

Reflections on a Journey of Transformation: My 2025 at IBM and the Path Ahead

My tenure at IBM has come to an end, but the narrative I’ve spent two decades building is far from over. As I close this chapter, I find myself looking toward the next—searching for an organization ready to leverage twenty years of experience in global training strategy and digital transformation.

The past year was defined by a singular mission: overseeing the deployment of AI-driven tools to accelerate learning content development. I witnessed the immediate, complex results of those efforts firsthand. Now, I am eager to carry that momentum forward. But before I step into the future, I must reflect on the remarkable, often unpredictable, year that was 2025.

Leadership in a Time of Transition

The year began in the wake of 2024’s reorganizations. I found myself leading a new team, positioned as the primary subject matter expert for our portfolio. With a deep understanding of our clients’ needs and our go-to-market strategy, I possessed a clear vision for aligning our curriculum with the company’s broader goals.

My team was a study in contrasts: seasoned professionals familiar with the product line working alongside early-career hires navigating their first corporate roles. This dynamic shifted my focus toward intensive coaching. Unlike previous mentorships with mid-career colleagues, this year required a more foundational approach. I invested deeply in one-on-one sessions, helping these new professionals bridge the gap between academia and the complexities of IBM’s culture. Watching them transform into confident, high-performing contributors remains one of my proudest achievements of the year.

Innovation and Connection

By summer, the focus shifted to "agentic AI." I had the privilege of leading team "Perfect Pitch" in the third annual 2025 watsonx Challenge. This internal "hackathon" is a rare opportunity to collaborate outside of traditional silos. Our diverse group developed a proposal for a "Learning Content Developer" agent designed to automate content aggregation and compliance checking. It was a masterclass in collaborative innovation, providing us all with vital hands-on experience with the platform.

That spirit of connection carried into October at TechXchange in Orlando. I spent the days leading up to the conference facilitating enablement sessions for our sales teams and business partners. In an era of remote work, the opportunity to reconnect in person was invaluable. I met my new teammates face-to-face for the first time, forging relationships I hoped would anchor our future projects.

The AI Paradox

The news that followed in November was as sudden as it was jarring. Despite a successful year and several critical projects in mid-flight, a massive restructuring affected thousands of people across the  organization. On November 4, my team and I were informed that our positions were being eliminated.

There is a certain irony in being a leader of digital transformation only to be affected by the very shifts that AI is driving across the tech landscape. We were assured the decision was not a reflection of performance, yet that provides little solace when decades of institutional knowledge are severed in an instant. My final day was December 4. Stepping away from the "hive mind" after 20 years felt less like leaving a job and more like saying goodbye to family.

Navigating the "Mordor" of the Modern Job Market

To borrow a phrase from Boromir: "One does not simply walk into Mordor." The current job market is formidable, demanding a level of strategic persistence that goes far beyond the traditional resume submission. I have spent the last month treating the job search with the same rigor I applied to my global strategies—leveraging networks, researching target roles, and customizing every point of contact.

While the holiday season passed in a blur of applications and follow-ups, I am beginning to see the first signs of traction. Phone interviews are turning into meaningful conversations, and through it all, I am making space for self-care and family. The journey ahead may be long, but the "flicker of light" at the end of the tunnel is growing brighter. I am ready for the next challenge.

Tuesday, October 15, 2024

IBM TechXchange Conference in Las Vegas 2024

I will be there next week and I'm very excited about it! This conference is different than others in that it's really geared towards education and skill enablement - getting you to the next level with products, technologies, etc. As I write this, it begins in 6 days, but it's not too late to register: https://www.ibm.com/community/ibm-techxchange-conference/ 

I am co-leading 3 learning sessions on IBM Liberty, and I will also be in the Sandbox (expo area), so if you see me there, please say hello!

Thursday, January 31, 2019

Troubleshooting Kubernetes: "zombie pods"

I recently ran into a mysterious problem as I was developing and testing a lab exercise to teach about Kubernetes resiliency. I sort of caused the problem myself, because I had run through several scenarios with the example application, and I wanted to blow it all away and start over...so I just started deleting things. That, my friends, is a sure-fire way to break something. If you are dealing with Deployments and ReplicaSets, merely deleting a pod is just going to cause K8s to try and redeploy it.

I ended up with a handful of pods that were stuck in a state of "Terminating," and they would not die. For days. So, I asked around, tried researching the problem. A google search of "pods stuck in terminating" gave many hits, with many different possible causes and solutions. Some issues mentioned kubelet and a hostname mismatch - that was not it. 

I tried doing a drain, cordon, and shutdown of the node. When I started it back up, the pods were still there, still terminating. 

I tried deleting the Helm release, and helm command would not work. I got errors, which I googled, and that pointed to a problem with Tiller. I tried deleting the helm cache. I tried reinstalling Tiller, but Tiller would not come up. The Tiller pod was stuck in a state of "Pending." 

Some of the issues mentioned that they were trying to deploy pods on the master node, which is something you typically don't do, because the whole point of K8s is to let it schedule pods on the worker nodes. However, if you want a single-node environment, or something like that, you must remove a taint from the master node that prevent pods from being scheduled on it. That sounded a lot like my situation, because I was actually only running a master node...

...and that was the problem. I started with a cluster with two worker nodes, but they were offline. I had not restarted them since encountering the problem. After starting the workers, the status of all the hung pods resolved.

The moral of this story is: sometimes the answer is just too obvious to find through an internet search.  


Tuesday, June 12, 2018

IBM Microservices Specialization on Coursera

The IBM Microservices Specialization just launched on Coursera! This series of self-paced online courses takes you through microservices fundamentals, microservices application development, and deployment of microservices to IBM Cloud and IBM Cloud private. In this course, you get hands-on experience with:

  • Docker and containerized applications
  • Kubernetes - a container orchestrator
  • Helm - the Kubernetes package manager
  • Microclimate - an end-to-end development environment for microservices
  • Jenkins, and other tools used for DevOps
  • IBM Cloud (formerly known as Bluemix), and 
  • IBM Cloud Private - an application platform for developing and managing on-premises, containerized applications. 
You can audit this series at no charge, or enroll for a nominal fee and earn a completion certificate. 

Monday, February 12, 2018

Microservices and Kubernetes education on Coursera.org

I recently developed and launched a new course on Coursera.org -

IBM Cloud: Deploying Microservices with Kubernetes

About this course: In this course, you learn how to install the Kubernetes command-line interface (CLI), and create a Kubernetes cluster on which to run applications. Hands-on tutorials show you how to deploy microservices to a Kubernetes cluster. You also learn about securing and managing a Kubernetes cluster, and how to plan your Kubernetes cluster for deployment on IBM Cloud.

You can audit this course at no charge, or pay a nominal fee to receive the badge/certificate after completing it.

This course is part of a specialization on Microservices. If you complete all courses in the specialization, you get a special badge. Another course in the specialization, Microservices Fundamentals, also recently launched, and two more courses in the specialization are targeted for release later this year.

Coursera is a an education-focused technology company that offers online courses, and works with universities and other organizations to offer online courses, specializations, and degrees in a variety of subjects.

Thursday, July 20, 2017

Teaching mobile developers in Africa

This article is getting a replay on the IBM Mobile Business Insights blog:

http://mobilebusinessinsights.com/2017/07/sowing-the-seeds-for-tomorrows-mobile-developers-in-africa/

A bunch of my articles from that time period have been archived, and are no longer available online, but this one, I think, is worth revisiting. It was one of the most interesting and successful experiences that I had while teaching abroad.