WhyLog

I’ll be honest posting this is terrifying.

For the last few months, I’ve been living in my code. I’ve spent countless late nights building WhyLog because I was convinced I had found a universal pain point: the "Knowledge Debt" that kills engineering teams when a key developer leaves.

I knew the problem. I felt the pain. I built the solution.

But here is the reality: Right now, I have zero users and zero revenue.

It’s a strange feeling. You spend hundreds of hours building something you truly believe in, and then you realize that "believing in it" and "getting people to use it" are two completely different skill sets.

There are days when I look at my empty dashboard and wonder if I’m just delusional. Maybe engineers don't actually care about documentation. Maybe the "Ask Ahmed" problem isn't a problem people are willing to pay to solve.

But then I remember the feeling of staring at a legacy codebase, knowing the person who wrote it is gone, and feeling completely lost. I remember how much time is wasted in Slack threads trying to reconstruct a decision from three years ago.

I know the pain is real. I just don't know if I'm the only one who feels it.

So, I’m putting myself out there. Not with a polished marketing pitch, but with a request for honesty.

If you've ever felt that frustration—or if you think I'm totally off base—could you tell me? I’m not looking for "polite" feedback; I’m looking for the truth.

If you're curious, it's at https://whylog.nubrotech.com. But if you just want to tell me I'm not crazy for trying this, that would mean the world to me too.

Hey Indie Hackers

I've spent the last few years watching engineering teams silently lose something incredibly valuable: the reasoning behind their own code.

Not the code itself but the WHY.

• Why did we pick PostgreSQL over MongoDB?

• Why is there Redis in the auth flow?

• Why does this "temporary" workaround still exist 2 years later?

The answer is usually: "Ask Zain." But zainleft the company six months ago.

The Uncomfortable Truth:
Every team knows this is a problem. Every team tries to fix it with Wikis, ADRs, or Notion docs. But they all fail for the same reason: Documentation requires a behavior change.

Engineers are under deadline pressure. Asking them to stop their flow to write a doc is a losing battle. Behavior change doesn't survive a sprint deadline.

So, I stopped trying to change engineer behavior.

I built WhyLog to capture decisions passively, from work the team is already doing.

The workflow is dead simple:

1. Connect your GitHub repo.

2. Merge PRs like you always do.

3. When a meaningful PR is merged, WhyLog’s AI analyzes the code changes, the description, and the discussion. It then drafts a decision record (The "What," the "Why," the tradeoffs, and the affected files).

4. You get a Slack notification. One click to approve. Done.

Six months later, when a new engineer asks why you switched to session cookies, they don't hunt through 2022 Slack threads. They search WhyLog and get the exact reasoning and the original PR link in seconds.

What’s under the hood:

• GitHub Integration: Automatic PR capture.

• Gemini-powered AI: To draft the decision logic.

• Slack Workflow: For low-friction approval.

• Semantic Search: Ask questions in plain English.

I’m currently offering a free plan (no CC required) to get more teams onboard.

I'd love the IH community's take on this:
For those of you leading teams or scaling products what is the one decision in your codebase that you wish was documented, but isn't?

Check it out here: https://whylog.nubrotech.com