Why I'm Documenting My AI Journey

After two decades designing systems for large enterprises — Oracle databases, SAP Hybris, PeopleSoft, complex SQL pipelines — I’ve watched technology shift dramatically beneath my feet more than once. I’ve always adapted. Now the biggest shift of my career is underway, and this time I’m not just adapting: I’m going all-in.

Why AI, Why Now

The enterprise world I know is being reshaped by AI faster than most people realize. The architects and developers who understand AI at a deep level — not just how to call an API, but how these systems actually work — will be the ones shaping what gets built next.

I want to be one of those people.

Why Document It

I’ve learned more by explaining things than by consuming them. Writing forces clarity. If I can’t explain it, I don’t actually understand it.

There’s also a practical reason: building in public creates accountability. If I say I’m going to figure out how LLM fine-tuning works, I’d better actually do it.

What to Expect Here

No fluff. No “10 ways AI will change everything” hot takes.

What you’ll get:

• Experiments I’m running and what I find
• Honest takes on tools, frameworks, and approaches
• Lessons from applying an enterprise architecture mindset to AI
• Projects worth sharing (some will fail, and I’ll document that too)

If you’re a fellow technical professional navigating the AI landscape, you’re in the right place.

Let’s get into it.