That's not correct from what I'm reading.
1 karma · joined June 5, 2024
That's not correct from what I'm reading.
My other concern is that you haven't bothered to research statistics on police brutality and harassment, yet you seem to express doubt that the numbers are significant. In your hypothetical "most people can go through their lives and never experience police behaving badly", yet almost no Black American will tell you this.
In addition to good naming, strong static types and functional purity help a great deal (but I won't try to evangelize haskell here :))
> ...hidden (because if someone is reading code that calls myVeryWellDocumentedFunction, they won't see the documentation, especially if the function is just incompletely named)
what is your proposed alternative? Ideally a function would do the only possible sensible thing imaginable, but that is frequently not attainable.
> ...inaccurate (because the only accurate thing is the code)
Well when the code doesn't match the spec in the comments, we've found a bug in the code, or a bug in the spec. Either way we can find someone to blame. This is vastly better than finding a bug and not knowing whether the function or the caller should be fixed.
You haven't made any arguments in support of this claim.
> Further, the data is misleading as well. Suicides, homicides, and accidental deaths are three different things.
Yes, what is your point?
> This means that the data tells us nothing about whether tougher laws would help or hurt the state of gun-related death
Rates of gun ownership is tightly-correlated with rates of gun-related deaths, at whatever scale you cut it. This also holds true for gun suicides:
http://www.hsph.harvard.edu/news/magazine/spr08gunprevalence...
> yet there is zero reason to conflate that with homicides involving a firearm.
The article doesn't conflate anything; it makes a very interesting and important comparison: vehicle deaths (which have been extensively studied for decades, with much federal regulation and other pressure to improve safety) are now on par with gun deaths (which had been banned from federal research for nearly two decades).
> It's amazing that we've improved vehicle safety in the last 60 years
Wouldn't it be nice if fewer people were dying from guns as well?
Maybe, or maybe not. Anyway religions have no inherent meaning external from the way in which they're practiced and understood by their practitioners.
What I'd like you to expand on is: what do the distinctions you're making in your argument entail (w/r/t public policy or just personal behavior)?
So what does that entail? Isn't this philosophy of science?
I think you imagine that you are being very rational, because you've studied some climate science and believe you're intelligent enough to form your own judgement, but you're wrong. It's extremely irrational to dismiss the consensus opinion of climate science researchers based on your own (epistomologically limited, non-professional-climate-scientist) assessment of their research.
> it still looks like your typical doomsday story dressed up as science.
And say the likelihood of this doomsday scenario being correct is 10% by your assessment: do you think a rational risk analysis would conclude that we should do nothing and go about business as usual? Do you also enjoy playing russian roulette when your not skimming climate science articles?
You can check out this module:
http://hackage.haskell.org/package/base-4.8.1.0/docs/Control...
You can see all the varied sorts of things which are "instances of Monad", then scroll beyond and see all these different useful operations which behave sensibly for all those different instances (and from which you can build your own more complex operations which work for any Monad, and which also behave sensibly).
Eek, then by all means take comments seriously and change them when your code changes. I think it's particularly important to comment functions and methods (especially effectful/stateful ones) with what precisely they're expected to do, what invariants hold, etc. (insofar as the type system and function name don't make these clear). Otherwise another programmer has no way (aside from looking at and completely understanding every call site) of knowing what bits of the functionality are incidental vs intended behavior, and are likely to make small modifications for their own purposes which break other things.
Programmers seem very eager to lack of comments and I'm super unsympathetic; this is the one thing that just kills me. Comments hold together a codebase, make it much easier to learn and read, and are a way for programmers to impart all sorts of bits of knowledge about the domain that is valuable "we would do X here but foo() from library Y works in such and such a way so, blah blah blah". And if you don't like to read comments like that I'm sure your editor will fold them for you.
Can you expand on what you mean by that? (Specifically by "hunted down" and how what you're talking about relates to inequality)
Because that argument betrays the most infantile misunderstanding of an issue that is extremely important; climate is not the same as weather, and extreme heat and cold and weather events are what climate models predict.
> Many conservatives are right to underline that simply increasing taxes is not the solution. So what's the solution? Innovation in new source of renewable or less polluting energy technologies.
Are you describing cap-and-trade? That's actually a conservative solution from decades ago; this is the "middle ground" and was roundly rejected as some kind of socialist takeover by today's conservatives.
Anyway it's probably too late for all of that anyway. It's certainly too late for your impotent handwaving about "innovation in new source of renewable". What a joke.
I'm not sure that's accurate. I think in the US it was mostly skilled industrial workers who were unionized.