Yes
05.11.2024 22:24
👍 2
🔁 0
💬 0
📌 0
Yes
For me it was a combination of the 🦋s, unashamed Elon propaganda/ lies, and then finally the starter packs. I was a small account, but after a couple of days I think I now have *more* Bluesky followers. It was tempting but it's now genuinely worth my time to pay attention.
She has a strong intuitive sense of the "EW FFS" element of my OSS work
Worth also remembering that a Republican presidential candidate has won the popular vote in the US exactly *once* since 1988. And yet we've somehow had twelve years of Republican presidents, and however many decades of their Supreme Court picks.
Reminder that the National Popular Vote Interstate Compact exists and has a *chance* of coming into effect, it only needs a handful more purple states to sign on.
If you're frustrated to be voting in a non-swing state today, check it out and see how you can support it www.nationalpopularvote.com
That's what we found empirically when I was working on AI chatbots at Microsoft (admittedly "early" AI, pre GPT). People liked when chatbots enabled new functionality - and AI was great for shipping new stuff fast. But for any given functionality it was just not efficient UX.
I agree about most of that, but not chat. Chat is a great stopgap for developers/product teams who haven't figured out the right happy path yet, and want to let their users find it. But once you've found it, UI ("book now" button) beats AI (typing "b-o-o-k-n-o-w") every time.
In terms of OSS contributors, @colinhacks.com made one here: bsky.app/profile/coli...
My wife thought this was cool for about 15 seconds before I told her the npm downloads -> MRR conversion rate
When vitest starts using the library you wrote as a prod dependency
It makes it so much easier to
- add functionality
- upgrade to new major versions
- narrow types to your domain
- switch to another dependency entirely
- apply patches/side effects without them "infecting" the rest of your codebase
I love this pattern. I'd go further than - not to be an defender of abstraction which is so uncool now - but in medium to large projects, you should usually do something like this for any dependencies that you use in more than a handful of places.
okay I made a starter pack with my favorite TypeScript folks from the old site, mostly OSS maintainers
let me know who I forgot 👀
go.bsky.app/84ChefN
What if you are authoring a tool and need to choose the default
We must find a way to make this a flamewar
Have we done tabs vs spaces here yet?
...tabs r bad
👀
lol thanks @colinhacks.com for getting me to start using this!
Feels hopeful. Might see if I can start ignoring The Bad Place after Tuesday...