和 Author, 麥笛文（Stephen McDonell）,
这还要回到去年月之暗面在战略上的“急刹车”，其以海外市场为主，通过API调用带动收入，都是从去年开始逐步成型的。
。业内人士推荐快连下载安装作为进阶阅读
�@�G���^�[�v���C�Y������Kiro�̊g���@�\���Ǘ��ł����A�g���@�\���W�X�g���K�o�i���X�@�\�́AKiro���Г��p�̊g���@�\���W�X�g���Ɍ����邱�ƂŁA�Г��ŏ��F���ꂽ�g���@�\�����𗘗p�\�ɂł����A�Ƃ������̂ł��B
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.