• 0 Posts
  • 7 Comments
Joined 25 days ago
cake
Cake day: August 30th, 2026

help-circle
  • While I don’t disagree with this post in spirit, it feels tone deaf. Many very popular and well used FOSS projects rely on one or two core contributors who are volunteering their time to build something useful, fitting that work in alongside their paying work and the rest of their life. If a maintainer of a project I use has 3 hours in between their kid’s baseball game and dinner one Sunday to spend working on it, I’d much rather them spend that time making the project better than on giving pro forma replies to PRs and issues that aren’t valuable to the project to adhere to some sense of decorum (and, as a former maintainer, even a polite “no” to a bad idea or a disguised request for free technical consulting is time consuming).

    As a tangent,

    Not acknowledging contributions and the work that goes into them, whether through a quick response or a kind word, undermines our entire community. Every time that happens, it’s a “fuck you” towards a contributor. That seems fashionable if we look at the wider society—things are falling apart around us as we burn the planet and let nations get away with exploitation and murder—, but that doesn’t make it acceptable.

    is kind of a wild connection to draw given the reality of many (most, I’d argue) FOSS projects. A busy single maintainer prioritizing their limited time by ignoring low effort contributions is in no way like burning the planet.

    (maybe the author is implicitly thinking of very large, well resourced projects with sustaining funding and a lot of maintainers, where I think a higher standard might be fair. That’s not really clear from the post, though, and I don’t think it’s accurate to regard those as “the community”, in the same way that we don’t regard Google, Amazon, etc as the entire software industry)


  • I have a hard time telling AI authored LinkedIn thought leadership apart from formulaic LinkedIn thought leadership sometimes, but this feels AI written, which makes it fairly amusing considering the point it’s making.

    (Does vibe coding feel incredible? Also, “Nobody’s asking what happens in Month 18 when the original dev has left and nobody understands the codebase” implies that the vibe coder original dev understood the codebase at any point, which isn’t an argument I’d feel comfortable making for any of the ones I’ve worked with)



  • I was half joking. 😅 Of all the tradesfolk I’ve hired to do work on my house, my arborist is the only one who’s job I could see myself actually liking. He gets paid to be a nerd about something (trees, tree health, tree care), the work itself seems a lot more pleasant than dealing with plumbing or electrical repairs, and at least my guy is a one man band who just shows up and does his thing, which is certainly appealing after a career of various EMs, PMs, TPMs, and other people who need to be appeased when doing work. Also the fun tools.



  • I guess it isn’t that surprising. I bet the developers who write the software included in this distribution would love some of those millions, but being a guy with a brand and opinions is apparently more valuable to the investor class. Consistent with how they think about the workforce at their own companies, anyway.

    (I normally read things like this as people paying tribute to the guy running the company getting the money, or wanting to be perceived as in favor of that company’s viewpoints. I don’t understand why anyone would want to pay tribute to DHH. Ignoring the ick, he’s not that important or powerful. There are a lot of SWEs who don’t know who he is, let alone the general public)


  • I don’t have a problem believing it. They have an infinite money supply (to date), the negative consequences of this are borne by other people, and they probably have plenty of leadership from other tech firms who are used to making narrow ROI arguments based on what benefits the company. Easy enough to imagine “hey, let’s unfuck our crawler!” getting dismissed at not a priority.