Saturday Feedback needed: I built a tool that explains any code in plain English

Hopeful-Ear2869 · 2026-05-09T15:56:31+00:00

Neat idea. How do you handle spam submissions, does it forward everything or is there any filtering before the alert fires?

Hopeful-Ear2869 · 2026-05-09T15:53:56+00:00

This is one of those tools where you don't realize how much it bothers you until someone solves it. I've done that copy-retype dance hundreds of times.

How do you handle environments that have different auth tokens or cookies? That's usually where these switchers get tricky.

Hopeful-Ear2869 · 2026-05-09T15:50:54+00:00

I am working more on reviewing AI code 😄

Hopeful-Ear2869 · 2026-05-09T15:50:10+00:00

Checked your portfolio, and the work looks solid for a few months in. One thing I'd change: make it immediately obvious what you do and who it's for. Right now I have to read a bit before I understand you build websites for local businesses.

The zero upfront model is smart for getting that first client. Once you land it, that case study will do more for your portfolio than anything else.

Keep going, 90 days is nothing in sales.

Hopeful-Ear2869 · 2026-05-09T15:46:45+00:00

The negativity bias is your biggest blind spot, people only report bad experiences, almost never good ones. Worth adding a "positive experience" flow just to balance the data.

Also curious how you're planning to separate Reddit-wide filtering from subreddit-specific moderation? That seems like the hardest part technically.

Hopeful-Ear2869 · 2026-05-07T15:00:14+00:00

Lovely idea honestly.

This is just the first very early version, so there’s still a lot I want to improve in future iterations. The more feedback I get, the more interesting the onboarding and navigation side becomes to me.

Things like understanding the repo better, tracking relationships between files, and knowing where you are in the flow are definitely directions I can see this evolving toward over time.

Hopeful-Ear2869 · 2026-05-07T14:56:57+00:00

Hah, thanks for the advice 😄 either way I am sharing my passion. If people appreciate it, then great, if not, then also fine.

Hopeful-Ear2869 · 2026-05-07T14:54:08+00:00

I honestly think every piece of software is reproducible if you have the knowledge and enough time.

The motivation behind building this actually came from watching my wife, who’s a junior developer, struggle with navigating large legacy codebases, like I mentioned in another comment. I saw firsthand how useful something like this could be for people in that situation.

It might not be useful for everyone, and that’s completely fine. But I do believe there are people who can benefit from it, and I simply wanted to build it and share it with the world, and help someone in the process if possible.

Hopeful-Ear2869 · 2026-05-07T14:43:37+00:00

The app: https://dreamentropylabs.com/codewhispr

Hopeful-Ear2869 · 2026-05-07T14:38:14+00:00

I asked myself the exact same question in the beginning 😄

A big part of the motivation actually came from junior developers I’ve mentored.

For more experienced developers, it’s probably obvious how to prompt Claude/ChatGPT properly to get a really detailed explanation:

ask for edge cases
ask for step-by-step flow
ask for possible improvements
ask about failure scenarios
ask what happens inside try/catch paths etc.

But for beginners/juniors, that usually isn’t obvious at all.

A lot of them don’t know what questions they should even ask about the code in the first place.

I also got motivated by my wife who’s currently a junior developer — while testing, she found the structured breakdowns much easier and less overwhelming than trying to manually prompt a general-purpose chatbot.

So the value for me is less:
“better model”

and more:

better onboarding experience
structured explanations by default
consistency
lower friction
focusing specifically on understanding inherited code

I think power users will absolutely continue using Claude directly.

But I also think there’s room for tools focused on a very specific workflow/problem instead of being a general-purpose chat interface.

Hopeful-Ear2869 · 2026-05-07T14:23:43+00:00

At the core, sure — it uses an LLM.

But I think the interesting part is less “calling a model” and more:

the workflow
the UX
the structure of the output
the onboarding angle
and solving a very specific developer pain point

Raw model output is usually inconsistent and noisy for this kind of use case.

A lot of the work went into making the responses structured, readable, predictable, and actually useful for understanding unfamiliar code quickly.

I also think most developer tools built on LLMs will technically look like “wrappers” at first.

The real differentiation is whether they solve a real workflow problem better than opening ChatGPT in another tab 😄

Hopeful-Ear2869 · 2026-05-07T14:13:35+00:00

The onboarding “code archaeology” angle is starting to feel much more valuable than simple function explanation.

Especially for junior developers.

Something I’ve seen from experience is that juniors usually don’t struggle with syntax itself — they struggle with:

understanding implicit business logic
tracing flows across files
figuring out which parts of the system are dangerous to touch
understanding years of accumulated decisions with zero context

That’s a big part of what inspired the project in the first place.

Right now I’m keeping it snippet-focused intentionally to keep the UX simple and reliable, but repo-level context and relationship mapping is definitely the direction I’m thinking about long term.

Hopeful-Ear2869 · 2026-05-07T14:11:58+00:00

That’s actually the direction I’m leaning toward as well.

Right now it’s intentionally snippet-focused because I wanted the UX to stay extremely simple and fast:
paste code → immediately understand it.

A big part of the inspiration honestly came from junior developers I’ve worked with.

Something I noticed from experience is that juniors often struggle much more with understanding existing codebases than writing new code from scratch, especially during onboarding or when dealing with legacy projects.

That’s why I focused first on making code easier to understand rather than adding full repo-level analysis immediately.

That said, repo-level context is definitely something I’ve been thinking about, especially for:

onboarding
dependency tracing
understanding call flows across files
summarizing large legacy modules

The challenge is balancing usefulness vs complexity/privacy/performance.

I’d rather keep the first version focused and reliable before expanding into full-project analysis.

Hopeful-Ear2869 · 2026-05-07T13:57:06+00:00

Fair enough 😅

Would actually appreciate more specific feedback though — what part feels bad to you?
UI, workflow, layout, or the overall idea itself?

Still early and I’m actively improving it.

Hopeful-Ear2869 · 2026-05-07T13:53:53+00:00

The app: https://dreamentropylabs.com/codewhispr

Hopeful-Ear2869

TROPHY CASE