HNHacker News
TopNewBestAskShowJobs

status_quo69

271 karma · joined November 29, 2016

submissionscomments
status_quo69··on A petabyte of health insurance prices per month
We do have this in a way with healthcare.gov, since the marketplace allows consumers to view multiple insurers rather than those tied to their jobs. However these plans are still pricey, I put in some dummy data with a higher than average income (60k) and got plans at 280 per month at the bottom of the barrel. Seems to me like it's a good step in the right direction but the marketplace doesn't have an actual market driving force to reduce prices even with the 11 million plans selected for 2023. Having worked in healthcare billing processing software, this lines up, insurance companies really don't give a shit about reducing prices to compete since consumers at the point of billing are always a captive audience (if you don't have it and you have an emergency, you're fucked)
status_quo69··on Microsoft Freezes Salaries for 2023
It's not secretly a salary cut, it's an explicit salary cut relative to the cost of living and everything else. After all, your money is worth less now than it was a year ago if there's no cost of living increase? I'm sure the initial circumstances of salary negotiations for a position took into account current economic factors. I'm much less likely to want to stick around at a company that cannot compete with living expenses with a general 2% increase YoY. That screams stiff/cheap or that the company is on the cusp of folding.
status_quo69··on Biggest industries burn through $7.3T of natural capital a year
Should the opposite should also hold true then, we should dismiss staunch capitalists that continue to believe in that economic theory in spite of the atrocities perpetuated by most capitalist societies against people in adverse conditions? Seems a bit knee jerk to dismiss things wholesale.
status_quo69··on Nobody wants to teach anymore
> This is against the site's rules.

I apologize, that was a knee jerk reaction because I've never seen the assertion that 2+2=4 is racist before, only that math can be used inaccurately (purposefully or by accident) in racial contexts. I was a bit taken aback by the assertion and should have engaged differently.

> Funny how you build up a straw man. I never claimed any of that.

This isn't a straw man, I'm not building up some contrived argument here; the original comment was that "2+2=4 is racist" is a rallying cry for [some not insignificant number of math teachers].

> For example the Wall Street Journal. And hundreds of similar articles.

I did find this Opinion while googling, and read the parent Op-Ed (https://www.wsj.com/articles/california-leftists-try-to-canc...) and then followed through to the framework but I just don't see anything about the manual they were talking about in that Op-Ed in the works cited (seems like all references to the manual have since been removed). So I dug up the wayback machine on the page to see the context in which they were using the "A Pathway to Equitable Math Instruction" manual.

> A Pathway to Equitable Math Instruction (https://equitablemath.org/) is an integrated approach to mathematics that centers Black, Latinx, and linguistically diverse students in grades 6–8, addresses barriers to mathematics equity, and aligns instruction to grade-level priority standards. The Pathway offers guidance and resources for immediate use in planning their curriculum, while also offering opportunities for ongoing self-reflection as they seek to develop an anti-racist mathematics practice. The toolkit “strides” (above) serve as multiple on-ramps for educators as they navigate the individual and collective journey from equity to anti-racism. It is a collection of resources to help grades 6–8 Black, LatinX, and linguistically diverse students thrive in mathematics education.

Ok so generally seems like they're recommending the usage in primarily POC or mixed classrooms where the considerations for teaching might be a bit different due to a multitude of factors.

Now digging into the manual a bit, the titles are definitely inflammatory but the content is honestly fairly humdrum (quotes taken from the first chapter https://equitablemath.org/wp-content/uploads/sites/2/2020/11...)

• Teach rich, thoughtful, complex mathematics. • Teach rigorous mathematics, understanding that rigor is characterized as thorough, exhaustive, and interdisciplinary. • Use mistakes as opportunities for learning. • Recognize mistakes as miscommunicated knowledge. • Allow for engagement in productive struggle • Teach students of color about the career and financial opportunities in math and STEM fields. • Encourage them to disrupt the disproportionate push-out of people of color in those fields. • Invite leaders and innovators of color working in STEAM fields to meet your students. • Rely on teamwork and collaboration as much as possible. • Teach mathematics through project-based learning and other engaging approaches. • Provide multiple opportunities for students to learn from and teach each other. • Intentionally include mathematicians of color. • Expose students to mathematicians of color, particularly women of color and queer mathematicians of color, both through historical examples and by inviting community guest speakers. • Teach students of color about their mathematical legacy and ancestral connection and mastery of math. • Honor and acknowledge the mathematical knowledge of students of color, even if it shows up unconventionally. • Give rightful credit to the discovery of math concepts by mathematicians of color. Reclaim concepts attributed to white mathematicians that should be attributed to mathematicians of color.

Which all seems fairly reasonable here to my eyes. I will 100% agree with any assertions that the titles are very standoffish and even straight up accusatory but the content of the manual really seems like something good teachers should strive for. So to conclude I don't think that 2+2=4 is racist is really a rallying cry, the literature cited everywhere seems to talk mainly towards the teaching methodologies employed.

status_quo69··on Nobody wants to teach anymore
> The rallying cry seems to be that "2+2=4 is racist".

Source? This is such a wild claim it has to be made up. A cursory google search brings this article: https://www.edweek.org/teaching-learning/teaching-math-throu...

Which is distilled down to "teachers teach math in a way that is topical to the current environment, such as BLM protests which is really nothing new. You might disagree with it, sure, but to say that this is "the wokes" teaching 2+2=fish, that's frankly ridiculous.

In fact, the only thing I can find reporting on "2+2=racist" is this Washington Examiner article deriding a math teacher from NYC for her tweets (article here: https://www.washingtonexaminer.com/news/math-professor-claim...) which sounds _awful_ but it's a single person tweeting, and it seems to be in relation to using "math is pure and objective so it always must be neutral" as a defense for situations where data/statistics/algorithms presented show a clear bias. Which I think generally is an agreed upon phenomenon-- depending on the sampling and interpretation of the data, folks can come to _wildly_ different conclusions, especially if data was accidentally omitted.

Best example of this phenomenon is facial recognition software, which can perform very badly when deviating from the sample data. https://www.nist.gov/news-events/news/2019/12/nist-study-eva...

> For one-to-one matching, the team saw higher rates of false positives for Asian and African American faces relative to images of Caucasians. The differentials often ranged from a factor of 10 to 100 times, depending on the individual algorithm. False positives might present a security concern to the system owner, as they may allow access to impostors.

...

> However, a notable exception was for some algorithms developed in Asian countries. There was no such dramatic difference in false positives in one-to-one matching between Asian and Caucasian faces for algorithms developed in Asia. While Grother reiterated that the NIST study does not explore the relationship between cause and effect, one possible connection, and area for research, is the relationship between an algorithm’s performance and the data used to train it. “These results are an encouraging sign that more diverse training data may produce more equitable outcomes, should it be possible for developers to use such data,” he said.

All the other sources I found on google were either think tanks, facebook posts, or spam sites.

ETA: even in the most pessimistic reading of those tweets, I'm personally hard pressed to find that one person tweeting means that all math teachers everywhere are trying to take math down to "2+2=racist"

status_quo69··on Kubernetes is a red flag signalling premature optimisation
Having very recently done this (almost, another dev had half time on it) solo, It's not _too_ terrible if you go with a hosted offering. Took about a month/month and a half to really get set up and has been running without much of a blip for about 5 months now. Didn't include things like dynamic/elastic scaling, but did include CD, persistent volumes, and a whole slew of terraform to get the rest of AWS set up (VPCs, RDS, etc). I'd say that it was fairly easy because I tinkered with things in my spare time, so I had a good base to work off of when reading docs and setting things up, so YMMV. My super hot take, if you go hosted and you ignore a ton of the marketing speak on OSS geared towards k8s, you'll probably be a-ok. K8s IME is as complex as you make it. If you layer things in gradually but be very conservative with what you pull in, it'll be fairly straightforward.

My otherhot take is to not use helm but rather something like jsonnet or even cue to generate your yaml. My preference is jsonnet because you can very easily make a nice OO interface for the yaml schemas with it. Helm's approach to templating makes for a bit of a mess to try and read, and the values.yml files _really_ leak the details.

status_quo69··on Supreme Court Overturns Roe vs. Wade
Because that's a reactive punishment that does absolutely nothing to help out the woman who might be carrying a fetus post rape, not to mention the fact that rape is already illegal and a rapist isn't exactly going to be deterred by the fact that there's illegality involved. The issue of abortion also touches upon things like ectopic pregnancies where the woman can/will die if an abortion is not performed.
status_quo69··on Report: 90% of nurses considering leaving the profession in the next year
We already have decent (not always great but decent enough) government provided healthcare for the elderly through Medicare. So in fact, we've completely avoided your example already and said "yep, all life has value if you're eligible for medicare".

Of course resources are finite, nobody ever argues that they're infinite. But we treat healthcare as if there's a constant scarcity of medicine with how much is charged because there's a constant urge to squeeze even more profits out of patients who probably have only 2 choices- pay for the medicine or die.

status_quo69··on My self-hosting infrastructure, fully automated
Some people just like to tinker and try other things even if it's overkill. I have a k8s cluster on DO to host shitty side projects, it's pretty nice to just `kubectl apply -f manifest.yml` and be done with it, especially since I'll probably wind up tearing everything I just set up anyway.
status_quo69··on Tips for a Healthier Postgres Database
Like a lot of other complex systems, there's a lot of tweaking you can do in the config, but generally postgres works out of the box pretty well. There's a few gotchas on setup (postgres has a very conservative default configuration for things like memory usage and parallelism), but it's still pretty good.

I'd say the biggest footgun is really not knowing about the process per connection limitation, which is why the article mentions pg bouncer. Everything else in the article is pretty geared towards setting your db up for monitoring so you can head off issues.

status_quo69··on Lazydocker: The lazier way to manage everything Docker
You can also achieve this with watch
status_quo69··on Make your monorepo feel small with Git’s sparse index
I dunno, the linux kernel is pretty big and centralized by that definition, probably a monorepo by some definitions. I don't think this is a square peg round hole problem, I think that the operations that git must do coupled with the inevitable massive files that every company shoves into their repos (assets, binaries, you name it) makes git chug quite a bit.
status_quo69··on Builder Pattern in Rust
The nice thing about this pattern wrt mutability is that the mutability is scoped very tightly to the statement, since it's not often that you'd need a builder to live longer than a single statement or at the very most the lifetime of the builder. Although I've had to allow a builder to live longer than a single statement for things in the past, nothing is coming to mind at the moment. Because Rust enforces single ownership of mutable resources, it's not all that bad.
status_quo69··on Scaling monorepo maintenance
> If you need to handle different versions talking to each other in production it doesn't seem any harder to also deal with different versions in source

It's much more annoying to deal with multi-repo setups and it can be a real productivity killer. Additionally, if you have a shared dependency, now you have to juggle managing that shared dep. For example, repo A needs shared lib Foo@1.2.0 and repo B needs Foo@1.3.4, because developers on team A didn't update their dependencies often enough to keep up with version bumps from the Foo team. Now there's a really weird situation going on in your company where not all teams are on the same page. A naiive monorepo forces that shared dep change to be applied across the board at once.

Edit: In regards to your "old code talking to new version" problem, that's a culture problem IMO. At work we must always consider the fact that a deployment rollout takes time, so our changes in sensitive areas (controllers, jobs, etc) should be as backwards compatible as possible for that one deploy barring a rollback of some kind. We have linting rules and a very stupid bot that posts a message reminding us of that fact if we're trying to change something sensitive to version changes, but the main thing that keeps it all sane is we have it all collectively drilled in our heads from the first time that we deploy to production that we support N number of versions backwards. Since we're in a monorepo, the PR to rip out the backwards compat check is usually ripped out immediately after a deployment is verified as good. In a multi-repo setup, ripping that compat check out would require _another_ version bump and N number of PRs to make sure that everyone is on the same page. It really sucks.

status_quo69··on China is betting that the West is in irreversible decline
> but to consider their niche life-style as something more desirable than an average life style.

I don't see how this follows as a rebuttal of the gp comment, if anything it says (to me) that the US is _not_ in decline because we're willing and able to have conversations and make progress on what should be accepted in modern society. This comment feels like a soapbox to me rather than contributing to any sort of discussion, because nobody can comment on _what_ groups you're referring to, and there are no sources to be had. Very disappointing.

status_quo69··on YouTube blocked chess channel after mistaken detection of racial slurs
Another example of this is Transformers, which is/was beloved by kids and was easy advertising for Hasbro.
status_quo69··on Where Everything Went Wrong: Error Handling and Error Messages in Rust (2020)
I've used `thiserror` with great success in small side web projects since you can create a new enum of Errors that can be converted from a class of underling library errors. Then, inside of my regular application code, I sprinkle in `anyhow` to make my life easier.

For example, if I wanted to say, return a 500 status code for all diesel database errors, I can convert the diesel error into my custom error type, then throw it back up the stack using `anyhow`. This works _really_ well in conjunction with Rocket's Responder impl.

EDIT: This is pretty close to what TFA is saying as well, I should have read more in the article, heh

status_quo69··on YouTube to remove content that alleges widespread election fraud
I doubt that compiling a list will convince you, but NPR, the BBC, the Economist, the WSJ, the AP, National Review as a small snippet.
status_quo69··on YouTube to remove content that alleges widespread election fraud
> people really do want to base their opinions on facts

Not really, confirmation bias is a real thing for all human beings. The issue here is that there's a fundamental disagreement about what constitutes a fact. Objectivity in reporting is also subjective, funnily enough. If I consider NPR to be very objective because the dead-pan monotonic voice of the announcer simply says a direct quote from a member of congress, I can talk to a relative who will tell me that same NPR story is biased because they reported on something they don't agree with.

> It was because the media respected its role in society and at least tried to be objective.

There are _plenty_ of news outlets that still respect their role in society. The difference is that 20-30 years ago, there wasn't a deluge of information or misinformation readily available to get those dopamine hits from confirming biases.

status_quo69··on YouTube to remove content that alleges widespread election fraud
Why should credibility matter? That is to say, how can the average person know that what they're reading is credible or not to make that determination and say "oh, CNN reported this and it's credible! Must mean that CNN is becoming more credible and I should watch it more because they have a better product" rather than "CNN is reporting this but it doesn't line up with what I want to believe, they must be wrong and not credible". Your metaphor doesn't make sense in a world where news stories are looked at skin deep, where someone doesn't even know that the toilet paper is scratchy it just _looks_ scratchy from the label or uncle Joe told me that it must be scratchy because it's made by Proctor & Gamble.
status_quo69··on How the CPython compiler works
Do you mean a switch statement in pure-python that avoids certain opcodes, or a way to avoid executing opcodes in the main interpreter switch statement?
status_quo69··on No Recent Automation Revolution
I don't personally buy this. If prices were the most efficient way of determining what we should do for other people, why does the government already subsidize certain medications? Or agriculture? Or public development/education? College education becoming increasingly expensive proves this false, I believe.
status_quo69··on Microservices Considered Harmful (2019)
> you can use multiple languages

You can but you shouldn't unless there's a very good reason (ex: there's a very specific interface only available in a language that doesn't conform to the rest of your services) :)

status_quo69··on Today’s Javascript, from an outsider’s perspective
You can usually promisify the functions that take a callback via util.promisify (although I've done it manually myself as well).
status_quo69··on Show HN: PgTyped – Typesafe SQL in TypeScript and Postgres
Clarification: compile time query building, not querying. Due to inlining from the compiler, you can almost entirely construct the query at compile time and shave it down to a few string concatenations.
status_quo69··on Show HN: PgTyped – Typesafe SQL in TypeScript and Postgres
Just to clarify a bit for other readers since I've worked with diesel for while, diesel isn't a "full" orm, as there are no real helpers provided to you outside of "we can map the result of a db query into a struct(s) that you specify" and some really nice guarantees for compile time queries. Other than that, your struct is a pretty dumb mapped representation and it's on the implementers of the application code to provide sugar for better access patterns. For people coming from something like active record, this is (in my opinion) closer to Arel than ActiveRecord, or closer to sqlalchemy core than sqlalchemy orm. As an example, you won't necessarily be able to do `MyStruct.join(OtherStruct)` and have it magically figure out how to query the database and map the results out of the box.
status_quo69··on Announcing TypeScript 3.9
Sort of... Your maintenance burden just becomes higher as a consumer of the library because you can't rely on the compiler to tell you if something goes wrong. But if you have a good testing harness you'll probably figure that out eventually anyways.

To generate typings for your library, you can start with converting from jsdoc if you have docstrings with types, or if you want to infer types at runtime during a testing suite you can use something like https://github.com/microsoft/dts-gen

I've never used dts Gen but it looks promising as a starting point. But as an additional point, only the public functions and classes really need type declarations, so unless you export all of your functions that could cut down on the burden to write up the types.

status_quo69··on Why should I have written ZeroMQ in C, not C++ (2012)
Unless I'm misunderstanding your comment, you can make panics abort rather than unwind.

https://doc.rust-lang.org/edition-guide/rust-2018/error-hand...

status_quo69··on How I Start: Rust
Sorry, I misunderstood! As far as I'm aware there's no curated list of best practices just yet, although that would be awesome! Most of this comes from past experience with things like Flask/marshmallow and a lot of trial and error. Maybe one day when I've shaken out all of the issues at hand and I've figured out a good way of handling various scenarios I'll write something up about it
status_quo69··on How I Start: Rust
Something in the vein of juniper but for JSON:API? That would be incredibly useful! I'm not at that stage yet, mainly hacking on https://github.com/zacharygolba/json-api-rs to bring it up to rust 2018 and add some more niceties as well as bringing the rocket integration up to the async branch.

What I'm working with right now is more of a pattern. It's a bit rough still and allows for too much recursion and N + 1 queries galore, but since my usual queries from my front-end are for single items it's been pretty nice.

Maybe one day I'll be more up to snuff on macros to expand upon that DSL. I'm already starting to see some rough patches in my very tiny pattern with relationships

← PreviousPage 2 of 3Next →