尼采式调试器
Nietzschian Debugger

原始链接: https://github.com/DilawarShafiq/nietzschian-debugger

Nietzschian Debugger 是一个从不提供修复方案的 CLI 调试工具;相反,它通过提出尖锐问题帮助开发者自行发现根因。可通过 npm(Node.js 20+)或 Python 3.10+ 获取,需要 Anthropic API 密钥。用户可从三种强度——苏格拉底、尼采或查拉图斯特拉——中选择,并可引用真实代码文件。它会在本地保存会话、总结长对话并追踪调试技能增长。示例展示了四个问题如何引导开发者从“部分用户出现 403”定位到因最近 TTL 变更导致的 JWT 令牌过期。专为希望提升调试直觉而非快速复制粘贴答案的开发者和团队而构建。采用 MIT 许可证。

Hacker News 上的一篇帖子宣布 GitHub 项目 “Nietzschian Debugger” 获得 20 分。评论者关注的不是功能,而是其品牌和 AI 使用。有人指出尼采曾批评苏格拉底辩证法;其他人建议阿多诺或黑格尔作为更好的调试哲学隐喻。多人指出 “反 AI” 标签与需要 Anthropic API 密钥,以及 AI 生成图像、README、代码和 LLM 输出的证据相冲突。有人认为项目根本不应以哲学家命名,而另一些人则开玩笑说即使是反 AI 工具如今也在使用 AI。少数人询问它是否可以简单地作为一项技能实现。总体而言,讨论突显了对项目身份和命名的怀疑,以及对 “反 AI” 意味着无用助手而非无 AI 的困惑。
相关文章

原文

Nietzschian Debugger: the debugger that only asks questions

"What doesn't kill your code makes it stronger."

The anti-AI. Every other tool gives you answers. Nietzschian Debugger confronts you with questions.

You paste your bug. It doesn't fix it. Instead, it:

  • Challenges your assumptions about what's happening
  • Forces you to confront the evidence you're avoiding
  • Tears apart your weak reasoning until only truth remains
  • Guides you to the "aha!" moment — YOUR moment, not the AI's

AI is making developers weaker. Copy-paste from ChatGPT, ship, repeat. Nobody understands their own code anymore. Nietzschian Debugger forges stronger developers — through struggle, not shortcuts.

"He who has a why to debug can bear almost any how."

# Published release (npm, v0.1.0)
npx nietzschian-debugger

# Current source (Python 3.10+)
pip install git+https://github.com/DilawarShafiq/nietzschian-debugger.git
nietzschian debug "your bug"

Requirements:

  • Node.js >= 20 for the npm release, or Python >= 3.10 for the current source
  • An Anthropic API key (BYOK — bring your own key)

Set your Anthropic API key:

# Linux / macOS
export ANTHROPIC_API_KEY="sk-ant-..."

# Windows (PowerShell)
$env:ANTHROPIC_API_KEY = "sk-ant-..."

# Windows (CMD)
set ANTHROPIC_API_KEY=sk-ant-...
# Start a debugging session (default: nietzsche intensity)
nietzschian debug "My API returns 500 but only on Tuesdays"

# Gentle mode — for when you need guidance, not punishment
nietzschian debug --intensity socrates "My login endpoint fails randomly"

# Maximum intensity — for seniors who want pain
nietzschian debug --intensity zarathustra "Memory leak in production"

# Point it at specific code
nietzschian debug "Auth fails in ./src/middleware/auth.ts"
Level Style Best For
socrates Warm, guiding, scaffolded questions Juniors, learning fundamentals
nietzsche Direct, confrontational, no hand-holding Daily debugging (default)
zarathustra Brutal, adversarial, hostile to weak reasoning Seniors who want real pain
  Nietzschian Debugger v0.1.0 — intensity: nietzsche

You: My login endpoint returns 403 for some users

Nietzschian: You say "some users." That's vague. What separates
             the ones who fail from the ones who don't?

You: I'm not sure, it seems random

Nietzschian: "Random" is the word we use when we haven't looked
             hard enough. What do the server logs say for the 403
             responses? Go look. I'll wait.

You: Let me check... oh, they all have expired JWT tokens

Nietzschian: Now we're getting somewhere. Why would some users
             have expired tokens while others don't? What changed
             recently in your auth system?

You: ... oh. We changed the token TTL last week and didn't
     invalidate existing sessions.

Nietzschian: There it is. You didn't need me to tell you — you
             needed to be forced to look.

Session Complete — 4 questions to root cause (Solved)

Your Debugging Profile:
┣ Assumption-checking    ██████████  strong
┣ Evidence-gathering     ██████░░░░  moderate
┗ Root cause speed       ████████░░  strong

"Man is something that shall be overcome."
 — Friedrich Nietzsche
Command Effect
solved or found it End session — you found the root cause
I give up Get one lifeline question, then exit
exit or quit Abandon session immediately
Ctrl+C / Ctrl+D Force quit
  • Never Gives Answers — Every response is a question. The tool will NEVER tell you the fix.
  • Real Code Reading — Reference a file path and it reads YOUR actual code, not generic examples.
  • Contextual Philosophy — Nietzsche when you're avoiding, Seneca when overwhelmed, Sun Tzu when you need strategy.
  • Growth Score — Track your debugging skills across sessions with visual bar charts.
  • Session History — All sessions saved locally in .nietzschian/sessions/ for trend tracking.
  • Sliding Context — Long sessions don't crash; older turns are transparently summarized.
Traditional AI Nietzschian Debugger
"Here's the fix" "What have you tried?"
Makes you dependent Makes you dangerous
You learn nothing You learn everything
Fast but shallow Painful but permanent
AI gets smarter YOU get smarter
  • Junior developers who want to actually learn, not just copy-paste
  • Senior developers who miss the struggle that made them good
  • Engineering managers who want their team thinking, not just prompting
  • Bootcamp students building real debugging intuition
  • Anyone who believes the best developer is a self-reliant one
# Clone and install
git clone https://github.com/DilawarShafiq/nietzschian-debugger.git
cd nietzschian-debugger
pip install -e ".[dev]"

# Run tests (121 tests)
pytest

# Run the CLI locally
nietzschian debug "test problem"
  • Python >= 3.10
  • Claude API via the Anthropic SDK
  • Click for the CLI, Rich for the terminal UI
  • pytest for testing

MIT

联系我们 contact @ memedata.com