100 Posts Later: How Sharing My Work Helped Me Find My Momentum Again

There is usually a practical question in my mind when I click Publish. Did the code run? Is the explanation clear? Did I check the signs in that equation one last time?

This time, the number stopped me: 100.

This is the hundredth published article on The Data Guy. It is not a tutorial, a model comparison, or a release announcement. It is a moment to look back at why I started, what changed along the way, and what publishing one hundred times has taught me.

It is also worth saying something plainly that many of us are too quick to soften: I feel proud of this achievement. I feel accomplished. More importantly, I feel motivated to keep going.

Contents

---

A Return That Became a Beginning

On April 14, 2025, I published the first article on this site: Coming Back to AI Roots—My Professional Journey.

That post told the story of a career coming full circle. My fascination with artificial intelligence began long before the current wave of generative AI. In 2003 and 2004, I worked on Urdu OCR and paper-form data extraction, recruiting fellow students to produce handwriting samples that I could scan, label, and use to train neural networks.

Then my career moved toward web development and enterprise systems. Those years taught me how to build software that must survive contact with real users, real business processes, and real operational constraints. But the pull toward AI never disappeared.

The first article was my declaration that I was returning to that original curiosity. I wrote that I wanted to explore practical AI, connect research with production systems, and share what I learned with other builders.

At the time, I did not have a map for one hundred posts. I had a direction and the willingness to begin.

Looking back, that was enough.

The Honest Beginning Behind the Milestone

A month later, I published Build, Ship, Share Is the Way. It contained a more vulnerable admission.

After more than 22 years in technology, I had started slowing down. Experience had made me comfortable—perhaps too comfortable. I was consuming more than I was creating, spending time doomscrolling and watching other people build things instead of building them myself.

The AI Makerspace community helped interrupt that pattern. Its simple mantra—Build. Ship. Share.—gave me a practical way forward:

• Build something that makes you curious.
• Ship it before perfection becomes another form of procrastination.
• Share what you learned so the work can help someone beyond you.

What One Hundred Posts Look Like

Before this article, the archive contained exactly 99 published posts. Together, those articles represent approximately:

The numbers are satisfying, but they are not the real story. Each one represents a question that I stayed with long enough to turn into something another person could read, run, challenge, or extend.

The milestone posts show how the journey expanded:

• Post 1 was the decision to return to my AI roots.
• Post 25 introduced The Data Guy Show and carried the writing into a new medium.
• Post 50 tackled a deeply practical enterprise problem: downloading SSRS reports from D365 Finance & Operations.
• Post 75 explored production observability for D365 F&O.
• Post 90 connected Itô calculus to the Black-Scholes pricing engine.
• Post 99 used finite differences and PSOR to solve the American put PDE.

No single post tells the whole story. Together, they form a record of sustained curiosity.

Curiosity Did Not Stay in One Lane

The early archive was dominated by AI engineering, RAG evaluation, agents, and the difficult work of taking prototypes into production. That was a natural extension of my return to AI and my enterprise background.

The writing then moved deeper into Dynamics 365, authentication, observability, automation, Model Context Protocol integrations, and open-source releases. Those subjects reflected the problems I was solving in practice: how do you connect new intelligence to systems that businesses already depend on?

Then another thread began pulling at me.

I started writing about probability, Monte Carlo methods, stochastic differential equations, Bachelier, Wiener, and Itô. That mathematical journey eventually crossed into Black-Scholes, option pricing, free boundaries, numerical PDEs, and quantitative finance.

On paper, those topics may look like different lanes. To me, they are connected by the same questions:

• How do we reason under uncertainty?
• How do we turn an elegant idea into a working system?
• How do we test whether the result deserves our trust?
• How do we explain complexity without hiding the difficult parts?

Consistency did not mean writing the same article one hundred times. It meant returning to those questions from different directions.

Five Lessons the Writing Taught Me

Motivation Often Follows Action

We often imagine motivation arriving first and action following naturally. My experience has usually been the reverse.

Some articles began with excitement. Others began with a blank document and the decision to write one honest paragraph. The energy often appeared only after the work had started.

Momentum is not a personality trait. It is something we generate by moving.

Explanation Is a Test of Understanding

It is easy to feel that you understand a concept while reading someone else's explanation. Writing your own removes that illusion.

Explaining a RAG metric, an authentication flow, Itô's lemma, or a complementarity condition forces you to confront every missing step. Code must reproduce the claim. A chart must show what the caption says it shows. A benchmark must have a clearly defined comparison.

Writing did not merely document my learning. It made the learning more rigorous.

Shipping Changes Your Relationship With Perfection

Every article can be improved forever. There is always another example to add, another sentence to polish, and another edge case to investigate.

Shipping does not mean ignoring quality. It means recognizing the point at which additional polishing stops serving the reader and starts protecting the writer from being seen.

Publishing repeatedly taught me to care deeply about the work without demanding that any single post carry the weight of being definitive.

Curiosity Compounds

One article rarely ends with a period. It ends with better questions.

A post about Monte Carlo history led toward stochastic processes. Stochastic processes led toward Itô calculus. Itô led toward Black-Scholes. Black-Scholes led toward American options, where optimal stopping opened three different numerical paths.

Sharing Turns Private Learning Into a Public Asset

Notes stored on my computer can help me. A published explanation can help someone I may never meet.

That does not require a massive audience. If one developer avoids an authentication mistake, one student finally understands why a formula works, or one experienced technologist feels encouraged to begin learning again, the act of sharing has already multiplied the value of the work.

The Count Is Clean; the Path Was Not

One hundred published posts sounds orderly. The work behind them was anything but.

There were abandoned openings, drafts that needed to be rebuilt, charts that communicated the wrong thing, code that needed another verification pass, and articles that grew far beyond their original scope. There were evenings when the words arrived quickly and others when a single paragraph refused to cooperate.

There were also stretches when other parts of life deserved more attention than the publishing schedule.

I am mentioning this because milestones can hide the process that produced them. The clean number is the visible part. Underneath it are revisions, uncertainty, missed plans, restarts, and many small decisions to continue.

That makes the achievement feel more meaningful, not less.

Gratitude

No body of shared work is created alone.

I am grateful to the readers who gave these articles their time, shared them, questioned them, and sent thoughtful feedback. I am grateful to the open-source maintainers, researchers, educators, colleagues, and practitioners whose work gave me something worth studying.

I am especially grateful to the AI Makerspace community for helping me rediscover the rhythm of building, shipping, and sharing. What began as encouragement became a habit, and the habit became this archive.

And to everyone who has read even one article: thank you. Writing may begin as a solitary act, but being read turns it into a conversation.

What I Want From the Next Hundred

I do not want to turn this milestone into a promise to publish faster. I want it to sharpen the direction of the work.

For the next hundred posts, I want to:

• go deeper into the intersection of AI, enterprise systems, mathematics, and finance;
• publish more reproducible notebooks, visual explanations, and research-backed series;
• show limitations, failed approaches, and uncertainty alongside successful results;
• keep connecting theory to code and code to real-world decisions;
• protect curiosity from the pressure to chase every new trend;
• continue sharing before perfection becomes an excuse to stay silent.

The goal is not simply to make the archive larger. It is to make it more useful, more thoughtful, and more recognizably mine.

The Next Post Starts the Same Way

The first post began with a return to something I had once loved. This one confirms that the return became a practice. Across 165,000 words, dozens of code examples, and more questions than I could have predicted, the most important result is simple:

I am proud of what I built. I am grateful that I shipped it. I am humbled that people chose to read and share it.

Now it is time to begin the next hundred—one useful question, one honest explanation, and one published article at a time.

Build. Ship. Share. Keep going.

---

If you are waiting to begin something—or begin again—what is the smallest thing you could build, ship, and share this week?