Conversation

Notices

1. Embed this notice
   Matthew Lyon (mattly@hachyderm.io)'s status on Wednesday, 10-Sep-2025 01:33:11 JST Matthew Lyon

   I said this when I first started getting into electronics and I’ll say it again:

   software libraries need something akin to Datasheets. A technical document which lists facts about the operating parameters and intended uses, meant for a technically-minded person to evaluate “is this suitable for my use case?” and “what all would be involved in integrating this into my product?”

   in my experience too much of this material for software reads like marketing fluff, making empty promises about ease or scale or whatever without any context under which those promises apply

   we talk about software “engineering” and this sort of technical document strikes me as fundamental to that practice

   • Embed this notice
     Jonathan ‘theJPster’ Pallant (thejpster@hachyderm.io)'s status on Wednesday, 10-Sep-2025 01:59:30 JST Jonathan ‘theJPster’ Pallant

     in reply to

     • Matt Campbell

     @mattly @matt I try my best. https://docs.rs/cortex-r-rt for example.

   • Embed this notice
     Bradalot “:verified:” (bradr@infosec.exchange)'s status on Thursday, 11-Sep-2025 02:58:21 JST Bradalot “:verified:”

     in reply to

     @mattly

     Consider: Having good product or component datasheets is downstream from holding product liability and warranty exposure.

     Since software is subject to neither of the latter, it will not create either of the former.

   • Embed this notice
     Bradalot “:verified:” (bradr@infosec.exchange)'s status on Thursday, 11-Sep-2025 03:26:27 JST Bradalot “:verified:”

     @mattly

     I think I get it (not sure). You're saying "make datasheets".

     And I'm saying (too boldly) "Enact software liability, and datasheets will make themselves."