skysight-inc/HackerNews huggingface dataset:
For leaders, this is the beauty of health insurance companies (better called managed care organizations, MCOs).

For places like UK and Canada, leaders have to answer to everyone for why access and quality of healthcare is declining. In the US, using the MCOs, leaders can more easily direct sufficient healthcare to who they want it to go to without being able to be identified as the cause.

For example, leaders can tell MCOs to reimburse healthcare providers less for Medicaid (poor people), and more for Tricare (military) and Medicare (old people who vote), and even more for federal government employee health plans (for themselves). Or they can tell MCOs to require more “prior authorization” (PA) for Medicaid so people give up more quickly at getting medicine, whereas federal government employee plans can require fewer PAs.

Add employer specific risk pools/deductibles/copays/out of pocket maximum limits into the mix, and there are multitude of levers that can be pulled to ensure people are getting the quantity and quality of healthcare corresponding to their socioeconomic level.

Rich people always had concierge medical care. But with the use of MCOs, you can drill it down to income/wealth/political quintiles or even deciles.
I'm curious, why would this be bad? I've generally always seen it as best practice to create classes in your domain model and try to write your ideal code and then have separate classes/DTOs that are used for communicating outside your domain model such as reading/writing to a database using an ORM or responding from an API with your ideal model for the consumer (since more often than not consumers don't need or want all of the cruft inside the domain model and your DB will likely have stored the information in a different format in a large system). I always love thinking of ways to simplify architecture though and I absolutely hate having classes/records that looks so similar though so I'm intrigued about a simpler solution if there is one? Domain Driven Design practices really encourage a bloated/complex architecture so I try to avoid it if possible but more often than not business requirements end up becoming so complex that I immediately fall back to those abstractions when the logic starts to get complex.
Writing complex, unreadable code takes no special talent. Writing concise, nicely structured, understandable code, but still efficient, is the harder task.
"What if someone owned all the air."

Never in our history has anyone ever cornered and monopolized an industry worldwide. Even bringing it down to country level, the exceptions, government formed monopolies. Of which in the last 40 years or so has been incrementally reducing. Nobody is talking about going back to public workers for roads. How about we break every single government monopoly? Problem solved.

What if someone owned all the air. You pay their toll until you build a biosphere and seal in your atmosphere with loads of plants. Then you stop paying and stop receiving their bottles of air.

You start producing your own air and compete against the giant space robot.
After a decade of collecting data, probably
... and to protect the identity of the bear that told you to follow the honey, (while preserving journalistic integrity about not fictionalising sources) never refer to it in print by its proper name, but use an obvious pseudonym, such as "honey-eater"
Soldiers would be the obvious real world example. Or drones.
I don’t think you can make the blanket statement that immigrants are educated, want to work (who does?!), and pay taxes.
It's in their annual and quarterly reports where their profit comes from. They run highly profitable coffee stores around the world.
if you google image search "garbage collector" as I just did, you will in fact see photos of these actual, pivotal, working members of our society.
> When it takes 15 years simply to get permission to do something, you know that your country will never be competitive globally.

I think Sweden is quite competitive in general. Also, as others have said, it could have pretty big impact on various things. But I guess if Sweden was a dictatorship the government could just decide to start digging and not care about the people living there or the environment. 10-15 years sounds very long though, but a week.. I don’t know in which country that would happen.
Privatization of Russia's war fighting [video]
North Beach has some good spots. My go to after a night of drinking is Golden Boy.
I think it has happened several times actually. The town keeps moving as the mine expands.
A friend mine is doing research in solar to simplify production and making parts more green so to rely less on these practices. Each component is being intensely studied. Just adding this to the conversation. Also by upping the yield and longevity, costs go down.
Neato used to make them; then around the time Vorwerk purchased they’ve only sold cloud only versions.

I own both types and I found the cloud version to be less reliable and less convenient.
So that in long nested data you know which tag closes what.
{{{{{}}}}}
That is really cool! Not sure where you at, but feels like with so much vacation, I would just take 1-2 days every week at summer time, and have only 3-4 working days during summer. Can you do it that way as well?
Hiding reddit style posts when they appear in HN
Somehow you've managed to hit all the current Russian propaganda talking points ("8 years", "sanctions not working" and so on). Unless you're getting paid to post this, I strongly recommended to change your information diet. As others have already pointed out, virtually nothing you wrote is true. Other than the totally brainwashed vatniks and the insane talk shows on TV, I don't know anyone who thinks that Russia is winning the war. That's certainly not the mood on Russian business sites nor the mood of their war correspondents. Where did you get your narrative from?
> Values should be only text. Outside of the handful clear specified cases of numbers and maybe true/false/none, they should not have any other interpretation on the parser.

I think simpler way would be just forcing quoting on text. That fixes the boolean and the different base numerics problem
Ask HN:For WebDev,would you learn Java in 2023 given the JVM based alternatives?
Mada 9: Taliban unveils its first supercar, Powered by Toyota Corolla engine
Which of these is better is a matter of distance and scope. If x is only used locally and within a screen or two of the declaration, adding a data structure screens or files away will make things harder to parse. If x is used in many places, passed around to many functions, or is otherwise far away from where it’s needed, it should be replaced with something that has better naming and more robust structure. If it’s the latter, you should rename it away from x as well, as the name of the variable is the first thing that should get documented as you increase distance. If you have a `Status` type already, then you should use that even if X is hyper-local.

Of note, the nesting here seems suspect, why not use a three item tuple or a flattened data class? In many cases I find where people start arguing about naming or abstraction, there’s a way to simplify things further so it’s readable for everyone and easier to use inline. I always look for those now when I’m reaching for “you should rename this” or “you should restructure this” kind of comments.
The Mt Weld rare earths mine located in the Goldfields Region of Western Australia is one of the highest grade rare earth mines operating in the world [1].

The ore is initially drilled and blasted and the blasted ore is excavated and loaded on to trucks. The trucks transport the mined ore to the concentration plant located 1.5km away from the mine.

The ore at the concentration plant is crushed before being fed to the ball bill, after which it undergoes flotation. The flotation concentrate is thickened and filtered and the final concentrate is subsequently shipped to the east coast of Malaysia to the Lynas Advanced Materials Plant in Kuantan, where the concentrate is processed [2] to produce separated Rare Earths Oxide (REO) products.

Step [2] is the significantly nasty step and typically occurs awy from mine sites that produce concentrates for input.

For further overview, see (for example): Rare Earth Elements: Overview of Mining, Mineralogy, Uses, Sustainability and Environmental Impact [3]

[1] https://www.nsenergybusiness.com/projects/mt-weld-rare-earth...

[2] https://lynasrareearths.com/about-us/locations/kuantan-malay...

[3] https://www.mdpi.com/2079-9276/3/4/614
Break their parser, probably
> this is probably a strategic mistake

A larger strategic mistake would be having lots of very large and both military and natural disaster vulnerable tailings ponds everywhere in your country "just because there is the possibility of a strategic mistake if we don't mine stuff".

It doesn't take more that a dozen of those Tailings dam failures to completely ruin a small country.
The NOTAM system is something that a room full of decent engineers could easily build from scratch and make it infinitely better in a short time. It’s essentially just a database of categorized posts with some APIs for sending entries and and returning them when requested. These government IT teams spend way more than what it should cost and end up with bloated ancient tech that barely works.

That’s not speaking poor of the engineers (which in my experience can be very good) but of the management and innovation culture of these agencies, which is too often terribly broken. They would say they are “risk averse” but as yesterday highlights their poor approach to this creates a ton of risk.
FTX pre-mortem overview
Thanks, that's reassuring.
The whole business is full of one-way bets where you either escape with the money or go bankrupt/get arrested. I think they may have assumed that law enforcement in Bulgaria was not sophisticated enough to be interested in them.
Open fireplaces suck a huge amount of air from the room. It was once explained to me that in one particular case (a specific house) the open fireplace would typically suck 150 cubic meters of air every hour, when that was replaced with a wood stove it went down to 15 cubic meters/hour. So, an order of magnitude of difference. Those numbers shouldn't be taken as accurate of course, but at least that house got much warmer simply because they didn't have all that air sucked in from outside all winter.
15% revolutionary LARP, 15% intent to cause damage/mayhem, 70% self-guided tour of Congress. If it were given the same benefit of the doubt as the BLM riots, it'd be classified as mostly people showing up to a rally because their idol told them to with bad actors leading the charge after he told them "go home".

The dollar-store gallows picture is still laughable.
It would be very useful to say have a locale called U or similiar that would have standard things like: encoding UTF-8, ISO 0601 date time, A4 paper size, en-US language, etc.

Does anyone have a an easy recipe to define my own?
I checked the sample Kubernetes project in Java [0] and it looks hideous. YAML looks much better in comparison.

[0] https://www.pulumi.com/docs/get-started/kubernetes/review-pr...
I was one of them, and it took me burnt hard many times for me to change.
I'm really puzzled about where "they're brilliant" comes from. Are you not brilliant too? If nothing else, at least brilliant at writing good code?

Their code has no consistent style? Sounds like you need a coding standard. Everybody should be using the same style, and should be using it consistently. Use tools to enforce your coding standard if you can (auto-formatters and code analysis to enforce naming standards and check spelling(one of my favorite analysis features!)).

Paragraph spacing in code? Your coding standard needs to specify that code is written for the person that follows (i.e. readability and maintainability is a primary goal). Pretty much a boilerplate clause in a coding standard. With that in hand, you have ammunition to back up an discussion about whether paragraph spacing in code improves readability. (I'm inclined to think that it very much does).

As for the rest... I worry that you may be micro-managing. The discussion about dynamic or static initialization is a totally normal and expected sort of conversation to have (without regard to whether you were right or wrong). A discussion happened. You pointed out an easier way to do it. Great. But it doesn't seem productive to me to agonize for hours over a coding decision that probably took under a minute to implement. (If you were able to initialize statically, surely it couldn't have been difficult to write equivalent dynamic initialization, and to reason about it's correctness).

A decision to cache an initialized data structure. Not really that difficult to implement; and not really that difficult to reason about. I think you just need to trust your team members to make reasoned decisions about that sort of implementation detail.
¿Has decidido mudarte? ¡Te ayudaremos!
mudanza, servicios de cargadores r
Transportamos cargas pesadas y de gran tamaño
Proporcionamos los servicios de los cargadores, el embalaje de la carga, el montaje y el desmontaje de las cargas
Ofrecemos una plataforma para subir al piso 650070707 ayuda@mudanzer.es
> I couldn't tell you anything about the film other than

The bit where he says "What's this, my mantra?" and the monk says "No, it's the wifi password".
Imagine it is a human driver saying that shadows on the road made him believe there was a person there so he slowed down to make sure.

He wouldn't be at fault for slowing down (after checking his eyesight).

Lane change is what makes Tesla at fault here, not unreasonable slowing down.
Show HN: New Visualizations for Chess Enthusiasts (Link only)
Hello HackerNews, I'm happy to share my newest analysis video of the recent Chess game between Magnus Carlsen and Nodirbek Abdusattorov in the World Blitz 2022.

I had previously put out some videos in a similar style on the channel but wanted to see how far I can get the visualizations and how much I can automate it with python. The biggest time sink when creating these videos is adjusting the individual parts of the video using matplotlib, which I can mostly reuse across videos. Here is what I show in the video beside the chessboard:

The bottom visualization shows the engine evaluation across different depths, which allows you to (1) follow the engine evaluation of the game and (2) compare evaluations across depths to find surprising moves (which I originally implemented for this repo: https://github.com/CYHSM/chess-surprise-analysis).

The right lineplot indicates the number of games which have previously reached the highlighted position. This allows you to see when a completely new game starts (Thanks Agadmator) with steep drops indicating more exotic lines. The title in the plot also indicates the opening name, for as long as they are identified.

Please let me know what you think and if I should upload more videos in the same style.
Just because a movie looks better doesn’t mean it is a better movie. There has been trash made during all eras, but today is about volume, not quality, so finding the gems is much harder and frustrating.

Do we really need to have another movie about super heroes or another movie about rescuing some retiring tough guy’s kid from a bad guy? Or another movie that spends the first half rotating between character building scenes filled with silly, rote dialogue and no story line? Or another movie that takes an old, tired story and simply replaces the characters with a new set of characters intended to signal the importance of a particular demographic group? Or another Jurassic Park, Hangover, Rocky, Transformer, Terminator, Star Wars clone? Yawn.
With that logic anything we do for the climate is green washing. While your thoughts are catching on, Sweden has always been a nation of mining.
I’d add some tourist desirability factor and quality of life factor
It's wonderful to see his work being recognized. I was in bioinformatics grad school when the first major Neanderthal sequencing paper came out and it was a bombshell.
Actually it is quite the reverse, environmental damage in colder area takes much longer to recover.
There’s also tungsten: “tung” is heavy, and “sten” stone in Swedish.
There's HOCON which is pretty good if you can run on a JVM. It's a superset of JSON designed for readability and human-friendliness when writing config files. It doesn't change the type system and doesn't have yamls weird edge cases, but is still a lot easier to write than JSON. There's also a relatively tight spec.

https://github.com/lightbend/config/blob/main/HOCON.md

We use an extended version of it for our app and the resulting config is pretty clean. You can see an example here:

https://hydraulic.software/blog/8-packaging-electron-apps.ht...

The only downside is that the reference implementation is hardly maintained anymore.
If you haven’t read Stables and Volatiles[0] it’s a great place to start. It’s comforting to know that this is a common, structural management problem and not some one-off. Lots of engineering teams in lots of organizations have faced your challenge.

One of the things the blog post does really well is explain how a volatile can be valuable (even essential) in the lifecycle of a company. I personally tend to lean more toward volatile, so I can appreciate the tensions your colleagues are facing.

I have a few recommendations…

1. It’s very likely they don’t see the value of collaborative team work. You will all benefit from them coming to see the team as important. There’s no magic bullet here, but they’re still human and hopefully reasonable. Questions and conversation can help.

2. It’s possible they’re actually just insecure assholes. If so, work to remove them from the team ASAP. There’s no room for assholes.

3. If they are a volatile and they’re in a team which mostly benefits from stability, try to find a problem which is substantially challenging and useful to the team which you can hand them.

4. If there is no opportunity for that kind of challenging work, they might not be a good fit for the team long-term, and management owes them honesty about their fit.

Overall, I hope it works out for your team. Personality and work-style dynamics are tough but I have seen big changes on teams happen, and it’s possible for yours too!

[0] https://randsinrepose.com/archives/stables-and-volatiles/
get your or his supervisor to contact instead and problem solved.
I haven't used it for years and I have never looked back! Even in extremely large systems, manually writing a mapping layer is quick (although admittedly obnoxious) and has helped me identify issues so much easier.
Most of the good places in New Haven (Pepe's, Sally's, ...) didn't even do slices. New Haven style requires a fresh, whole pie.
They will be made to allow it. And hopefully that guys reign is nearing its end.
> a whole different approach is needed
Why not tell us something about this approach ?

Unless it's doing nothing.
> Also wouldn't want working parents to spend time with their kids instead of doing mundane household chores

I love how the answer to "modern life doesn't leave enough time to do basic human tasks" is "buy a $1k+ soon to be e-waste LIDAR powered AI enabled fully autonomous vacuum cleaner" instead of "fix the damn system". We truly have completely lost our collective minds somewhere since the 90s
Almost none of that is correct, except in the specious sense that most of those technologies run on electricity and electricity is still made from fossil sources in most areas. In some cases it's sort of laughable: solar panels are just semiconductors, everything about that industry is electrified (most of the power input is in growing the wafer out of molten silicon).

Basically your argument is circular: you're saying that renewable electrification can't happen because electricity is made from carbon. But as electrification proceeds that becomes untrue by definition.
If your org was hacked by the Russians/Chinese and was a national safety system, then you might be right to start there.
This is the town where the deposit was found: https://cdn.britannica.com/85/117985-050-36D70897/Kiruna-Swe...
> Mobile-native filmmaker Mike deGruy

Sign of the times I guess, my first instinct when reading this line was that it was a term for people creating films using mobile phones/gopros rather than traditional cameras. It actually means the city of Mobile, Alabama.
I've worked with plenty of these people in the past, and I've mostly abandoned hope for them.

Most of these issues stem of from a lack of understanding in the importance of designing a system that is simple consistent, where the least possible context is required to work with it, that is robust to refactoring and debugging, that other can work with as well, etc.

Unless they're actively trying to improve themselves with the criteria you dictate, it'll be an endless battle to get good output from them -- the management equivalent of the relationship cliché "They're damaged but I can change them".

My only approach now is to isolate them in discardable islands of code or firing them to improve team unity. Only keep if young and really willing to change and stick around.
Referring to Twitter not paying rent for some of their office space I assume, which was allegedly part of a renegotiation tactic.
If you can still trust Eufy

https://www.theverge.com/2022/11/30/23486753/anker-eufy-secu...
As one could argue that the earth is flat and nothing is real.
I think problem in this particular case is using YAML as DSL. Every other data format would be equally bad here. Replace YAML with TOML and you're still in same templating hell.

YAML is least worst for me, and I don't think I ever hit the problems article is showing because

* I use editor that will highlight stuff like anchors

* I often generate config from CM so it can't have those errors

* Loading into defined struct in statically typed language also makes them impossible.
Thule comes from a Greek cartographer, Pytheas. Thule was supposed to be an island to the north of Britain, but nobody knows what he referred to or if whatever place he referred to even was real. Some people, especially 19th century Scandinavian nationalists, associate Thule with Scandinavia.
I see nothing wrong about closing tag. Helps to navigate and understand in my opinion. I have way more problem with developers trying to be super concise and writing constructs that are very hard to parse mentally when looking at.
> X continues to be the Linux standard

Part of it is, of course, that it is not just the Linux standard. It's also the FreeBSD, OpenBSD, NetBSD, DragonflyBSD, GNU HURD, Minix 3, Solaris, OpenSolaris/Illumos, AIX, HP/UX, z/OS, and OpenVMS standard.

I am sure I missed some currently-maintained OSes in there.

X is a core part of the interoperable, cross-platform, open systems world, as it has been for decades. Since most of those will never undertake large new development now, it will probably never be replaced in this, but some of those systems will keep running the world for decades to come, until the collapse of technological civilisation.

Personally, since nobody can kill off or totally replace X, my suggestion is that we collectively decide what bits we don't need any more, and cut it down to the core stuff that we need to keep.

Byte-swapped clients just were banished.

Why not get ruthless and strip out all the ancient stuff that nobody uses in the 21st century, keep just the essentials, and call the result X12?

I am no expert in this area but I gather that most of the font server stuff is obsolete now. It is probably safe to assume only 24-bit colour now. In the mid-1990s I ran X11 over DECnet on VAX/VMS. I am sure everything but TCP/IP can go now. I am willing to bet there is lots of other stuff that could be removed, leaving a smaller, more maintainable core that someone somewhere is going to need for years to come.