home.social

Search

61 results for “maggieb”

  1. Maggie Pruetzel wins IHSA golf title using same ball for two days

    Maggie Prutzel of Marquette tosses the golf ball she used the entire IHSA Clas 1A State Tournament – a…
    #Golf #News #altgame #news #sports
    europesays.com/golf/82059/

  2. Today is the birthday of F. Murray Abraham (1939), Maggie Blye (1942), Kevin Kline (1947), and Karen Austin (1950) toilet-guru.com/movie-stars.ht

  3. (this was in my drafts, but didn't go out!) Final (non-lightning) talk of the day, @MaggieFero explains the importance of good documentation practice, regardless of who is reading it.

  4. alojapan.com/1557851/raw-deal- Raw deal: Two sushi restaurants burglarized in 48 hours – KIRO 7 News Seattle #Cairo #ipads #jason #jason_schloss #jason_sloss #Kent #Kirkland #kyro_evans #local #maggie_barnett #news #northeast_116th_street #russell_road #sumo #sumo_sushi #sumo_sushi_grill #sushi? #video KENT, Wash. — Two Sumo Sushi restaurant locations in Kirkland and Kent were burglarized within approximately 48 hours of each other. Police are investigating both incidents

  5. Havering Launches 2026 Poppy Appeal as Mayor Leads Tributes to Armed Forces – The Havering Daily

    Havering’s Mayor, Councillor Maggie Themastoclis, led the launch of the 2026 Poppy Appeal at The Mercury Shopping Centre…
    #London #Britain #UnitedKingdom #UK #GB #England #Headlines #News #Europe #EU #Havering
    europesays.com/gbr/london/4355

  6. HSBC Debuts HKD Stablecoin RedCoin on PayMe, Reaching 3.3 Million Users — BigGo Finance

    HSBC launched its first Hong Kong dollar-backed stablecoin on Friday, putting a regulated digital token directly into the…
    #EuropeSays #Britain #Europe #EU #HSBC #AnchorpointFinancial #HKDAP #HongKongMonetaryAuthority #HSBCHongKong #johno’neill #LawrenceLi #MaggieNg #PayMe #RedCoin #StablecoinsOrdinance #standardchartered
    europesays.com/britain/149871/

  7. RE: mastodon.social/@RonJeffries/1

    Yesterday at , I mentioned that a relatively common AI tooling error is reversing negation... here's an example 😅

    (Thanks for sharing it, @ronkjeffries !)

  8. Now @kattni can edit circuitpython instructions on a phone

  9. PyScribBLE is @kattni 's Bluetooth Low Energy package supported by toga-code-editor (with syntax highlighting) and toga-console to run beeware on a tiny hardware device!

  10. In closing his talk, @andrew informs us all that mountain rescue in the US is always free, and they'd rather be called sooner than later if you think you might need it.

    As a security professional, please also notify us sooner than later if something feels weird, whether you clicked a link that felt wrong in retrospect or a process is suddenly taking an unexpected length of time. Most of us wanna help!

  11. CW: discussion of peril

    Software systems aren't just code. @andrew @

  12. CW: discussion of peril

    "Heroics hide process failures"; "every near miss is a massive gift to you" because you can learn and adapt without experiencing the full consequences of the incident. Avoid the same one happening twice if you can, though. - @andrew @

  13. CW: discussion of peril

    "It is human nature to ignore risk" and everyone does it all the time. You have to accept some amount of risk, but it's important to address head-on and acknowledge.- @andrew @

  14. "Clear leadership is critical": "rescue is not a democracy", advice must be considered but you need a clearly accountable individual who can make the call. You can't do everyone's thing every time. - @andrew @

  15. CW: discussion of peril

    Practice incident response, and practice it proportionate to how often that type of incident occurs (with some extra reps on higher-risk areas).

    Leave time in your schedule for problems to happen! If you're scheduled 100% of the time, you have no margin of error.

    Try to move slowly and steadily, with small, frequent releases. Big jumps are riskier.

    Have a safety culture: blameless is good, but also every single person must be able to call stop and *actually* cause an evaluation. That's not to say you should never tolerate risk, but that you should consider it carefully.

    - @andrew @

  16. CW: discussion of peril

    In software, we can limit the scope of what we collect, by not creating user data unnecessarily, for example. Also, we have the opportunity to cheaply roll back our mistakes. They're not literally set in stone like some other disciplines' mistakes may be.

    In mountain rescue, if there's a problem with a rope system for example, someone may already be over the edge and fully dependent on it, so you can't fix that. - @andrew @

  17. CW: discussion of peril

    Mountain rescue teams can help handle some risk by building a safety culture, training in advance, and having a clear chain of command to reduce duplication of work. - @andrew @

  18. CW: discussion of peril

    Andrew also introduces the risk matrix: likelihood of occurring and severity of consequences if it occurs. In mountain rescue, you're guaranteed high consequences and that it's dangerous (you didn't get called out to have tea).

    We also have risk in our codebases, but we can likely impact both the likelihood and the consequences, using some of the same levers that mountain rescue teams use. - @andrew @

  19. CW: discussion of peril

    Search and rescue doesn't use the helicopter as often as you'd think; it's more common to hike out and get someone. They do search (looking for someone missing), rescue (helping someone who needs it, whose location is known), and recovery (retrieving deceased people from the field).

    For mountain rescue specifically, you also describe by angle: flatland (no ropes), low angle (you need a rope, but it's not holding full weight), and high angle (your full weight is on a rope, like a rappelling example we saw). - @andrew

  20. Next, has @andrew, sharing about Mountain Rescue! The content has a content warning for general discussions of peril, which I'll put on the rest of this thread.

  21. Finally, @coderanger reminds to be kind, to ourselves and others

  22. Some of the ways we trust code review require hypervigilance, which leads to burnout. Hypervigilance also leads to cognitive overload, because you only have but so many things you can keep track of. - @coderanger at

  23. When we explicitly declare the purposes of our code review and choose specific smaller bits to look at, we can keep ourselves from trying to reconstruct the mental state of the developer, which is in turn one of the most effective ways to successfully accomplish large-scale code review. - @coderanger at

  24. Explicitly declaring types, staying consistent (and trying linters to ensure it), and other automation layers let us save the squishy bits for squishy humans with a nice firm safety net.

    Code review can also help, and it's one of the most common ways we often assess each other's code. Code review is a way to reduce defects, but it's also good for team training, architecture consensus, and specialist consultation. HOWEVER, it's easy to miss things; code review isn't great at finding defects! It can also be time-consuming and timing, in a way that gives people a reduced sense of agency. - @coderanger

  25. Unit tests are subjective, and so is coverage reporting. Make those decisions deliberately and thoughtfully.

    Instead of overall coverage, @coderanger likes patch coverage: what's the difference in test coverage before versus after this change? if it's not enough, get curious about why important-seeming code doesn't look tested.

  26. Creating a checklist culture, like @coderanger learned as a diver and practices in frequent, repetitive, high stress, or high-impact-of-errors situations, can help us move through processes in a streamlined way and reduce human error. That checklist must be followable, explicit, and shouldn't have a lot of steps people are expected to skip.

    You've got to practice that checklist, though! It should be routine by the time it matters.

    Finally, checklists must be blameless. Failures after following the checklist are a problem with the process, not the person.

  27. One of the ways that @coderanger , as a human, is bad at things, is a way we're all bad at things, too! Confirmation bias is a form of cognitive shortcut that can save us time, but can also cause predictable problems.

    inattentional blindness is when we remember only what we were paying attention to, and miss something important.

    Recency bias causes us to map things to recent events, repetition blindness keeps us from noticing "boilerplate", and overconfidence bias in many forms is SUPER prevalent in tech.

Share on Mastodon

Enter the server where you have an account.