31 Matching Annotations
  1. Jun 2026
    1. In testing with an RTX 5090, DiffusionGemma spits out around 700 tokens per second. With a single Nvidia H100 AI accelerator, DiffusionGemma can produce 1,000+ tokens per second.

      这是一个重要的性能数据声明,但缺乏详细测试环境信息。需要了解测试的具体设置、硬件配置、模型版本以及比较基准,以验证这些数字的准确性和可比性。

    1. what changed after the December 2025 model inflection , and why "spec to pull request" is now becoming a real production workflow.

      'Spec to pull request' as a production workflow means the human's job becomes writing requirements, not code — a complete inversion of the current engineering process. The December 2025 inflection point is significant: it marks when models became capable enough to close the gap between high-level intent and production-ready implementation without constant human steering.

  2. May 2026
    1. Sessions can run in parallel, can persist while your machine is off, and can be triggered from third-party apps, such as Slack (coming in June)

      文章提到Vibe的会话功能可以在机器关闭时保持状态,这是一个重要的技术特性,但没有提供具体的性能指标如会话持续时间、资源消耗或并行处理能力。与同类产品相比,这种持久化会话功能可以提高用户体验,但缺乏具体数据来评估其性能优势或资源效率。

  3. Apr 2026
    1. Unknown section heading | Preserve; do not error

      大多数人认为严格的格式规范应该拒绝未知或不合规的部分,以确保一致性。但作者选择保留未知标题而不报错,这表明设计系统应该允许扩展和进化,而不是被严格规范所限制,这是一种反直觉的开放性设计原则。

  4. Jul 2023
  5. Nov 2022
  6. Jun 2022
    1. Technical specs have immense benefits to everyone involved in a project: the engineers who write them, the teams that use them, even the projects that are designed off of them

      Benefits: 1. as developer, easy to solve problem 2. as team, easy to do team work 3. as Project manager, easy postmortems

  7. Feb 2022
  8. Jun 2021
  9. Nov 2020
  10. Jan 2020
  11. Nov 2019
  12. Oct 2019
  13. Sep 2019
  14. Apr 2019
    1. However, we found a few trade-offs when using clojure.spec: clojure.spec requires registering a spec for each key in every path that you care about in a data structure, which can be verbose, especially for deeply-nested data structures. We felt this pain the most when specifying the incoming webhook payloads from the providers. We didn't specify the full payloads, we only specified the values that we actually needed, some of which were nested 7-8 levels deep. To work around this, we used data-spec (part of the spec-tools project) to define the payload specs as a mirror of the shape of the actual data. clojure.spec's error output is concise, and it's not always immediately apparent where the validation failure is within the data, especially when validating a large data structure. To help with this, we used expound to generate friendlier error messages at the REPL and in tests.

      spec gotchas

    2. This system is the first significant project on which we have used clojure.spec, and it proved useful in a few ways: Specifying the inputs to each layer in one place made it easier to visualize the shape of the data as it flowed through the subsystem, and proved valuable when describing the behavior to other engineers.Instrumenting the inputs and outputs of our layer boundary functions (via Orchestra), during testing, enabled us to quickly catch cases where we deviated from the spec, allowing us to see the issue at that boundary instead of as a random error within the implementation. Validating the layer inputs against our specs in production allows us to quickly diagnose and isolate faults to the layer where it was triggered, and helps us catch when our assumptions about the shape of the webhook event are incorrect. Having specs allowed for more straightforward tests, since we didn't need to assert on the shape of the data.

      benefits of spec

    1. (defn- gen-string [chars] (gen/fmap str/join (gen/vector (gen/elements chars)))) (defn- gen-query-string [] (->> (gen/tuple (gen/not-empty (gen/string-alphanumeric)) (gen-string uri-chars)) (gen/fmap (fn [[k v]] (str k "=" v))) (gen/vector) (gen/fmap #(str/join "&" %)))) (defn- gen-method [] (gen/fmap keyword (gen/not-empty (gen-string lower-case-chars)))) (defn- gen-input-stream [] (gen/fmap #(java.io.ByteArrayInputStream. %) (gen/bytes))) (defn- gen-exception [] (gen/fmap (fn [s] (Exception. s)) (gen/string-alphanumeric)))

      nice lesson on generators

  15. Oct 2018
  16. Nov 2017
  17. Aug 2017
  18. Jul 2017
  19. Jun 2016