THE BUILDER · A TRUE STORY
STUBBORN COMICS PRESENTS

THE BUILDER

ISSUE #001 OF ∞

PROLOGUE EVERY STORY OPENS IN THE DARK

Every system begins as chaos.

Most people see complexity.

I see a problem waiting to be solved.

SPLASH PAGE EVERY STORY NEEDS A BUILDER

AANAND
ARORA

IF THE SOLUTION DOESN'T EXIST,
I'LL BUILD IT.

Most people see disconnected systems.

I see opportunities to connect them.

Most people see manual effort.

I see automation.

Most people see complexity.

I see patterns.

CHAPTER 01 THE ORIGIN

EVERY BUILDER HAS
AN ORIGIN STORY.

I was never interested in technology for the sake of technology.

The tools changed. The curiosity didn't.

What fascinated me was the challenge.

  • Why does this process take so long?
  • Why are these systems disconnected?
  • Why is this problem still unsolved?

That curiosity eventually became a habit.

And that habit became a career.

On paper, I'm a mechanical engineer who ended up building AI systems. In practice I've been the same person the whole time — someone who can't walk past a broken process without sketching the fix.

TOOLKIT — the tools change; the curiosity doesn't enterprise AI · data platforms · semantic search · agentic workflows · automation · analytics

BASE OF OPERATIONS
Pune, India
CURRENT MISSION
Enterprise AI & Data Platforms — Office of the CDO, Tata Technologies
TRAINING
B.E. Mechanical, Thapar → M.Sc. Data Science & AI, BITS Pilani (in progress)
FIELD NOTES
Ctrl+Think — a newsletter on AI, automation & intelligent systems
KNOWN ALIAS
the stubborn sailor

CHAPTER 02 THE ENEMIES

EVERY STORY NEEDS VILLAINS.
MINE AREN'T PEOPLE. THEY'RE PROBLEMS.

Every company I've walked into, the same four villains were already there — wearing a different logo. You've met them too.

CHAPTER 03 THE MISSIONS

FIVE PROBLEMS THAT
DIDN'T STAY PROBLEMS.

The confidential stuff stays in the vault — no internal diagrams, no screenshots, nothing that earns me a call from Legal. What's left is the part I actually care about: the problem, the thinking, and what changed. Pick an issue.

CHAPTER 04 THE DOCTRINE

GOOD SYSTEMS DON'T SOLVE ONE PROBLEM.
THEY MAKE FUTURE SOLUTIONS POSSIBLE.

The doctrine is simple: everything I build has to make the next thing easier to build. Otherwise I've just produced more chaos with better branding.

SYSTEMS DOCUMENTS CONVERSATIONS SIGNALS THEPLATFORM ingest · govern · structure SEARCHmeaning, not keywords AGENTSintent → action ANALYTICSquestions → answers PEOPLE,FASTER
LIVE ASSEMBLY — COMPLEXITY ENTERS LEFT. CLARITY EXITS RIGHT.

CHAPTER 05 THE ROAD

THE WORK IS SYSTEMS.
THE FUEL IS THE ROAD.

checkpoint, not destination.

The mountains remind me how small I am.

The road reminds me to keep moving.

The next challenge is always somewhere beyond the horizon.

FIELD NOTE — MY BEST ARCHITECTURE DECISIONS WERE MADE SOMEWHERE ON A MOUNTAIN ROAD.

ISSUE #∞ IN PROGRESS

STILL BUILDING.
STILL LEARNING.
STILL EXPLORING.

The problems keep changing. That's what makes them interesting.

FINAL PANEL THE INVITATION

HAVE A PROBLEM
WORTH SOLVING?

I'm not collecting job titles.
I'm collecting problems I can't stop thinking about.

EMAIL ME CONNECT ON LINKEDIN ↗

STUBBORN COMICS · ISSUE #001 · THE BUILDER

THE FOUNDATION

EVERY HERO STORY STARTS WITH INFRASTRUCTURE. NOBODY PUTS THAT ON THE POSTER.

THE CHALLENGE

Everyone wanted AI. Almost nobody wanted to talk about the plumbing. Data was scattered across systems that didn't speak to each other, every team integrated their own way, and governance ran on good intentions. You can't build intelligence on top of that — I've watched people try.

THE APPROACH

I took the unglamorous route: one platform, one way data moves, governance enforced by the platform instead of by reminders. And I refused to design only for the current wish list — the whole point was workloads nobody had asked for yet.

THE OUTCOME

Today it carries analytics, AI applications, and agents that didn't exist when we started. That's the only test of a foundation that matters: the things it holds up later.

LESSON FILED: Great systems are invisible. When they work, everyone moves faster.

END OF ISSUE #001 · NEXT: THE TALENT MAZE

STUBBORN COMICS · ISSUE #002 · THE BUILDER

THE TALENT MAZE

SOMEWHERE IN THE DATABASE, THE PERFECT CANDIDATE IS INVISIBLE…

THE CHALLENGE

The right person was already in the pile. The pile was the problem. Keyword search treats "built data pipelines" and "ETL developer" as strangers — so great candidates vanish because they used the wrong noun.

THE APPROACH

I built search that reads meaning instead of matching strings — vector embeddings, LLM workflows, and ranking that learns from what recruiters actually do, not what they say they do.

THE OUTCOME

Recruiters stopped digging and started deciding. The pile became a shortlist, and every name on it came with a reason attached.

LESSON FILED: The best answers usually already exist. The real challenge is finding them.

END OF ISSUE #002 · NEXT: THE LOST KNOWLEDGE

STUBBORN COMICS · ISSUE #003 · THE BUILDER

THE LOST KNOWLEDGE

THE ORGANIZATION HAD AMNESIA. NOBODY HAD NOTICED YET.

THE CHALLENGE

Watch a company solve the same problem three times in three departments and you start taking it personally. The knowledge existed — in documents, decks, repositories, and people's heads. It just couldn't be found by the person who needed it on a Tuesday afternoon.

THE APPROACH

Centralizing files is easy, and mostly useless. The real work was connection: linking what the organization knows to whoever needs it, and making retrieval smart enough to answer the question behind the question.

THE OUTCOME

The organization started remembering. Old answers resurface for new problems, and "has anyone done this before?" finally gets an answer that isn't a shrug.

LESSON FILED: An organization's greatest asset is usually the knowledge it already has.

END OF ISSUE #003 · NEXT: THE PROCUREMENT ORACLE

STUBBORN COMICS · ISSUE #004 · THE BUILDER

THE PROCUREMENT ORACLE

MEANWHILE, IN A MEETING ROOM: A SHARP QUESTION ENTERS A TICKET QUEUE. IT IS NEVER SEEN AGAIN.

THE CHALLENGE

A leader with a sharp question shouldn't need to know what a star schema is. But every insight ran through someone who could write SQL — so curiosity sat in a queue, and most questions quietly died there.

THE APPROACH

I built an agent that takes the question in plain language and does the rest: writes the queries, runs the analysis, draws the chart, and sticks around for the follow-ups. You bring intent. The system absorbs the complexity. That's the deal.

THE OUTCOME

Executives ask their own questions now. The distance from "I wonder" to "I know" went from days to a sentence.

LESSON FILED: People shouldn't need to learn systems. Systems should learn people.

END OF ISSUE #004 · NEXT: THE MACHINE THAT BUILDS MACHINES

STUBBORN COMICS · ISSUE #005 · THE BUILDER

THE MACHINE THAT BUILDS MACHINES

AND THEN, QUIETLY, HE STARTED AUTOMATING HIS OWN JOB…

THE CHALLENGE

Every analytics solution walks the same road: requirements, documentation, modelling, build, test, deliver. Do it fifty times and you stop seeing tasks — you see a pattern. And a pattern is just a machine you haven't built yet.

THE APPROACH

So I built the machine: an agent workflow that takes a business requirement and carries it to a working solution — interprets the intent, drafts the plan, validates the data, generates the output. Humans stay exactly where judgment lives.

THE OUTCOME

Idea-to-solution collapsed from weeks to a conversation. The process scales without scaling the team — and I get to spend my time on problems that don't repeat.

LESSON FILED: The future of automation isn't doing work faster. It's building systems that know how to work.

END OF ISSUE #005 · NEXT: WHATEVER YOU BRING ME.