The 10 Days That Saved Me 3 Weeks for Chrome Extension

"I Shipped My Chrome Extension in 3 Weeks: A Journey to Paradoxical Productivity"

The First Ship: Fast Equals Broken

I shipped my Chrome extension in just three weeks. I was excited and jumped straight into coding. I built the detector, the UI, and the features. My mantra was simple: ship fast and iterate later.

However, I missed a crucial step. I had no specifications or systems in place. My focus was solely on momentum and determination. I was obsessed with getting it live. I thought I was being productive. I wrote lines of code every day, and progress bars were moving. But when I published it, disaster struck. The extension failed at authentication. Users couldn't access it from the same Salesforce page. Not sometimes, but every time.

I stared at the error logs, confused. I didn’t understand how Salesforce session authentication worked across domains. I had spent three weeks coding, but I lacked a fundamental understanding of the system I was building for.

That’s when I realized I had violated two key principles: Outcome vs. Process and Flexibility. I was fixated on the outcome without a solid process underneath. I was also locked into a rigid coding approach, grinding through blockers without considering alternatives. Additionally, I neglected my Life-Work Balance. Three weeks of hustle left me burnt out.

The cost? A broken extension and a frustrated builder.

The Step Back: Doing Nothing Was Doing Everything

I faced a choice: rebuild it the same way or take a step back. I chose the latter, which felt completely wrong at first. I did three things that changed everything:

1. I stopped coding.

2. I admitted I didn’t know enough.

3. I gave myself space to learn.

   
   

I spent ten days on research with zero lines of code. This was my Mindset Shift. What if slower is actually faster? What if I needed to learn more before coding?

This unconventional strategy went against the hustle culture that says to code harder and ship faster. Instead, I gave myself permission to step back. I dove deep into Salesforce authentication architecture.

I discovered that session authentication requires a specific chain. It starts with a new tab, goes to the host domain, converts to the old domain, enhances the domain, extracts the session ID, and then uses the SID for authentication. Each domain has different rules. You can’t just grab a session ID and expect it to work.

I mapped everything out and documented my findings. It felt slow and unproductive, but I was finally moving in the right direction.

The Rebuild of My Chrome Extension: Clarity Unlocked Speed

Version 2 of my extension wasn’t built on hope. It was built on a solid system. I applied three more FORMULA principles:

1. Outcome vs. Process: I built a process first. Linear tickets became my system for breaking down work.

2. Routines & Rituals: I created a daily workflow ritual:

3. Morning: Review tickets.

4. Afternoon: Write specs for new features.

5. Evenings & Weekends: Let Claude Code execute the clear tasks.

6. Flexibility: When a ticket didn’t work, I adjusted the spec instead of forcing the code.

   
   

I created ten feature tickets. Each had 2-3 tasks with clear acceptance criteria. The authentication flow looked completely different this time:

Version 1 approach:

• "Build auth" → vague conversation with Claude → code → debug chaos → repeat.

  
  

Version 2 approach:

• Ticket 1: Research Salesforce domain conversion rules (spec complete).

• Ticket 2: Implement SID extraction logic (build with context).

• Ticket 3: Test cross-domain authentication flow (verify it works).

  
  

I connected Linear to Claude Code through MCP. The tickets became specifications, and the specifications became implementation.

Here’s the time breakdown that tells the whole story:

• Version 1: 21 days of coding → 0 working extensions.

• Version 2: 10 days of research + 14 days of structured building → 1 working extension.

  
  

The paradox was clear. The ten days I spent "doing nothing" made the next 14 days actually work.

The Principle: AI Forces Clarity

This experience wasn’t just about a Chrome extension. It was about how AI development works. AI agents don’t eliminate thinking; they reveal when you haven’t done enough of it. Claude Code can build anything if you tell it what to make clearly enough.

The paradox is that AI tools promise speed, but they require upfront clarity to deliver it. You can’t skip the thinking; you can only choose when to do it.

In Version 1, I tried to think while coding. It was chaos. In Version 2, I thought first, then coded. It was clean and efficient.

This is Adaptation & Action in practice. One failure taught me a system I now use for everything:

• Salesforce automation: Spec the flow before building it.

• Agentforce sub-agents: Map the orchestration before coding.

• Any agentic workflow: Specification-first beats code-first.

  
  

The shift from code-first to spec-first changed my entire development approach.

What I Learned About Paradoxical Productivity

This story aligns with every principle in the FORMULA I am building this year:

• F (Flexibility): I had to break my code-first habit and pivot my approach.

• O (Outcome vs. Process): Building a system delivered what forcing an outcome never could.

• R (Routines & Rituals): Linear + MCP + Claude Code became my repeatable workflow.

• M (Mindset Shift): Slower felt wrong, but turned out to be the only thing that worked.

• U (Unconventional Strategy): Ten days of "doing nothing" was doing everything that mattered.

• L (Life-Work Balance): Stepping back instead of grinding saved both the project and my sanity.

• A (Adaptation & Action): One failure taught me a framework I use every day now.

  
  

The ten days I spent not coding weren’t wasted time. They were an investment that made the next 14 days—and every build after—actually work. Paradoxical productivity isn’t just a theory. It’s what happens when you stop forcing speed and start building clarity.

Sometimes the fastest way forward is slowing down long enough to see the path.

Conclusion: Embracing the Journey

In the end, my journey taught me that productivity is not just about speed. It's about understanding the process, embracing flexibility, and allowing time for learning. I encourage you to reflect on your own projects. Are you rushing through tasks? Or are you taking the time to ensure clarity and purpose in your work?

If you liked reading this, I am sure you will love my newsletter, where I share deep dives on topics like Salesforce + Dev life, Tech & AI trends, Productivity experiments, Prompting techniques, New AI tools I test, and What's on my mind in tech, and it's free, no spam!

All you have to do is subscribe to get the good stuff in your inbox.