skysight-inc/HackerNews huggingface dataset:
> My constitutional law professor did some CRT scholarship in the 1980s and brought this perspective to our class* in an interesting way

Exactly. Which is why it's bizarre to suggest that liberal professors at NYU and Northwestern are suddenly upset in 2022 about something that was routinely taught when they went to law school. It's more reasonable to assume that they're responding to something else that they're observing.

> * circa 2009, when "CRT" was better known as a near-obsolete display technology than a boogeyman of the American political right.

"CRT" is just a vernacular shorthand for a collection of ideas that have become prevalent in certain circles in the last few years, which share common threads such as abandoning the ideal of race neutrality in law and policy. It's similar to how "supply-side economics" being used to refer to Reaganite economic policies. Whether those ideas are technically CRT is beside the point.

Opposition to that collection of ideas is not limited to the "American political right."

Insofar as "CRT" encompasses, for example, Ibram Kendi's assertion that positive discrimination is required to overcome past discrimination, most Americans oppose that: https://www.pewresearch.org/fact-tank/2019/02/25/most-americ... (in college admission); https://www.insightintodiversity.com/majority-of-americans-b... (in hiring decisions).

Insofar as "CRT" is associated with various left-wing criminal justice ideas, most Americans, including so-called "people of color" oppose them: https://www.pewresearch.org/fact-tank/2021/10/26/growing-sha...

The "American political right," moreover, is hardly the only one that has realized that these ideas and policies share common roots. Emmanuel Macron, of the French center, has come out against them too: https://www.newsweek.com/macron-france-reject-american-woke-...

Insofar as more Democrats don't oppose CRT, I suspect it's because they haven't heard much about it or are skeptical that it's just a right-wing effort. But I sent this article to my dad--an immigrant from a Muslim country who has supported Democrats since Carter--and he expressed concerns about "critical race theory." Because he's a strong proponent of "color blindness" as a foundational principle of law and society. He was alarmed, as a public health expert, by proposals to prioritize non-whites for vaccinations. He was likewise alarmed by TJHSST, the high school I attended, recently abandoning its admissions test under the theory that it was "racist." I suspect there are a lot of Democrats like him who are skeptical that Republicans are acting in good faith, but don't actually agree with progressives that we need fundamental changes to our legal system.
Hex scores $52M Series B
First comer advantage. Initial Java was a robust, yet simple, sane build tools, relatively safe, typed language when most everything else was c or c++ and not as "safe" (modern c++ is actually very safe language if you stick to its guidelines however). Over time Java has become almost as complicated as Modern C++ but people picked it up over time mostly. It's still used because it's still a robust general purpose language, tons of libraries, huge corps don't like to rewrite things, and there are lots of Java programmers out there. Don't let the webstack blind you, there is a whole other world out there of backend, embedded, finance, and legacy stuff that hackernews audience is just a small part of.
Yes - Please contact us at ask@realitydefender.ai
Investors see growth opportunity in Femtech devoted to women’s health
APL Problem Solving Competition 2022
Hacking Google Maps with a wheelbarrow full of phones
Why? I get no discernible benefit as a user / customer from Facebook operating at this scale. Why would I "just accept" this?

Your comment reads like this:
https://www.newyorker.com/cartoon/a16995
Why is graphic one "clearly a violation" and "we need to kill more" isn't?
What gitlab features do you utilize where latency actually is a problem?

I currently manage an internal gitlab instance with some remote coworkers, but I haven't heard any complaints about latency. Although tbf, I feel like we've barely scratched the surface of what gitlab supports
Clojure 1.11 is now available
That's not what it means at all. It just means you find it easier to work outside of the spec's design. He's very clearly saying that if you are doing that, it's always possible to avoid it and work within the intent of the spec instead. If you're happier working outside of that, good for you. The "logistics" of you needing to get your work done has no bearing on what the designers of the tools you're using intended.
Yes exactly! But it seems like the breakers for the internal circuits were turned back on repeatedly by whatever system was doing a "reprise automatique du courant".I guess that means UPS power back ups, but why would those not be shut off automatically either by the fire alarm or just the breakers? Maybe they weren't, it's not really clear, but it's surprising to me that the breakers would not cut all current if they are damaged? Do fire-safe breakers exist?
The most surprising and interesting finding from this article for me is that Majorgeeks is still around.
My company runs without containers. We process petabytes of data monthly, thousands of CPU cores, hundreds of different types of data pipelines running continously, etc etc. Definitely a distributed system with lots of applications and databases.

We use Nix for reproducible builds and deployments. Containers only give reproducible deployments, not builds, so they would be a step down. The reason that's important is that it frees us from troubleshooting "works on my machine" issues, or from someone pushing an update somewhere and breaking our build. That's not important to everyone if they have few dependencies that don't change often, but for an internet company, the trend is accelerating towards bigger and more complex dependency graphs.

Kubernetes has mostly focused on stateless applications so far. That's the easy part! The hard part is managing databases. We don't use Kubernetes, but there's little attraction because it would be addressing something that's already effortless for us to manage.

What works for us is to do the simplest thing that works, then iterate. I remember being really intimidated about all the big data technologies coming out a decade ago, thinking they are so complex that they must know what they're doing! But I'd so often dive in to understand the details and be disillusioned about how much complexity there is for relatively little benefit. I was in a sort of paralysis of what we'd do after we outgrew postgresql, and never found a good answer. Here we are years later, with a dozen+ postgresql databases, some measuring up to 30 terabytes each, and it's still the best solution for us.

Perhaps I've read too far into the intent of the question, but maybe you can afford to drop the research project into containers and kubernetes, and do something simple that works for now, and get back to focusing on product?
Thanks for expressing how I feel about R so succinctly.
> Due to R-studio being the default, there's not much support for other editors.

But RStudio is amazing... Easily best environment I've used for any programming language (well, except Pharo).
Another DNSSEC screw-up takes down thousands of .au domains
Most of the cases where this breaks anything, are already broken, it's just not visible.
Is there a tutorial someplace that explains how ggplot actually manages plotting? Or the architecture and layers between the high level code and how a plot is drawn? Meaning, I love being able to express what I want and ggplot figures out a good plot for me. But I know there are many layers that can be manipulated, but I just don’t understand the layers.

One of the best compliments I can think of is that with ggplot, easy things are easy and hard things are possible. But I haven’t been able to figure out how to fully work the system.

(Thanks for all of the work!)
Neither by default. I look to be convinced that they've implemented containers because it made sense for their technical architecture or strategy.

I have a vendor who pitched their new "cloud-native" re-platforming project and it really spooked me. It's data management-type tool that was migrating from a traditional on-prem client/server architecture to an AWS-hosted Angular interface with a MongoDB backend. I got the same pitch a year later and the entire stack had changed. I was spooked the first time; now I'm really spooked and thinking about migrating off the platform.
Facebook, Instagram involved in “extremist activities” Russian court rules
Even with four teams, I've found a lot of instances of people building the same thing. That wouldn't necessarily be bad, except often those 'things' fall into a space of errors that almost everyone makes until they learn/are taught to stop doing it.

So you notice that there are 2.5 implementations of a bit of logic because there are bugs, maybe security bugs, that cross 2 of them or are different on each.

I have found that once the code exceeds the size of one brain, it accelerates because if I don't know code exists, I will write it again. Like driving down a mountain side with the brakes on the whole way, eventually the sanity leaves the system and you go careening down the mountain.
Maintaining an entire secondary deployment and CI system just seems unrealistic to me. I'd get so much flack about the extra spend and when the systems get out of sync and causes downtime, that investment ends up with net negative for all involved.
She didn't go to law school, she's not part of that world.

Think about how many articles get tech stuff wrong. Articles about law tend to be even worse because of the political/emotive aspects, which writers (such as here) try to inflame.
Gentrification arguments are almost always about renters. Neighborhoods that are subject to gentrification will usually skew renter, too, because they were redlined not too long ago and so the families who lived in them couldn't get on the housing ladder / families with the means to get on the housing ladder moved elsewhere.
Status pages are just not reliable unfortunately.
On my team, the level of scrutiny a merge request receives depends on the author and the functionality. MRs from a principal or lead engineer tend to get rubber-stamped at a higher rate, though, to your point, many of us will explicitly call out code that we would like to have reviewed in more detail. If a more junior level developer submits a merge request, it is highly likely their code will get a close review.

I'm not sure I agree with your premise that code reviews are the product of a culture with a lack of trust and ownership. I think, in fact, submitting to a review process is a sign of ownership -- it's saying "hey, the quality of the code we produce as a team is important to me, and I know I make mistakes."
Notification is required only if their impact assessment concludes on a significant risk to users (which they must be able to produce to the data protection authority at any time).

Otherwise, business as usual.
I've seen many articles and comments about apnea and its serious consequences. The thing is, I have no idea if I have it. As far as I know I sleep fine, so I don't bother looking deeper, but I have this nagging FOMO doubt that I could maybe magically drastically improve my sleep. Wish there was some simple test that could rule out even starting down this rabbit hole.
On the other hand, a good memorization skill must not necessarily mean you come to the right conclusions. Your sources, peers, genetics and a mind that is by nature chaotic, do it's part.

For example, having good memory may lead you to become more arrogant. If other people praise you for your skill, you become so confident in your conclusions that you stop questioning them and rather see confirmation in an echo chamber of sources.

This arrogance is the source of much evil, I think. You see it a lot in politicians and management.
Yes on trust. However… I'm pretty darn experienced in what I do these days, and every day I still write a bit of crappy code, usually as I come to an understanding over time of the current problem. WTFs come from code written six months ago as well as yesterday. If someone can point out an issue early, it saves everyone time. So, I welcome it.
You are correct though she isn't the author, but everyone in this thread assumes she is haha

(The actual author also seems unqualified to argue the issue)
The edit is really insightful. I’ve had vaguely similar thoughts, but this is the first time I’ve seen it stated coherently.

Any resources for reading up on this point of view?
2022.1 is coming shortly. In any case, one can easily specify jdk18 as the platform to use for a project. The IDE might not recognize some syntax, but the code will compile and run just fine.
I thought it was "See One, Do One, Train One"... which might actually be worse!
While a lot of the post is good info, there are some upsides, if we can get the EHR situation worked out.

Many years ago, prior to anything like ML, Canada figured out that cystic fibrosis patients whose weight is higher than 50th percentile, had significantly better lung function. Nobody really understood why, but the correlation was so strong (.85 or something like that) it could not be ignored. Treatment protocols for CF changed to encourage weight gain, and lifespan outcomes have steadily improved over the years.

What other oddball correlations are hiding in the depths of bloodwork, weight/height, etc. for patients? We've teased out all the easy ones, the ones that are left are combinations nobody thought to even measure.

Regarding the EHR debacle, I'm optimistic that something could be worked out as a standard and implemented across the board. Expensive? Sure, but it's an investment that pays off pretty quickly, I think.
I read metehack's comment completely the opposite way: that a working records system is part of a functioning medical system and a consequence of a decision to have such a system.

In other words I interpreted the comment as making the point you make.

Having benefited from the French medical system (and having it treat my dad when he was visiting us) it's really quite good. People in the US (where I live) would laugh if they heard the way French people complain about their health care system: it's a dream by comparison. French complaints are like an American complaining that there is "too much room"
IMHO storage is the big issue to figure out with a production ready gitea installation. Gitea only supports the local filesystem for storing bare repo data and not anything like S3 or other distributed or highly available storage systems (it supports S3 only for git LFS data right now, it is a long awaited open issue to get the bare repos there too).

So the big issue for any non-trivial or highly available setup is going to be how you get high availability for the local storage volume. There are tons of options with various tradeoffs and levels of complexity here--simple local disk RAID, distributed filesystems like gluster or ceph, etc. I think this is the real crux of getting a good gitea instance going.

No matter what figure out and test a good backup and recovery solution!
What a great service. I'd be curious if you could go into details how the radio feature worked back then, because I found myself receiving worse suggestions when I used similar features in Spotify/Google Play Music.
Have you ever been in a traffic jam and seen cars taking the shoulder to pass everyone and exit? Google would need to listen to the masses and ignore the few breaking the law.
Haha I know what you mean - but realistically all the government really needs to do is provide specification and fund it, while having the courts uphold its reliability.

for example, Google could provide the service - but they would have to avoid co-mingling the service with their existing one. They wouldnt have the same rights to the content within the email as they do with a gmail account. And they wouldnt be spam filtering small businesses into oblivion for trying to talk to each other directly.

technically the service can be fulfilled by multiple vendors adhering to the same specification.
JavaFX isn't guaranteed to be in a JVM. You run into "deprecated" APIs that were removed. JVM options change, and that breaks how things are deployed. If the JVM were a stable target a site like http://whichjdk.com/ wouldn't be necessary.

This is just how things are. It's Java fanfiction to say this isn't the case, and necessitates having multiple JVMs installed.
Probably not for the most of the tech companies nowadays, but there are still large companies who still uses Oracle products, so they might pay Oracle Java support as a package deal most likely.

I think it'll be very atypical for a companies who doesn't use any of the Oracle product to use proprietary Oracle Java and pay for the support
> Git is distributed

It's distributed into https://github.com

i.e. not in any real sense at all.
I really wish that these services would stop requiring text records at the root. Ideally the key would be whateverservice-$RAND but at the very least put it under whateverservice.
There's actually been a pretty good report by the President's Council of Advisors on Science and Technology on this subject a while back:

https://www.healthit.gov/sites/default/files/pcast-health-it...

It did not place the blame on insurance companies. Which I think is correct. Insurance companies affect billing, but they do not drive health care records management. That's driven by an entirely different set of companies such as Epic and Meditech.

And the poor state of EHR in the USA is not entirely their fault, either. A lot of what went down is that universal standardization was not a major part of the requirements when the US government started requiring health IT. So health care providers decided to favor preserving their existing policies and procedures, which meant choosing extremely configurable EHR systems that allowed them to computerize their old paper-based systems with minimal modification. Since easy computer interoperability was never a design goal of those paper-based systems, it was not inherited by the EHR systems they grew into, either.

This creates a situation where even two Epic customers, despite being on the same EHR platform, are still hard-pressed to directly transfer records between their systems, and are as likely as not to still just fax or email each other printouts because it's easier.

And standardizing and perfecting insurance and billing would do nothing to fix this situation. The two systems are likely to be connected, but they are not the same thing.
What if the person doesn't maintain their car? What if they drive through mud that partially covers some sensors? It seems like there are lots of things outside the control of the manufacturer. It's probably best to see if any future accidents are because of errors with the system or end user errors. Anything else is doomed to failure.
The article doesn't seem to contain anything about listening with empathy.
>"These regulations aren't created just for fun, they're created because people died. Let's not take a step backwards."

Of course, and I realize that, I think we all do. The question, though, is at what point is a regulation more expensive than it is practical? It sounds heartless but some regulations don't seem worth the expense of how many lives it is designed to save. One of the reasons why the 4 prong outlet is required for dryers is because someone was changing the inner light bulb in the dryer and killed themselves because they didn't shut off power to the circuit. The regulation is meant to help prevent this in the future, but one has to wonder just how many people are actually being saved by this update. Especially when you personally have to shell out something like $750 to update your three prong outlet.
Eastern EU has been taking national security very seriously. Western EU has not, because Eastern EU serves as a set of buffer states for it.

The US can complain about this state of affairs all it wants, but it needs to remain in EU's good graces, if it wants to maintain its hegemony.
This is puzzling. If I had billboard in the middle of the city, and I'd get paid for a "kill all $group_name" ad, all while people are actually killing $group_name, in what world will it not make total sense to hold me accountable? They're literally making money of the war.
Considering that FB stock price has dropped to about where it was at the beginning of 2017, just from a tiny recent decline in DAU...It now has 1.9 billion DAU vs 1.2 billion then. Wasn't it insanely overvalued back then? FB has been endlessly tripping forward, trying to justify its insanely overvalued stock price since its IPO. Its value reflects the market's speculative estimation of the platform's value...to advertisers, not users.

I say, in all brutal honesty, I give zero fucks about a company going from a $900 billion market cap to just a mere $600 billion. Cry us a river already.
Some of my best coding interviews have been async take home projects. Plaid actually had a time-limited (2 hr) take home interview where I had access to a github repo with instructions.

Seems like there is a lot of promise here, as Fairlane could help companies like Plaid automate this takehome process in a scalable way for candidates.

That said, I only see this working for very early screens. Do you have plans to support later stages of the interview process?
There are a range of treatment options out there, and we focus on FDA-cleared devices that are supported by clinical efficacy studies.
which doesn't change anything I wrote at all

not everything on their docket has the same weight of importance as the other things on their docket, nearly everyone thinks the thing on the docket that they care about is more important than the other thing

just something to keep in mind when someone is trying to get you to pay attention to their cause
In practice, how often are you interested in it? C# has `Object.referenceEquals()` because you _may_ want this sometimes. But to have reference equality be the default for something like `==` is a design flaw. Not one that can be fixed now, of course, but it will continue to cause bugs for years to come.

Sometimes, it happens in core Java libraries themselves: https://bugs.openjdk.java.net/browse/JDK-8274779

https://github.com/openjdk/jdk/blob/722d639fad2e4fc6eb2aabd4...
Aha! That could make sense ~Access Denied. Thanks for responding! Good luck, will keep an eye on this ;)
‘Spam Nation’ Villain Vrublevsky Charged with Fraud
Re: charging into battle, I think the focus of the question was the pug.
I've noticed a phenomenon where I sometimes have to comment about something near the pointy end of the code review pyramid in order to get my brain into the correct mindset to really start grocking how and why someone has made the changes they have. After I break this barrier it often leads to the deeper questions about whether it is doing what it supposed to be doing.
You removed the requirement but the field is still there and nothing says the field is optional. I read your reply as "we removed the field".

FWIW I think it's reasonable to collect emails. But at least be honest as to whether the email field required (or not) on the form.
Accountability is a lot more than having a name you can legally blame. Firing and suing ad approval worker #1632 for mistakenly approving 8 ads doesn't provide accountability towards solving the problem it provides a scapegoat.
The certificate transparency log is also a good place to look for clues. ⁨https://crt.sh
Dungeon Alchemist – AI-Powered Map Generator
BMP forever! The most disgusting thing I've read today.
5 years of a Gogs instance. Zero downtime. I'll come back to you when it goes down.
North England vs. the Netherlands
A SAAS company never breaks an SLA. SLA's are written by the legal team. Uptime is maintained by the engineering team. They aren't even in the same building.