You are right, there's not enough time to filter a bad hire. Not enough time to fully vet anyone during an interview. We can work a challenge together to see how you work collaboratively

Interviews cover collaboration compatibility. Not enough time to quiz you on tech knowledge. Leetcode-style interview represents your ability to work a problem collaboratively with a team

You made real-life Clippy! for the Mac. This would be great to be for other mac apps too. Add context of current running apps.

It should work for any macOS app. It just takes a screenshot of the currently active window, you can even append the application name if you'd like.

Using native google sheets equations, you can build your own neural network. Google Spreadsheet: https://docs.google.com/spreadsheets/d/1VS1kn0zXbedx7JEJu1ui...

HTTP/3 maintains a unique connection ID through the QUIC protocol. The connection ID is not dependent the device's IP address. This allows the connectivity to remain persistent even as users switch between different networks such as 5G and Wi-Fi. In a way you can consider this as a "connectionless" session. The session isn't tied between two IP addresses.

WFH is happiness. I want that. And I want that for my team.

Challenges with Kubernetes: 1. High Costs due to unoptimized initial deployments. 2. Steep learning curve of Kubernetes. 3. Tuning autoscaling for stability and efficiency.

Carbon emissions too, evidently.

Recently

Carbon aware spatial shifting of Kubernetes workloads using Karmada - Blog - https://news.ycombinator.com/item?id=37050659 - 2 hours ago (0 comments)

This is problem for our planet. Carbon emissions are high.

Here's our current CPU Utilization. https://images.ctfassets.net/3prze68gbwl1/1wy7lTmXHA1liIlcMW...

We're paying AWS for servers that remain hot that we don't use effectively.

Conversation from reddit thread: https://www.reddit.com/r/Python/comments/15i5je7/unlocking_p...

I was initially excited about the possibility of disabling the Global Interpreter Lock (GIL) in Python 3.12, as it promised to enable new opportunities for performance gains. It's true, however we have so many options already! Disabling the GIL would only allow for the use of threading patterns and threads within Python, which I am not a fan of this programming pattern. My preferred method for achieving high concurrency and efficient programs is to use multiple processes with message passing.

If you're considering upgrading your Python the the latest runtime, you may get the results we saw as well.