Each of our services exposes an OpenAPI Swagger endpoint in our internal development environments. This endpoint serves a JSON response that defines the full API specification for all operations the service supports. During the live game’s development and operation, we used this to generate the C++ code for making calls to the backend, significantly cutting down on boilerplate coding tasks around defining request/response structs and JSON serialization/deserialization.
During development I encountered a caveat: Opus 4.5 can’t test or view a terminal output, especially one with unusual functional requirements. But despite being blind, it knew enough about the ratatui terminal framework to implement whatever UI changes I asked. There were a large number of UI bugs that likely were caused by Opus’s inability to create test cases, namely failures to account for scroll offsets resulting in incorrect click locations. As someone who spent 5 years as a black box Software QA Engineer who was unable to review the underlying code, this situation was my specialty. I put my QA skills to work by messing around with miditui, told Opus any errors with occasionally a screenshot, and it was able to fix them easily. I do not believe that these bugs are inherently due to LLM agents being better or worse than humans as humans are most definitely capable of making the same mistakes. Even though I myself am adept at finding the bugs and offering solutions, I don’t believe that I would inherently avoid causing similar bugs were I to code such an interactive app without AI assistance: QA brain is different from software engineering brain.，这一点在safew官方版本下载中也有详细论述
claude-file-recovery。旺商聊官方下载对此有专业解读
Continue reading...