SeptiumMMX

Interesting. If you don't mind me asking, at what age do you plan to retire, what funds to you plan to use to cover the living expenses, and what skill set are you trying to pass to your kids so they will be able to afford moving out and staring their own families?

I'm asking because things things are getting harder every year and the media has a permanent blind eye on them.

That's the problem. Real humans in real world cannot be impartial and will always have biases. So if you expose the public to many different biased opinions and let them learn to recognize the biases and see past them, the "cumulative mindset" will be more objective and less prone to manipulation.

But if you let one biased group decide what the majority is allowed to see, the public opinion will inevitably align with the interests of that group, and won't be necessary beneficial to the public.

Have you noticed how in the past decade or two we have totally abandoned the pursuit of happiness through self-reliance and independence? How being depressed and outraged is normal, and is all but encouraged. This is all coming from the media actively shaping what gets into one's attention span and it will only be causing more and more misery with no end in sight.

And this comes down to a very simple formula. Media likes people who will create content for free. People who are willing to do are often unhappy and have a mindset that causes unhappiness. Media broadcasting their content (to their own profit, of course) is popularizing that mindset and making more people miserable. Bingo!

Well, fact-checking works if it's done impartially. So, if you want to fairly fact-check a political debate, each side should have their own team of researchers/fact-checkers being equally able to object to an argument made by the opposing party. Due process, sort of, kind of.

But I don't think I've ever seen that done actually. Usually, fact checkers are akin to Reddit moderators. Technically independent, but with one important twist. These are people that have a lot of free time and are willing to spend it doing unpaid (or underpaid) work. And that's a huge bias. Big enough to question impartiality, if you ask me.

Given that it's BWT, the difference should be the most prominent on codebases with huge amounts of mostly equivalent files. Most compression algorithms won't help if you get an exact duplicate of some block when it's past the compression window (and will be less efficient if near the end of the window).

But here's a practical trick: sort files by extension and then by name before putting them into an archive, and then use any conventional compression. It will very likely put the similar-looking files together, and save you space. Done that in practice, works like a charm.

Because things can go from routine to multiple simultaneous life-threatening failures very quickly. Something like one flight declaring a mayday while another one just lost communication, all while the radar just started glitching in a weird way. Human intuition and common sense can sort it out. Deterministic algorithms would not.

Check out Avalonia [0]

It's a cross-platform spiritual successor of WPF and it kicks ass! You get proper separation of models and views, you can separate what controls there are from how they look (themes/styles), you can build the entire thing into a native compiled application with very reasonable speed and memory use.

[0] https://avaloniaui.net

I don't think the 4-hour SLA customers subsidize the 72-hour ones. It's more about managing the volume of support. If know you won't get an until 3 days after, you will google obvious things yourself, and only contact support if you can't get the answer otherwise. But shorter SLAs, let alone phone support, encourages a particular kind of customers to just copy-paste any error message they encounter (that may not necessarily come from your product) and expect support to untangle it. Been there, seen that.

The practical use for this could be satellite messaging (e.g. InReach) where a message is limited to ~160 characters, and costs about a dollar per message.

Had similar shenanigans. Solved by consistently having half a glass of water before bed (yes, you'll need to wake up to let it out), and another half at night if there's any hint of sleep problems.

Except, it doesn't render anything. It's the recently used parts of the higher layers of the inference network starting to have electrical activity of their own to do some kind of optimization/defragmentation.

You always need to look at the track record of the team. If they were not producing solid consistent results before you joined them, it's a very good indicator that something's fishy. All that "they are working on something else that we can't tell you" is BS.

If they were, and you were the only one treated like that, hiring you was a decision forced upon the team, so they got rid of you in a rather efficient way.