Kind likes

 Like

Liked Sentry: From the Beginning
Post details
I've been trying to invest more and more of my free time interacting with founders. I genuinely feel we've been through a lot with Sentry and I can provide some useful value to others. More so, I believe most people in this industry, most successful people, do others a disservice but not having honest conversations about the hardships and endurance it takes to succeed. As part of that I thought it'd be interesting, or at least therapeutic, to talk about some of the history in written form. I previously wrote about Sentry's Seed Funding, but I want to go deeper on some other topics this time around. I'm not entirely sure what future topics I'll cover, but hopefully you'll find some value in it.

 Like

Liked divya (@divya@sfba.social)
Post details
In hindu mythology, there is casual violence committed on "demons" who are supposed to be terrible people. Today is a day that celebrates the death of one of those for the South Indian hindus. Given how hindus treat Indigenous people today, it is not lost on me that it is very likely that those "demons" were likely innocent folks upon whom we inflicted violence 2000 years ago and decided to cement that horror in a mythology conveniently claiming these folks deserved it. This is why I do not celebrate Diwali. The closer you peer into hinduism, the more oppressive it becomes.

 Like

Liked Chris Siebenmann (@cks@mastodon.social)
Post details
Today, if you publish a popular Go module on a URL and you lose control of the URL (through, eg, domain expiration and having the domain snatched up), you have a problem that's probably more or less impossible to deal with short of making blog/Fediverse/etc posts about the situation. Go module identity is tied to URLs with more or less no external override or way to automatically announce and see problems (individual people can override for their usage, but that doesn't scale).

 Like

Liked Sean Coates (@sean@scoat.es)
Post details
Past-self just saved me 2+ hours by documenting how to do the thing that took ~3 hours to figure out and fix last time. Good job past-self. Also, good job current-self for remembering that past-self should have documented this and then going to find the doc.

 Like

Liked ruhee (@ruhee@phire.place)
Post details
I finally bought @beep@follow.ethanmarcotte.com's new book, You Deserve A Tech Union, because we do deserve one. And very amusingly, my learning & development budget covered it. ✊🏽✊🏽✊🏽 https://abookapart.com/products/you-deserve-a-tech-union

 Like

Liked Mike McQuaid (@mikemcquaid@mastodon.social)
Post details
Gonna give a talk ("Open Source: Boundaries, Burnout and Business”) and chat with folks about open source software at the first OpenUK Scottish meet up in Edinburgh on 22nd November 2023 from 6-9PM.

Would be lovely to see some of you there!

https://www.meetup.com/openuk-glasgow-edinburgh/events/296929069/

 Like

Liked kf (@kf@666.glitchwit.ch)
Post details
thinking today about back when I was in code school in SF one of the cofounders was OBSESSED with my two-character twitter handle, and even though I went by my birth name at the time, he would call me kf so I called him by his handle, too a year later, one of the staff told me that every time I did this, he would go upstairs in the office, slam doors, and tell the staff that I was insulting him for having a four-character handle 😂 anyway that’s how I got my name 🤣 #fragilemasculinity

 Like

Liked S. L. Crane (@slcrane@writing.exchange)
Post details
An update that absolutely no one could've seen coming**: One of the companies using AI instead of qualified copywriters to draft their career guide blog posts is now realizing that these texts are highly generic, repetitive, and of little value for readers. They will have to be redone, and a lot of time and resources were wasted. Awww. 😏 (** Just kidding. This was, of course, utterly predictable.) #AI #Fail

 Like

Liked lime with barcode (@scanlime@misc.name)
Post details
some naive networking greybeard once wrote that a good URL never changes, or something but URLs do change because everything changes, and the expectations around their longevity and change are one place where people exert power and have power used over them. if people rely on a URL they're actually relying on a stream of labor. There is no "static" content, all data storage requires some portion of ongoing renewal: new materials and ongoing human care.