Is DSA 100 Days better than LeetCode?

DSA 100 Days offers unlimited AI tutoring and mock interviews at $59/year, compared to LeetCode Premium at $159/year without AI features. It's designed for focused 100-day preparation rather than overwhelming you with thousands of problems.

How long does it take to prepare for coding interviews?

With DSA 100 Days' structured curriculum, most users complete their preparation in 100 days, solving one problem per day. The AI tutor helps you understand concepts faster than self-study.

What programming languages are supported?

DSA 100 Days supports Python, JavaScript, TypeScript, Java, C++, and Go with in-browser code execution and AI tutoring in all languages.

Building in Public: Why I'm Sharing This Journey

Day 5. Time for some meta-reflection.

Why am I writing these daily entries? Why share the journey publicly instead of just building in private?

The Scary Part

Here's what I'm risking:

**Public failure.** If DSA 100 Days doesn't work out, everyone will know

**Looking stupid.** Some of my early decisions will probably be wrong

**Vulnerability.** Sharing failures and struggles isn't comfortable

So why do it?

The Benefits

1. Accountability

When I tell people I'm going to ship something, I actually have to ship it. No more "I'll start that side project eventually."

2. Feedback Loop

I'm getting feedback from day 1, not after building for 6 months in isolation. If my approach is wrong, I'll find out now.

3. Marketing Built In

Every journal entry is content. Every tweet about the journey is marketing. I'm building an audience while building the product.

4. Connecting with Others

The responses I've gotten have been incredible. Other engineers saying "I struggled with the same thing." People offering to be beta testers. Connections I never would have made building alone.

What I'm Committing To

**Daily journal entries** (like this one)

**Weekly progress updates** with actual numbers

**Monthly retrospectives** on what worked and what didn't

**Total transparency** on revenue, users, decisions

The Philosophy

I believe the best way to build trust is to show the journey, not just the destination.

Anyone can post a success story after they've made it. "I built X and got Y users!" But those stories skip the messy middle.

I want to show the messy middle. The days when nothing works. The decisions that seem obvious in retrospect but weren't at the time.

If DSA 100 Days succeeds, you'll have seen the full journey. If it fails, at least you'll know why and learn from my mistakes.

A Request

If you're following along, I'd love to hear from you.

What topics do you want me to cover?

What's your biggest struggle with interview prep?

Would you be interested in beta testing?

DM me on Twitter or reply to any of these posts.

Tomorrow: The mindset difference between imposter syndrome at work vs. in interviews.

— Marcus