Раскрыт мотив изрезавшего молодого россиянина у метро мужчиныВ Москве арестован подозреваемый в убийстве молодого мужчины у метро «Сокол»
В России изменились программы в автошколах22:30
，详情可参考新收录的资料
Play video, "中日關係趨緊：高市早苗「台灣有事論」引北京強烈反彈 日本外務省官員赴華磋商", 節目全長 3,37
开发「语音模式」的时候以为用户能像 Tony Stark 一样，在一个独立的办公区，向 AI 说一堆炫酷的词语，然后 AI 就把你的想法准确无误地实现出来。但实际情况是，一群 i 人牛马在拥挤的办公室里把键盘都敲烂了，AI 还是只能回答一句“你说得对，我应该......”，最后牛马一个上午开口说的唯一一句话是“傻X”。
。关于这个话题，新收录的资料提供了深入分析
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.
�@CP�{�̉����́A���{�̎��v�J�������[�J�[�i�ߔN�A���R�[���Q�����ĂȂ��̂��c�O�ł����j�����v�����Y�u�����h�������ȃu�[�X���\���A�����ȊO�̏ꏊ���l�X�ȃJ�����E�ʐ^�֘A�u�����h�����߂��Ƃ��������B。新收录的资料对此有专业解读