eramdam

"You're obviously the Grungler"

cis; 30s; Web dev; videos gamer; enjoyer of music, tinkerer of computers; 🇫🇷 in 🇺🇸 (SF bay area);
Trans & Black Lives Matter. You probably know me for Better TweetDeck!

I sometimes repost 18+ stuff that's tagged, so be aware of that (and don't be a minor).

icon by @CoolTimesOnline

 


My blog (with RSS!)
damien.zone/
on Mastodon (paste it into the search of your Mastodon client)
social.erambert.me/@eramdam
Twitter (locked, feel free to ask but don't get upset if i refuse)
twitter.com/eramdam
everything else
erambert.me/

ireneista
@ireneista

and that's why it takes round-the-clock oncall teams to keep fixing it

otherwise it stops working

we suspect there's going to be a practical demonstration of this at some point in the next 24 hours. truly quite tragic, especially for the workers who spent years of their lives making it all go. also very bad for independent creators whose revenue was tied to the thing.


You must log in to comment.

in reply to @ireneista's post:

i mean this politely, but there are so many moving parts that are changing underneath you all the time. the bigger the thing, the bigger the potential for any part of the foundation to crack. it's horrifying but I suspect this is... a last hurrah of twt.

Wrote "twt" meaning Twitter. And I mean that dependencies break, programs get abandoned, links rot, accounts banned, etc. Any one thing breaking can result in a myriad of curious or implausible fixes being needed to even make things operational. I think the case of leftpad in the npm ecosystem is a fun one just based on how many things broke when it went poof. I can't say what'll break because I didn't build it or work there. It's just a vibe based on too many other projects losing key people and especially ones with way less people than Twitter did

Yeah, then I do agree with you that most software stands on shaky foundation, but I guess my claim is that in almost all cases there's a better way to do it

For instance, NPM's leftPad (IMO) reflects a design flaw in NPM more than anything; uploaded packages should be immutable

(I will grant that there is at least one "runtime dependency" which is hard to beat, and that is a working internet connection ;p)

broadly speaking we're on the same page there, in that we also believe that it's important to shore up those foundations, and that there are clear paths to doing so.

we do worry a bit about doing so through increasing the control that hierarchical power structures such as the NPM organization have over the practice of software development, but we think there's clear alternatives to hierarchy that are already underway elsewhere in the broader free software ecosystem, and we're hopeful that everything will work itself out.

the main thing that makes it difficult to take time to reinforce the foundations is that everyone is constantly adding features. sometimes building better things means slowing down and taking the time to do it right.

yep. and combined with the "relaxed" (cough) moderation guidelines, "blue checks for $8" starting on Monday, and the midterms on Tuesday ... also quite possibly not very good for democracy. we shall see.

the layoffs have started. one friend of ours was laid off while oncall a couple hours ago. and the secondary oncall was also laid off. and their manager was laid off. and it's a large, complicated service that has a substantial impact on ad revenue. we'll be extremely impressed if things are going well enough for them to even think about rolling out new features by Monday.

I spend more time than I would like thinking about how the dude responsible for this is still basically allowed to have the influence of a world leader because he purchased the title of Technology Guy, despite demonstrably and persistently having no clue what's up about anything at all.