Not sure if you are looking for an answer or just letting the steam out... But if you are searching for knowledge, then I would suggest picking up a book or two on leading people. It was a big surprise to me that such books exist and that they actually help understand the dynamics in companies, and how to achieve win-win outcomes. Good luck!

I think it paints part of a picture - obviously you shouldn't hire just based on top score in an algorithmic interview. But if I interview someone for a JOB WRITING CODE with decades of experience and they refuse to write code and can't explain the difference between a linked list and an array, that's a good argument for reconsidering hiring them...

Sure, explain. Write? Not sure about that. The main question is what kind of code they are supposed to write. Have you actually used a linked list in a company setting? I know the difference, but can't say I've used it... ever, in a company setting. I guess if I worked for Redis or similar this would be base requirement, but for 98% of software development jobs I don't see where this could be useful.

My experience is the opposite - developers eager to squeeze every last drop, using some exotic data structure [*] or sorting algorithm which takes way too long to implement and makes code review a nightmare. For a feature that doesn't need it.

[*] not saying that linked list is exotic, it is just rarely needed in $DAYJOB in my experience.

Yes, I have used a linked list in a company setting, both in writing code and in technically leading things where understanding the behavior of linked lists vs arrays was important. But again, it's not the only criteria in these kinds of interviews IF CONDUCTED WELL - the specific experience you cite, of "developers eager to squeeze every last drop... makes code review a nightmare. For a feature that doesn't need it" is also part of what you're looking for. And you can ask a candidate who does that "hey, that seems unnecessary here and hard to undrstand, why are you doing that?"

Almost anything is better than any Teams thing.

Really? Interesting. I loved KDE3, but hated KDE4 so much (slow, unintuitive UI, bugs) that I haven't looked at it since, preferring Xfce instead. I guess I could give it a spin again...

I use pipenv and it kind-of-works. Will try uv or poetry though - which one would you recommend?

UV. Using it as the exec target for python (UV script) is great. Dependencies declared at the top, now I have executable files in something better than bash.

I no longer shy away from writing <500 LOC utility/glue scripts in python thanks to uv.

I can't recommend uv enough. It's so fast, and uvx is so useful to run a random Python CLI tool. If you want to do things like you're accustomed to with pip you just `uv pip ...`

That... doesn't make sense? If anything, using a popular term would be a disadvantage wrt. SEO, because now they need to compete against many many many unrelated websites.

Sounds like a great idea, but difficult to achieve. The announcement blog post was almost 5 years ago, do you know maybe what the impact of this project has been in practice?

There are yearly releases of the standard https://data-apis.org/blog/ and I often see it ref'd on issues in individual libraries (numpy, pytorch)

See also funding from CZI (on the blog)

Subjectively I do find it helps with consistency -- and when things are not consistent, it's easier to discover what's different and why

edit: but I completely agree with this post and the follow-up from the same author on "dumbpy". At least at first blush, I need to read in more detail.

For me at least, it turns out there are no important ones.

Or even just AC (think visibility).