Pinned toot


GG: dog in space
GG: its her place now
GG: funny how we ever thought it was ours

GG: dog in space
GG: where is she now?
GG: funny how we ever thought she was ours

If you're under 30 you don't know this yet: you have until you're 35 to submit which class of adult you want to be. Popular paths are Grilling (main category: Cooking), Fishing, Lawncare, Sports*, Cars or motorbikes (non sport), Couponing, Meddling (Only available to those who chose the Parental model), and the Pursuit of Your Youth.

KJ recently chose Grilling Dad path with a minor focus in Wife Guy. I'm still undecided but I'm really excited about maybe becoming Overly Interested in the Weather.

*Ball or Combat sports. Air, Ice, Aquatic, Equestrian, Olympian, and motorsports available only in select regions.

as a streamer, i'm obligated to say that you should NOT use any kind of ad blocker because streamers get some nonspecific amount of money from ads.
an example of a blocker that does work on twitch without interrupting the stream is which you should again NOT use

re: seasons Opinion 

why does summer *exist*

Show thread

seasons Opinion 

whats the worst season and why is it summer

They. They put audio in the unmodified cart. They put. They put voice in there, with ACE

deltarune, this is stupid 

kris doesn't have an f in their name because they choose disrespect

I meant to turn this towards talking about medians a little, but it got a bit late and I'm going to sleep. Further investigation and own introspection is now homework assigned to the reader!

Show thread

Like, I think "we" can also refer to the sum of the "I" who is currently writing this, and other future versions of "me". Documentation is kind of inherently about having a conversation with yourself: "What kinds of questions would I ask if I were coming to this code without existing knowledge about it?" "What would I want a reminder on in the future, having forgotten the specific details of this code?"

I think there's not that much of a difference between a "note to self" and documentation that you write "for others". I mean, if you're writing it for yourself, you probably don't hold it to the same literary standard as docs for others (or else you have a low standard of communication, deep down know others might get use from the note, or are awesome)... and you might take pre-existing knowledge for granted, for the sake of brevity in a note that isn't going to stick around for ages. Like writing a short @todo instead of a full-scale tech debt bug report.

But those mostly feel like surface level differences to me. You're still writing a note to someone who you don't exactly "know"—either a future you or a hypothetical other audience. Whether it's future!you or someone else, you're using humility to recognize that you currently understand details or concepts that they don't, and that it's worthwhile to convey those details.

So, I think that's at least part of where "we" comes from—because "we" is all about inclusivity, it feels right to use when you're having this imaginary conversation with another. You're meeting them at the same level and teaching with the awareness that they don't know what you do, but the trust and respect that they will understand based off what you tell them. "We" brings you and them (or, us) together.

Probably that sounds kind of sappy, especially to apply to the established audience of "unknown strangers" or "future selves", but c'mon, it makes sense, right? "We" IS a sappy pronoun, and that's good!

Show thread

In enterprise or team codebases there is a fairly solid definition of who "we" is: literally, your colleagues, the ones who are also working on the same code. Those are specific people. But it also includes anyone who MIGHT work on this code in the future, like new team members, someone taking over your role developing a particular part of the codebase, etc. Or in open source projects, any general reader who is interested in building off of your own work (or just understanding it more thoroughly).

But also—and maybe this isn't as common as it seems—but don't devs sometimes use this same "we" pattern when there isn't even anyone they're theoretically referring to? When it's either private code or so ridiculously obscure that probably nobody will pay much attention to it until ages from now?

Is it just habit when we use "we" pronouns there? Okay, possibly! But language is cool and maaaaybe it points to more reasons that "we" is useful besides referring to literal other individuals.

Show thread

I've always found the thing programmers do with "we" pronouns in code comments funny! Like, here's one example out of a zillion:

 * [...]
* Many top blocks need to match fields as well as opcode, since that matching compares strings in uppercase we can go ahead and uppercase the cached value so we don't need to in the future.

"So that WE can go ahead," "so WE don't need to in the future." Right? But who's the "we" here?

"We" is for togetherness / inclusiveness, by definition; seems fair to say it's referring to the developer who's actually writing the documentation together with some imagined audience or colleague. But it's funny, because! There isn't a conversation going on here at all - we(!) say "we" but it's only one person talking, whoever is writing. So you're guiding that audience/colleague through your code, answering questions you project them as asking... even though there isn't anyone actually there. I think it's a cool phenomenon.

three (3) capital letters 

New profile picture! Yes.

I/we still don't use masto much at all, but hell if a girl doesn't need a place to put a profile picture from time to time.

wait shit we doing a fruit thing? uh I like plums they are so cold and so sweet WAIT FUCK THAT'S POEMS NOT FRUITS

Show older
Plural Café

Plural Café is a community for plural systems and plural-friendly singlets alike, that hopes to foster a safe place for finding and interacting with other systems in the Mastodon fediverse.