Will we also eventually get a generic sync.Map?

Heat pumps do not do well when it's -40 outside. You can say "fine, but how often does it get that cold?" but consumers are not going to be happy with a heat pump if their pipes freeze during an extended cold snap.

I live in Southern Ontario and I have a heat pump with an auxiliary natural gas furnace for emergency heating. The heat pump shoulders most of the heating load but the thermostat does kick on the furnace when the heat pump starts falling behind.

It should also be noted that although heat pumps are very efficient, even when it's below freezing outside, they cannot raise the temperature of the house very quickly. Consumers are generally quite unhappy when it takes 8 hours to raise the temperature of the house by 1 degree, so the thermostat usually calls for the furnace to start up before things get that bad.

Thanks for sharing. I want to ask you something: I understand that with IPv6 the idea is that every household receives several of IPv6 addresses so that every single IoT device has their unique IPv6 address and there is no NAT needed.

Would it be possible to use a dozen of IPv6 addresses at the same time? Like send one UDP packet over certain IPv6 interface, next packet over another IPv6 interface, and so on. If both sending and receiving end have access to multiple IPv6 addresses I can see how this significantly increases complexity for tracking.

Could you split up the traffic across dozens or hundreds of IPv6 source addresses?

>UUIDs are often generated client-side

since when?

No idea how you got that from Atomic Habits. Shockingly unscientific book.

A body's atoms do completely recycle every 5-7 years though. 98 percent are recycled annually. Weird.

What is "20% on Go"? What is it 20% of?

I don't understand the shit 'managers' get on here. I've been in this industry for 15+ years and with one or two rare exceptions every manager has been great.

They respect my time, when I need something they're incredibly helpful, and they care about my career development.

IMO the culling over managers over the past few years is really a way to make sure you don't have someone you can discuss career development, promotion, and pay increases with. I have very honest conversations with my managers about these things regularly. If I had to deal with someone a few layers above I doubt I'd have the same success.

Another 'benefit' for the company in culling managers is that the manager track generally has higher pay at each level. Understandable given it seems to involve more time commitment and dealing with people can be much more tricky than dealing with code. Less options for IC's to transition == lower salary burden. Reduce the number of people on the manager track and you reduce the amount of salary an employee can hope to attain. I've definitely been put off switching from IC to manager because I feel the jobs are less secure over the last few years.