dysfun@treehouse.systems ("gaytabase") wrote:
chef specialising in weetabix
dysfun@treehouse.systems ("gaytabase") wrote:
chef specialising in weetabix
pzmyers@freethought.online ("pzmyers 🕷") wrote:
The lab spiders are so, so cold as the university fires up the AC in our building, and apparently designates my lab as the cooling sink for everything. I'm going to be cosplaying as James Hong all summer long.
The spiders don't like it.https://freethoughtblogs.com/pharyngula/2026/04/26/its-summertime-and-you-know-what-that-means/
"You have to consciously and deliberately maintain it, or it will dissipate."
Kattni emphasizes that this is not a simple story of having a problem and then fixing it and then it's fixed. Trauma responses don't just go away with a little bit of empathy. Trust is not permanent; it can be broken, it needs to be repaired:
"I went through being convinced that I couldn't do this, several more times…over time, though, the ups have begun to outnumber the downs.…This is a hard fought improvement. It came through both repeated successes and multiple mistakes."
Boosted by slightlyoff@toot.cafe ("Alex Russell"):
phae@status.fberriman.com wrote:
You guys seen this thing YesPress.io? It's a total scam?
They're just generating pages for people who didn't ask/permit (e.g. @slightlyoff below), and if you look for someone who isn't on there it messages like the other people are already on there and gives you FOMO ("their" = owner). So if you want to edit your own stuff or join the "cool" people, you have to sign up... which is $99... which they are insinuating everyone else must have already paid.
Scuzzy.
Kattni describes a pretty intense process of recovering from trauma around code review, with the BeeWare team's help, that is complex enough that it's hard to capture in some quick notes here, but it really emphasizes that OSS governance *is* the process of nurturing contributor relationships. And that process worked, because where it lead to was:
"Obviously the response to discovering trauma around contribution is to take on a massive complex contribution, right?"
soatok@furry.engineer ("Soatok Dreamseeker") wrote:
See also:
soatok@furry.engineer ("Soatok Dreamseeker") wrote:
Post-quantum cryptography landed in PHP before GnuPG
Boosted by soatok@furry.engineer ("Soatok Dreamseeker"):
0xabad1dea@infosec.exchange ("abadidea") wrote:
I know you kids these days like your neural networks *sits backwards on a chair* how about you open a book and train the original neural network :neodog_book:
Boosted by soatok@furry.engineer ("Soatok Dreamseeker"):
bagder ("daniel:// stenberg://") wrote:
"Pre-built GitHub profiles with five-year commit histories and Arctic Code Vault Contributor badges sell for approximately $5,000 on Telegram."
https://awesomeagents.ai/news/github-fake-stars-investigation/
Apropos of the conclusion of the previous talk — "Human practitioners are the adaptable element of complex systems." — we are introduced to a way that Russell recovered from an error, i.e.: the review process created some pretty severe and unpleasant code review anxiety, and he immediately apologized and adjusted his style as soon as he was made aware.
Setting up good processes is important but the *meta*-process being responsive to human input is even moreso.
Kattni recites a litany of reasons that @freakboy3742 is an open-source maintainer role model for me. The BeeWare sprint at PyCon 2024 was filled with joy, constant recognition of contributors' achievements, rewards (challenge coins, and I just failed a coin check). Achieving this sort of social milieu with the degree of intentionality that Russell does is really something to aspire to, and it is not easy.
fromjason ("fromjason.xyz ❤️ 💻 ✍️ 🥐 🇵🇷") wrote:
Day ruined.
Next up, @kattni with "Bumbling into BeeWare: From typo-fix to core developer". Definitely excited to hear about this!
Love to see @dreid getting an (implicit) shout-out from the stage as well, via a website you should all be familiar with, https://how.complexsystems.fail
Benno carefully emphasizes that he doesn't want to be engaging in language wars, and in the spirit of honoring that I won't over-emphasize this, but he has the same feelings (bad) that I have about the way that Go halfheartedly encourages you to handle errors with tuple returns, by allowing you to easily forget to handle them.
dysfun@treehouse.systems ("gaytabase") wrote:
there is something massive hidden under the moon's south pole
is it dr iwo robotnik's moon base?
"Exception handling requires runtime code"
- C++ requires a runtime (sometimes: if you're writing kernel code or some other no-runtime context you might have to write C++ in a dialect that is missing runtime-requiring language features)
- Python obviously in its own runtime
- Rust… has no runtimeSo: rust has no exceptions.
Rust has result types.
adele@social.pollux.casa ("Adële 🐁!") wrote:
What I hate when I need to install #Linux on a machine
"[errno] hopefully tells you why something failed"
load-bearing "hopefully" there
(slide full of C code)
"Who knows the undefined behavior"
(pause for less than 30 seconds)
sometimes rhetoric is still very effective even if you know exactly how the trick works
Boosted by adele@social.pollux.casa ("Adële 🐁!"):
Stomata@procial.tchncs.de wrote:
A lightweight, JavaScript free web client for fediverse by @adele@social.pollux.casa
https://adele.pages.casa/md/blog/the-fediverse-deserves-a-dumb-graphical-client.md
Boosted by adele@social.pollux.casa ("Adële 🐁!"):
matusguy@treehouse.systems ("Marty") wrote:
@adele i have been using Smither (https://codeberg.org/nuclearfog/Smither) for Android. it is a pretty complete & lightweight client for mobile.
Whew. After a short (and much needed) "emotional whiplash break" inserted into the schedule by @chrisjrn, we have @benno with "State of Exception(s)", a talk about error handling. And then as befits a lighter-hearted and more technical talk, we open with a brief reference to the historical figure of Carl Schmitt and commentary from "reactionary twit" Brian Lunduke.
Oops.
Ahem. And now, some examples of idiomatic error handling in C…
"Oppose *systems*
Support *people*"
Remember that once-beloved children's fantasy by an author from South West England, about a pre-teen orphan boy who is inducted into a hidden magical society?
It was adapted for the big screen and even spawned a stage musical. The work attempted to address progressive social issues, but today it has lost significant favor due to the author's increasingly hard-to-ignore racism, antisemitism, and other prejudices.
I am speaking, of course, of Charles Kingsley's The Water-Babies (1863).
"*Why* are users turning to chatbots as a way of dealing with loneliness? What are the gaps in existing technology?"
An even wider-ranging indictment of the basic tools of statistics, data science, machine learning, and the concept of "intelligence" than I'm familiar with. Even the concept of a linear regression evokes an implicit normative judgement, that human difference is all quantifiable and sameness is desirable — when those things are demonstrably untrue. But more to the point these fields were *initally developed* by eugenicists.
Always glad to see Nick Bostrom, Longtermism, William MacAskill, Effective Altruism, etc etc get read for filth. These guys *still* get way too much credit for the bailey of their ideas and are not often scrutinized for the motte of overt eugenics, racism, misogyny that they are building upon.
Good morning! Up now: "An Economy of Empathy" by @pythonbynight . We are starting off … extremely dark … with some descriptions of the grisly reality of content-moderation work in the global south at a company called "Sama" (on behalf of Meta, née Facebook) and moving directly to eugenics, including from the founder of "AI", and creator of Lisp, John McCarthy. Oooooooof.
"Are these biases still present in the tech industry?"
Not exactly a surprise, but, again: oof. #NBPy