Skip to main content

39 bug = Small Requirement? Completely Wrong!

Paid1999-12-31

39 bug = Small Requirement? Completely Wrong!

39 bug = Small Requirement? Completely Wrong!

Last year doing AI efficiency improvement, when feeling our way across the river, everyone for a while reached a consensus: bug = small requirement

Now looking back, isn't this a joke?

Wrong because this thing is said backwards, bug is much harder to deal with than small requirement

From result perspective, for investigating bug solving bug I will bring out strongest model, for writing most requirements using claude without thinking is enough

Why is this?

Because solving bug's requirements are much higher than doing requirements, let's break it down

Solving bug breakdown actions:

  1. Understand bug phenomenon, map to product functionality

  2. Infer bug cause based on common sense: preliminary judgment whether it's front-end problem, whether it's my problem, whether it's historical problem

Purchase required to continue
This is a paid article. After signing in, your purchase will be unlocked automatically.
Buy now

Comments

No comments yet. Be the first to share your thoughts.

Leave a comment