jsmeaton

Eh I think that’s a pretty uncharitable take.

They did the same thing with ruff too. A totally optional interface through the uv command. Use it or not.

Stackoverflow started failing when Jeff left. While he had a big hand in the whole mantra of being more of a Wiki than just Q&A, I feel his sense of community wouldn’t have let it get so bad.

Then all of the OG engineers left (I hope Nick Craver is doing well, his blog posts were incredible), an investment company took over, and whatever good will and vibe that was left melted away.

I’ll still occasionally find a good answer there. But it has zero future of making answers available for future good questions.

They took the fun away.

Is there a way to determine if a particular connection is falling back to DERP today?

I have a pretty basic setup with tailscale setup on an Apple TV behind a bunch of UniFi devices and occasionally tunnelled traffic is incredibly slow.

Wondering if it’s worth setting this up on my Plex server which is behind fewer devices and has a lot of unused network and cpu.

Guess where we host nexus..

Astral folks that are around - there seems to be a bit of confusion in the product page that the blog post makes a little more clear.

> The next step in Python packaging

The headline is the confusing bit I think - "oh no, another tool already?"

IMO you should lean into stating this is going to be a paid product (answering how you plan to make money and become sustainable), and highlight that this will help solve private packaging problems.

I'm excited by this announcement by the way. Setting up scalable private python registries is a huge pain. Looking forward to it!

I've been wondering where the commercial service would come in and this sounds like just the right product that aligns with what you're already doing and serves a real need. Setting up scalable private registries for python is awful.

Do you have an example of this?

What issues are you having with uvx? It replaces tools like pipx that set up implicit venvs to run specific tools. Works great for me.

The “hello Bluey” at the end gets me every time.

Agree. Rounding most of the advice to providing an executive summary is about right.

If you’re not fully confident and think an experiment is worth while, lead with that, and provide assurances there are mitigations in place or a decision is easy to back out of. That’s still doing the work.

If you want an easy decision, you need to do the work. Not expect others to get into all the detail you did. There’s still room for those decisions - they’re just not as quick/easy.

I often give similar advice to colleagues that ask me for pointers on getting their recommendations approved.

"Make it as easy as possible for them to say yes"

Don't dump 14 paragraphs in front of someone expecting them to get onto the same level that you've been after many hours of studying a problem. If you're confident in your approach (and you should be, if you want an easy yes!), then be succinct, briefly describe the problem and why your solution is correct. Optionally link to a document that has more information if a reader wants to go deeper. Make sure you've already gained "approval" from your other team mates or product owners.

"We're going to solve X by doing Y. Team are all onboard. Proposal document is at [link] if you want the detail. Going to begin on Tuesday unless there's any more feedback we need to address."

Managers etc don't have time to get into the detail of every little thing, and appreciate when you've done the work, including gaining support from the wider team, so if they need to approve, they can just approve.