From Medium to My Mind: How I Built a Digital Twin of Myself in 24 Hours

If you know me, I love writing, reading, coding, and building. I often publish on Medium, sharing insights from my journey in AI and engineering leadership. But with the rapid evolution of gen-AI, most of my weekends now vanish into experiments—pushing the boundaries of what AI can enable.

But lately, I've felt constrained by traditional content creation platforms. They operate like legacy apps, still treat content as static artifacts—something to consume, not converse with. The content I write is my reflections on complex topics, lessons learned from scaling engineering teams, and insights from building production AI systems.

Why shouldn't I be able to have a conversation with my own accumulated knowledge?

So this weekend, I embarked on an 18+ hour coding marathon. What started as a simple blog migration from Medium to my own platform (nigamg.ai) evolved into something far more ambitious: building a conversational digital twin that has access to my entire knowledge base.

The Vision: More Than Just Another Blog

Traditional blogs are write-once, read-maybe affairs. But what if your content could be more interactive? What if readers could ask follow-up questions, explore related concepts, or dive deeper into specific topics? What if you could have a conversation with your past self about ideas you've developed over years of writing?

This isn't just about novelty—it's about creating a new paradigm for knowledge sharing and personal learning. As engineering leaders, we accumulate vast amounts of insights that often get buried in blog posts, meeting notes, or passing conversations. A conversational interface to this knowledge could be transformative.

From Concept to Reality

The Great Migration

First challenge: extracting my content from Medium. Medium's export functionality gives you HTML files, but I needed structured data with proper metadata. I built a scraper that:

- Extracted articles, titles, publication dates, and tags - Cleaned up Medium's HTML artifacts (those annoying formatting quirks) - Generated AI summaries for each piece using GPT-4 - Created a searchable knowledge base stored in S3 The result: 100+ articles properly structured and ready for the next phase.

Building the Knowledge Engine

Here's where it gets interesting. I didn't just want a static blog—I wanted my content to be conversational. The architecture needed to handle:

Smart Content Retrieval: Using semantic search to find relevant content based on user queries, not just keyword matching.

Context-Aware Responses: The AI needed to understand not just what I wrote, but the context and nuance behind my thoughts.

Real-Time Learning: As I add new content, the system should immediately incorporate it into the knowledge base.

I implemented a RAG (Retrieval-Augmented Generation) system with:

- Vector embeddings for semantic search - LRU caching for performance (because eng habits die hard) - Streaming responses for that real-time feel - Multi-modal content support (blogs, podcasts, notes, youtubes)

The Digital Twin

The final stretch was the most ambitious: making this feel like actually talking to me. This required careful prompt engineering to capture my communication style, technical depth, and leadership perspective.

The system now includes:

- Voice conversations (using ElevenLabs for natural speech) - Context from multiple sources (not just blogs, but podcast transcripts, notes, book highlights) - Memory of past conversations to maintain continuity - Professional boundaries (it won't discuss personal details, maintaining appropriate VP-level discretion)

The Technology Stack: Modern, Scalable, Pragmatic

As you'd expect from someone who's scaled engineering teams, I chose battle-tested technologies:

- Frontend: Next.js with React (because sometimes the boring choice is the right choice) - Backend: Node.js with streaming APIs for real-time responses - AI: Claude latest Sonnet for reasoning, GPT-4 for embeddings, Whisper for speech-to-text - Storage: AWS S3 for content, with aggressive caching strategies - Voice: ElevenLabs for natural speech synthesis - Infrastructure: AWS Amplify for deployment (fast iteration was key) The entire system handles tokens in context while maintaining sub-second response times. Performance engineering principles applied to AI—because what's the point of a smart system that's slow?

Early Results: Surprisingly Natural Conversations

I've started testing it with friends - "It actually sounds like me."

"I asked about scaling challenges and got insights I've never seen in any blog post—it was synthesizing across multiple articles."

The system doesn't just regurgitate my writing; it synthesizes insights across my entire knowledge base, creating novel connections and providing contextual answers.

A Quick Conversation with My Digital Twin

Here's a sample exchange that shows what's possible:


The response synthesizes insights from multiple blog posts while maintaining my voice and offering to dive deeper—exactly what you'd expect from a good engineering conversation.

What's Next: Let’s hear this audio clip where I’m talking to my self —

The Meta Lesson: AI as Amplification, Not Replacement

The most important insight from this experiment isn't technical—it's philosophical. AI isn't replacing human expertise; it's amplifying it. My digital twin isn't trying to be me; it's making my accumulated knowledge more accessible and interactive.

As engineering leaders, our job is increasingly about synthesis—connecting ideas across domains, helping teams navigate complexity, and making good decisions with incomplete information. AI can help us do this better, but only if we approach it thoughtfully.

Try It Yourself

The system is live at [https://www.nigamg.ai](https://www.nigamg.ai/) . Ask it about scaling engineering teams, building AI products, or navigating the complexities of technical leadership. And I'm always interested in feedback from fellow engineering leaders.

This is just the beginning. The intersection of personal knowledge management and conversational AI is rich with possibilities. What would your digital twin know? What conversations would it enable?

Want to discuss this further? My actual digital twin is available 24/7 at nigamg.ai, or reach out to me directly. As always, I'm more interested in building the future than just talking about it.

---

P.S.: Claude deserves co-authoring credit on this project. The irony of using one AI to build another AI that talks like me isn't lost on me. We're definitely living in interesting times.