• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle








  • I just had to switch to New Teams last week because Classic teams just continued to have more and more call drops and connection problems. The New Teams doesn’t even have an option to change the notification sound, and now I can’t move the banner that appears in the top center of the screen when screen sharing that covers up tabs in browsers and the main preferences/search dialog in VS Code…also a Microsoft product. Apparently no one at Microsoft noticed that one of their most used products used in the most normal way blocks out important functionality from another one of them.






  • seth@lemmy.worldtoMemes@lemmy.mlCrackers
    link
    fedilink
    arrow-up
    7
    ·
    9 months ago

    I read it as a helpful cue to shore up the small discordant point in the relationship, with saltine goodness and a little brainstorming on ways to improve the crackerage. Couples who cracker together, something something.





  • The Arch wiki is one of the most impressive documentation resources I’ve seen and I’ve only [needed to] scrape the surface so far. Almost every minor unexpected issue I ran into along the way had a detailed solution and the only issue I haven’t been able to resolve is getting all the buttons on my mouse to work…but did find out it’s Logitech’s weird receiver codes that are the issue and they don’t release drivers for Linux.


  • In many of them but not all, because it’s become convention and has been enshrined in their documentation policies. cGMP just requires that your quality management system has a policy in place that specifies how to document the date, and when exceptions are allowed (for instance, data printouts where YYYY-MM-DD is often the default).

    It’s also the reason some labs require you to initial/date every page of printed data, and some only require you to initial/date the first and/or last page. I’ve seen FDA auditors be okay with both, as long as you can justify it with something like: our documentation policy defines the printout as a copy of the original data, and the original data as what’s stored on machine memory with electronic signature; versus: our documentation policy defines the original signed/dated data printout as the original data. In any case, it still has to follow 21 CFR part 11 requirements for electronic records & signatures, where the only date predicate rule example they give is 58.130(e), which itself is broad and only applies to non-clinical lab studies. It’s notable that the date format 21 CFR 11 itself uses is actually Month D, YYYY, with no zero padding on the day.

    And if you don’t have IQ/OQ/PQ documentation showing how you locked down and validated the software’s ability to maintain an audit trail you can’t even use electronic records (or signatures).