home.social

#specifications — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #specifications, aggregated by home.social.

fetched live
  1. That is not to say that #DefenceProjects never suffer changes in #Requirements and #Specifications, or don’t have to contend with #ProjectCreep and #BudgetOverruns. In fact those are quite common. The real issue here is #Secrecy and #MixedMessages neither of which will shore up our trust in the knowledge that the people in charge know what they’re freeking doing. (NOTE: All the while consultants are lining their pockets and are as happy as pigs in mud).

  2. That is not to say that #DefenceProjects never suffer changes in #Requirements and #Specifications, or don’t have to contend with #ProjectCreep and #BudgetOverruns. In fact those are quite common. The real issue here is #Secrecy and #MixedMessages neither of which will shore up our trust in the knowledge that the people in charge know what they’re freeking doing. (NOTE: All the while consultants are lining their pockets and are as happy as pigs in mud).

  3. Cp and Cpk are parts of a method/tool in Six Sigma to determine whether requirements are within the mean or client/customer requirements/specifications. I'm working on Six Sigma training that I'll have available on Udemy. #sixsigma #quality #business #requirements #specifications

  4. Cp and Cpk are parts of a method/tool in Six Sigma to determine whether requirements are within the mean or client/customer requirements/specifications. I'm working on Six Sigma training that I'll have available on Udemy. #sixsigma #quality #business #requirements #specifications

  5. @Moss_the_TeXie @EUCommission
    If there is no chip in the cable, PD does not work and the limit is 3A and 5V

    But don't worry the laws to use #usbc are made by #eu politicians the technical #specifications are made by #engineers
    So, trust my colleagues!

  6. 昨年10月に発表されていた通り、電子情報技術産業協会 #JEITA が発行する「JEITA規格」の販売は4月1日から日本規格協会 #JSA に移行した。電子版JEITA規格の販売も開始。JEITA規格のウェブページは jeita.or.jp/japanese/public_st に告知。
    #Standards #Specifications

  7. @jasongorman

    Specs?
    Kids these days are spoiled.

    Back in the days when I was a codemonkey we had to read the clients mind with our psionics...
    ...and I am only half joking.

    One day my boss wrote an entire sentence of a spec for a whole module and I kept the dinner tissue as a memento of happy days when specs were hardcoded!

    #specifications #codemonkeys

  8. This #guide provides a #framework for writing effective #specifications for #AIcodingagents. It emphasises starting with a high-level vision and letting the AI draft the details, structuring the spec like a professional PRD, and integrating the spec into the development toolchain. The guide also highlights the importance of planning, breaking tasks into smaller chunks, and continuously iterating on the spec and implementation. addyo.substack.com/p/how-to-wr #AIagent #AI #ML #NLP #LLM #GenAI

  9. This #guide provides a #framework for writing effective #specifications for #AIcodingagents. It emphasises starting with a high-level vision and letting the AI draft the details, structuring the spec like a professional PRD, and integrating the spec into the development toolchain. The guide also highlights the importance of planning, breaking tasks into smaller chunks, and continuously iterating on the spec and implementation. addyo.substack.com/p/how-to-wr #AIagent #AI #ML #NLP #LLM #GenAI

  10. Announcement

    The XSF is considering to participate the Summer of Code 2026!

    If you are interested as a contributor or mentoring project start reading here:
    wiki.xmpp.org/web/Google_Summe

  11. #XSF Announcement

    The XSF is considering to participate the #Google Summer of Code 2026!

    If you are interested as a contributor or mentoring #XMPP project start reading here:
    wiki.xmpp.org/web/Google_Summe

    #GSoC #chat #messaging #jabber #standards #opensource #interoperability #rtc #specifications

  12. Reading posts about #LLM from management folks, I think they have forgotten the basics such as
    1. #productivity != gains,
    2. #specifications are hard to get right,
    3. English (natural language) is less precise than #programming #languages, and
    4. gains are almost always unrealized due to chasing wrong goals.

  13. Reading posts about #LLM from management folks, I think they have forgotten the basics such as
    1. #productivity != gains,
    2. #specifications are hard to get right,
    3. English (natural language) is less precise than #programming #languages, and
    4. gains are almost always unrealized due to chasing wrong goals.

  14. Regular software assumptions don't apply to #ai:

    ❌ "#Software #vulnerabilities are caused by mistakes in the #code"
    ❌ "#Bugs in the code can be found by carefully analysing the code"
    ❌ "Once a #bug is fixed, it won’t come back again"
    ❌ "Every time you run the code, the same thing happens"
    ❌ "If you give #specifications beforehand, you can get software that meets those specifications"

    boydkane.com/essays/boss

  15. Regular software assumptions don't apply to #ai:

    ❌ "#Software #vulnerabilities are caused by mistakes in the #code"
    ❌ "#Bugs in the code can be found by carefully analysing the code"
    ❌ "Once a #bug is fixed, it won’t come back again"
    ❌ "Every time you run the code, the same thing happens"
    ❌ "If you give #specifications beforehand, you can get software that meets those specifications"

    boydkane.com/essays/boss

  16. Today I discovered an interesting inconsistency in Activity Streams specs while investigating a Fedify issue.

    The question: How should we interpret URLs like "icon": "https://example.com/avatar.png"?

    JSON-LD context (https://www.w3.org/ns/activitystreams): @type: "@id" → “This is an IRI reference, dereference it to fetch an ActivityStreams object.”

    Activity Streams Primer: “assume that a bare string is the href of a Link object, not an id” (no dereferencing)

    Result: JSON-LD processor-based implementations try to parse PNG files as JSON and fail.

    Turns out w3c/activitystreams#595 already discusses the same issue for href properties. I added a note that icon, image, etc. have the same problem.

    Once again reminded of how tricky spec work can be…

    #ActivityPub #Fedify #ActivityStreams #fedidev #specifications

  17. Note that file sharing and forums have existed for years in Libervia, in experimental form. Those have been useful to find the flaws and needs, and the acquired experience helped me to write those specifications.

    #XMPP #Libervia #Specifications #XEP