• 646 Posts
  • 1.49K Comments
Joined 3 years ago
cake
Cake day: June 16th, 2023

help-circle



  • If a physics simulation doesn’t agree exactly with experimental data, it is often difficult to figure out why and tweak the model until they agree. With AI, incorporating a few experimental examples into the training process is a lot more straightforward, and it’s not necessary to understand where exactly the model went wrong.

    That’s not too bad if it’s only ever used as a rough guide in the early stages of design, with proper testing done later. But do we trust corporations not to get lazy and pressure their engineers to skip the accurate tests altogether, especially when they can then brag to their investors that AI is replacing expensive engineer time? What would Boeing’s management want to do with this tech?




























  • From the article:

    Google says it’s removing XSLT to address security vulnerabilities. The underlying library that processes XSLT in Chrome (libxslt) is an aging C/C++ codebase with known memory safety issues. Chrome’s team argues that because only about 0.02% of page loads use XSLT, it’s not worth the maintenance burden.

    It’s debatable whether Google, with all its resources, really needs to do this, especially given that 0.02% of all page loads is still quite a lot. But there are certainly times when it’s better to just delete seldom-used old code from your project to lower the maintenance burden and reduce the surface area for attacks.






  • It’s not easy, particularly if you developed it and have spent months immersed in all the detail. To emerge from that and imagine coming to it as a new user is pretty hard. I don’t have much to add but I like your advice. I need to rewrite the docs for one of my projects and I’ll be bearing your points in mind.

    Maybe one other point I’d add is: have a clear idea of who you’re writing for, and have different levels and styles of documentation for different types of users. Don’t try to satisfy everyone in the same document. Divide the documentation up by intended readership.