271 karma · joined November 29, 2016
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.
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"
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.
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.
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.
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.
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.
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
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.
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) :)
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.
https://doc.rust-lang.org/edition-guide/rust-2018/error-hand...
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