Python3267

Oh god, it makes sense now. Palinteer is partnering with ring for footing and will be acquired by Sauron.

Pulled out good ol' wireshark. It's the server that's erroring on the TLS handshake.

Thanks, yeah I misread the GUI. This is awesome!

Here's an interesting one, if the equipment is sensitive enough you could test if you can see the difference in air densities as a .22 caliber bullet passes by.

I've got nothing for this but I am morbidly curious.

We should have a wealth tax that is distributed to everyone, instead of taxing consumption. It's the most progressive tax possible, only taxing those with actual excess. It would work in an AI world, easing into everyone having the same amount of power instead of creating AI powered Oligarchs.

Taking a networking class, I'm still amazed that CS programs don't require it at this point.

Dollars to donuts, you cannot have a high velocity distributed system with dozens of developers without comprehensive docs and long term plans. This article is straight up bad.

This is a principle that can be applied outside of this question, but is applicable here. Many non-engineers view software as an asset, *it is not*. Every line of code is a liability, so minimizing the size of a codebase and limiting the complexity of distributed systems (If posible avoid DS's) is key for good reliable software.

If the code needs to be fast (written in a systems language like C, C++, or Rust) write it in Rust. It will limit the amount your can shoot your foot both at the compilation stage and while writing the code (You have to think about what you're doing to avoid the compiler yelling at you. Otherwise, for the love of god write your project in a simple garbage collected language. Not having to handle memory directly removes a lot of what can go wrong.

This article was written for non-technical folks unfortunately. I read the phrase below and nearly puked from the corpo speech.

> So, the methodology around temperature mitigation always starts at power reduction—which means that growth, IT efficiencies, right-sizing for your capacity...

How long until we see @eastdakota here :D.

Agreed, but the problem is a lot of companies don't ask questions that screen for people who can build longer term systems that are extendable.