Comment by cyrusradfar

3 days ago

That's really insightful. I think the goal is faster comprehension for the developer. Whether it's a PR in an area of code you haven't seen in a while and you want a refresher, a bug that you have no clue where to start, or you're onboarding -- in all cases, you can't start without a mental model of what's going one.

I'm solving may be for folks like me who would prefer to have the guide IN CODE. It's a new experience to me as I've never used an in IDE code tour.

I think what I'm experiencing is it's way more helpful for me to have the guide navigate through code so I can explore a little at each step and get a lay of the land.

How people learn is personal, and what I hoped for when I was building this was more of an experience where I'm walking through with a teammate.

I considered trying to have a voice AI read or explain each step. I also considered allowing another person to drive your IDE through mirroring what they're looking at. Both were cut at the idea phase because it felt it was feature bloat on a concept that I didn't know anyone (but me) really wants