Wes

Seems reasonable to keep that feature but also display the full URL in a less disruptive way. The web is *full* of linked text, so this is not "a bluesky problem" right?

Can I pick your brain, folks?

Reply with 3 topics you consider advanced in automated testing 👇

1. how to avoid brittle mocks
2. how the different types of tests (unit, integration, e2e) fit in your testing strategy
3. why coverage should be treated as a trailing metric not a leading metric for assessing "test quality"

Sounds like a pretty perfect system. Productivity through the roof with this approach 🚀

I send myself scheduled slack messages. But also I use a github repo for a todo list....so maybe don't listen to me.

nodejs.org/docs/latest/...

The other doc that says this is an alias of indicates it was added in 12. I was questioning myself. Guess those docs are wrong? 🤣

Is it a spoiler for the episode to link this api? nodejs.org/docs/latest/...

I had to go look this one up because I could not remember exactly how getting the event loop utilization worked.

I aspire to such an exit.

In case you missed it: we published an overhaul of the old Mocha website. It's on @astro.build Starlight and has most of the same contents as before, just separated into granular pages. 🤎

Next up will be auditing those pages to be more comprehensive and correct.

Voila!

@pfrazee.com is 🔴LIVE on stream.place! And we are live with office hours!

🔴 LIVE https://stream.place/pfrazee.com And we are live with office hours!

You can get 2-6x from basic caching of your entire node_modules. I have the data for nearly 27k installs across ~500 repos in front of me. 6x for p50 and 2x for p95 on cache hits compared to miss.

I see myself!

The @vlt.sh benchmark suite has been updated to include the yarn v6 canaries (still a WIP & improving all the time): benchmarks.vlt.sh

Respect for being able to get the clay to cooperate and grow to such a nice shape and size in the cold conditions. 🤣

PS. congrats on pulling a *great* handle on that right one. Pulling a proper handle is one of the harder things to get right.

The people demand pictures of the weird stuff!

Trust is interesting because it’s not quantifiable but it certainly is palpable. Teams with trust move lightning speeds faster than those without.

This is exactly the kind of thing people worry about with browser extensions. It looks like an Amazon ad blocker, but quietly hijacks affiliate links in the background. Most people aren’t reading extension source code (and if you are, congrats 🙃), which is why this works.

Recently in my work slack it showed one "typing..." so I said "go away <bot> I don't care what you have to say".

It stopped and never commented in the thread. So that is at least one positive interaction I had with one. 🤣

Oh I didn't mean for folks who wanted to. I meant for the actual metrics to reflect this change broadly.

Yeah, that was the specific thing I had been waiting for to see how adoption changed. Really would have been awesome to see where we would be had that been addressed from day 1.

> begging the world to just use ESM

Has that worked yet?

Thanks!

Ah, yeah I thought this implied there was more to it than `.d.mts` and the oddities introduced because of dual mode packages.

Do you have a doc link on that `.d.ts`/`.mjs` combo? Just interested in reading why that is potentially bad.

Meet has video/audio quality settings. Zoom does not, making it unusable for me in some situations while I am traveling.

As one does.

same. I have been confused but too busy to go learn what was going on. Glad I made the right choice.

Oh I am a vocal critic! Criticism from the right place is the best way to improve things.

Glad to see more folks working in this space, it needs the work. I just wish we could all build *together* instead of having to duplicate so much effort.