@fgtech All true 👍🏻
@fgtech All true 👍🏻
@fgtech It’s a bit of an issue for cultural discourse, though. Which is an issue for most things digital, not just the web. There are a lot of landmark iOS apps and games that are no longer available anywhere. Which means that a lot of modern takes on the history of interactive media will be as good as fictional.
Same with modern analysis of specific slices of web history. Too many of the primary sources are gone.
@artkavanagh Yeah, it is what it is and knowing that sooner would have been nice.
@terrygrier Exactly! It’s all a sort of performance that never actually translates into more interesting writing.
@artkavanagh My pleasure 🙂
@pimoore Thanks! I’m using a static site generator called Hugo (it basically turns folders of markdown files into a site) using a theme I made myself and hosted on Netlify. It’s honestly a little bit of a pain in the ass so I wouldn’t recommend it over a proper CMS 🙂
@AngeloStavrow IME mature projects are often worse. Features get added, new configs, etc. but the docs don’t keep up and often become just plain wrong. And node serverside projects seem worse than client-side ones.
I can’t rule out the poss that I’m just unlucky, tho 🙂
@leonp It’s so weird. I understand why local producers are capitalising on it, though. 🤷🏻♂️
@jemostrom I remember when I moved to Bristol back i 2000, when people learned I’m from Iceland, half the responses were “I hate Björk” and the other half were “þungur hnífur!”. 😅
@artkavanagh Thanks! 🙂
@artkavanagh The problem is that most public discourse is an attempt to persuade or promote a worldview. I’d modify it slightly in that if it’s public writing by a public figure then you need to inspect their role in the public discourse. The motivations of a VC discussing labour regulation automatically makes everything they say suspect, for example.
@manton I don't know if this is related but my micro.blog isn't cross-posting to Mastodon anymore.
@artkavanagh I would love that as well, yeah.
@lmika Dropbox! They have a file preview for epub that does very little other than render the epub as HTML and keep track of your location. Sometimes that’s enough 🙂
@email@example.com Yup! The notes account is a subset of the main mastodon account. It contains everything I post to the notes blog but it doesn’t have any of the additional posts, comments, or conversations I post to the toot.cafe account. 🙂
@jackyalcine Turns out make has a bunch of nice build-related features. Whodathunkit? 😄
@artkavanagh Hah! Yeah. Too true.
@artkavanagh No. I always assumed somebody else would. I've frankly been a bit perplexed by how quickly people seem to have forgotten the weblog adwords bubble
@kimberlyhirsh Such an eye-opener 🙂
@pimoore Yeah. Although I’m not sure how much of that can be attributed to npm’s design and how much of it is either its sheer size or bad habits in the JS/node community.
Or all of the above?
@manton Sure. I get that impulse. I really do. 🙂
My point is that what they did publicly, even before we started to get reports on what was happening internally, is damning enough. We don’t need to find out what happened because none of it would suddenly make their actions good management. Either they badly mishandled one major crisis or they’ve been badly mismanaging the company for months, if not years.
The only way that their public actions last week weren’t incredibly poor decision-making is if the goal was to get rid of employees in a loud and public way so as to discourage specific types of applicants in the future. Keep the company lean and make sure only yes-people apply in the future.
If that was the goal, then it worked perfectly.
@manton When several employees publicly state “I found out about this from Jason Fried’s public blog post” then it’s unambiguously the CEO who’s at fault. He should have ensured that the decisions were adequately communicated to staff before making it public. You can make excuses for him but, at best, those amount to ‘he broke something by accident’. He still broke something, didn’t apologise, and, as CEO, is ultimately responsible no matter what.
He prioritised getting ahead of potential leaks over ensuring good internal communications. No matter how you slice that, that’s pretty irresponsible management right there.
@manton This was mentioned by several (now former) Basecamp employees on Twitter.