An AI agent coding skeptic tries AI agent coding, in excessive detail

· · 来源:tutorial资讯

NASA also moved up the launch of Crew-12 to replace the prematurely-returned astronauts. That team docked at the ISS on February 14 and are scheduled to stay on the space station for around eight months.

SpaceX rocket fireball linked to plume of polluting lithium

杭州。关于这个话题,WPS下载最新地址提供了深入分析

Josh walks two hours into the city centre for a food parcel

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.

The secret

There’s a whole ecosystem of secrets management tools — Doppler, Infisical, HashiCorp Vault, SOPS, dotenvx. They’re all good, and if you’re running a team of 50+ engineers you should probably be evaluating them.