39 Matching Annotations
  1. Last 7 days
    1. Humans can be in the loop to grant permission and must accept Cloudflare's terms of service, but no human steps are otherwise required from start to finish.

      最佳实践是让代理自动化大部分部署流程,但关键步骤如用户同意服务条款仍需人工参与。

    2. These build on prior art and existing standards like OAuth, OIDC and payment tokenization —but are used together to remove many steps that might otherwise require a human in the loop.

      强调了现有标准和技术的融合使用,这是实现自动化流程的关键,同时也避免了过时的做法。

    3. Humans can be in the loop to grant permission and must accept Cloudflare's terms of service, but no human steps are otherwise required from start to finish.

      This emphasizes the best practice of automating processes where possible, reducing manual intervention and streamlining workflows.

    4. Humans can be in the loop to grant permission and must accept Cloudflare's terms of service, but no human steps are otherwise required from start to finish.

      最佳实践建议:自动化流程可以大幅提高效率,但人类审核和接受服务条款仍然是必要的。

    1. The feature can edit spreadsheets without a human-in-the-loop and was vulnerable to data exfiltration risks due to its ability to insert formulas that trigger external communication.

      最佳实践建议:在使用无需人工干预的AI工具时,应特别注意数据泄露风险。

    1. We approached this through caching, eliminating unnecessary network hops, improving our safety stack to quickly flag issues, and—most importantly—building a way to create a persistent connection to the Responses API, instead of having to make a series of synchronous API calls.

      最佳实践建议:通过缓存、减少网络跳数、改进安全栈和建立持久连接来优化性能。

  2. Apr 2026
    1. The result is a Skill that acts as a cheat sheet for the MCP, not a replacement for it. The MCP still handles the actual connection and tool execution. The Skill just makes sure the LLM doesn't waste tokens stumbling through the same pitfalls I already solved.

      这个发现令人惊讶且极具价值。作者提出了一个创新的使用模式:Skill作为MCP的'备忘录',两者形成互补而非替代关系。这种组合既利用了MCP的连接能力,又通过Skill避免了重复探索,代表了AI工具集成的最佳实践。

    1. errors in the spec would cascade into the downstream implementation.

      展现了Agent系统设计中的风险控制逻辑:过早陷入底层细节会导致错误级联。让Planner专注于高层目标,将实现路径留给执行层自主探索,有效避免了自上而下的规划谬误,增强了系统的容错性。

    1. The trick is to think about the _information_ first and the input method second.

      这是一个极具启发性的架构思维。开发者常陷入“怎么让用户输入”的交互细节中,却忽略了核心是“系统需要什么数据”。先定义数据契约,再适配输入方式(交互式、参数、配置文件),能瞬间解耦业务逻辑与交互层,大幅提升工具的可组合性。

  3. Feb 2025
  4. Jun 2021
  5. Jan 2021
  6. Oct 2020
  7. Sep 2020
  8. Apr 2020
  9. Jun 2018
    1. must keep the focus first on best practices

      Good practices? Here are a couple of critiques of the phrase best practices.

      1. When “Best Practice” is Bad Practice

      1. Best Practices Are the Worst

      Not trying to nitpick here, but as a teacher I find it more important to be able to look at any writing practice (digital or otherwise) and see how it fits my learners and our learning niche. I am always surprised at what works and what doesn't and how the trifling-est practice sometimes works. I understand, too, that the reason we propose 'best practice' and do research to determine what is best practice is to pare down on the universe of options available to us as teachers and learners. As an experiment ask a student what they might consider best practice for learning a particular thing and I think you might be surprised. Oh, right, students don't enter into best practice except as we practice it upon them.

  10. Oct 2017
    1. B

      I found myself thinking about the phrase "best practice" when reading this paragraph. All too often in my line of work we seem to be using that phrase more and more and it's beginning to feel like a new buzz word/phrase. The comment of the author "...they also distance us from our own instincts." really makes me stop and wonder about my intentions when saying it. Hmm...

  11. Feb 2017
  12. Dec 2016
    1. You can have a maximum of two access keys (active or inactive) at a time.

      Incredibly useful to have up to two access keys simultaneously. You can make sure a new key is working before invalidating an old key which may still be in use. I wish more API providers would follow this practice.

  13. Sep 2015
    1. When should I use an attribute versus an element? Use an element when you are creating a component that is in control of the template. The common case for this is when you are creating a Domain-Specific Language for parts of your template. Use an attribute when you are decorating an existing element with new functionality.