Юлия Мискевич (Ночной линейный редактор)
2月27日，魅族科技微博发文回应手机退市谣言：亲爱的魅友和关心魅族的各界朋友们，近日互联网上关心魅族的声音持续发酵，产生了很多错误解读。在此郑重通告，对于网上关于魅族公司“破产重组，业务停摆，手机退市”等谣言和不实报道，我们将坚决追究造谣及传谣者的法律责任，守护清朗网络空间。
，推荐阅读旺商聊官方下载获取更多信息
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.
Жители Санкт-Петербурга устроили «крысогон»17:52