36 'AI Programming 2.0' Dedicated Debugging Commands. This post is worth 20 RMB; sharing 2 dedicated debugging commands. (Why included in AI Programming 2.0? Because debugging is necessary regardless of the version.) I've used the first one myself for half a year; a colleague even solved a bug in 1 hour that they couldn't fix in 2 days using this command—he's a C++ developer. The second one is an original from today, and it works quite well, so I'm sharing it too. Without further ado, here are the commands (as usual, based on RIPER-5 Rules): Effect of Command 1: Dedicated Debugging Command
36 'AI Programming 2.0' Dedicated Debugging Commands This post is worth 20 RMB; sharing 2 dedicated debugging commands. (Why was it selected for AI Programming 2.0? Because debugging is necessary regardless of the version.) I've used the first one myself for half a year; a colleague even solved a bug in 1 hour that they couldn't fix in 2 days using this command—he's a C++ developer. The second one is an original from today, and it works quite well, so I'm sharing it too. Without further ado, here are the commands (note, as usual, based on RIPER-5 Rules): Effect of Command 1: Dedicated Debugging Command 1: Specializes in intractable issues, with excellent results for complex bugs. Combining relevant code, repeatedly perform analysis-hypothesis-verification-exclusion on the problem phenomenon, and write the process and conclusions into a file until the conclusions converge to 1-2 possibilities RESEARCH The core of this command is telling the AI the human approach to debugging...
No comments yet. Be the first to share your thoughts.