But before we jump into those challenges, lemme give you a quick tour of how the game works and how it’s architected.
This story was originally featured on Fortune.com
，推荐阅读搜狗输入法2026获取更多信息
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.
good estimate of the slice size ahead of time. But hopefully the
Your content outline should reflect these natural queries in your subheadings and section structure. This organizational approach simultaneously improves readability for humans scanning your content and makes it easier for AI models to identify which sections answer specific questions. When someone asks an AI about project management tool features, a model searching your content can quickly locate and cite the relevant section because you've structured it logically around that question.