Thank you for limiting my "Nooooo..." to only 5 'o's.
1,437 karma · joined October 10, 2019
[ my public key: https://keybase.io/hwbehrens; my proof: https://keybase.io/hwbehrens/sigs/dLHJ81Px5e89QVjFDYNRo6_ogUJozHWtgGR9MK3AYQQ ]
Thank you for limiting my "Nooooo..." to only 5 'o's.
Basically, it allocates a bunch of money for supply chain and production improvements.
http://talkingplants.blogspot.com/2019/09/botanic-or-botanic...
It seems to be a historical and cultural artifact?
In practice, though you shouldn't store the SQLite in a cloud sync service, setting up a symbolic link for the backing PDFs in e.g. Dropbox works quite well and gives you more control over your data syncing. Then, you only need to rely on their cloud for the paper titles and metadata.
I won't start using an app that doesn't let me do anything useful without paying, and I'm not going to sign up for a service if I don't know what I'm paying for, so I always look for that information up front before I even install.
While you're likely to get skewered for this line, I think it's because of a mismatch in vocabulary that is being ignored. The "work" in antiwork is usually referring to paid employment, but it seems that you're using it more akin to fulfilling accomplishment. I agree with you on the whole that people need to feel that they are making a positive impact on their surroundings to feel satisfaction.
Maybe that comes from paid employment, or volunteer work, or hobbies, or social interactions. A street preacher, a stay at home parent, an ancient cave painter, a bricklayer, and a software architect might all feel equally satisfied by their work, irrespective of the value placed on that work by their society.
In fact, I would argue that the (professed) goals of antiwork are aligned with your view -- people should be free to pursue the work they personally find the most fulfilling, rather than the most profitable.
What structural component is this meant to replace? It's called a "slab" but I can't see it being used to replace a concrete slab; even if it were stainless, I recall from that 1000-year house discussion that ground contact corrodes metal quite quickly.
Of course, companies know this and use it as one of the many tools to suppress wages.
Elaborating on your perspective on the situation, sharing how it's affected your behavior or though processes, or engaging others in discussion would have produced a more substantive contribution.
I am very sensitive to HN sliding into a 'Reddit, but for nerds' situation where facile comments dominate the conversation and the signal-to-noise ratio is unbearably low.
Looking at your other comments, in general you do a pretty good job of holding back the tide -- please don't take this as a general comment against you, but more as a signpost for others.
On one hand, we already raise pigs to kill and eat routinely, and (mostly) people don't care - is this any different than say, buying a pig heart at the market to eat?
On the other hand, it does somehow feel different to me, perhaps because sharing organs somehow humanizes the pigs by emphasizing our similarity? I'm not entirely sure from where my hesitation stems.
I'm curious if anyone else read this story with mixed reactions.
They're impossible to shut down without (potentially) affecting innocent bystanders. If they don't care, they absolutely can and do shut down towers.
In this case, if they judge anyone broadcasting or using this network as subversive, then there are no bystanders, only accomplices. And, thanks to the tyranny of the inverse square law, it becomes much easier to sniff out broadcasters/uplinks as well.
The easiest way to mitigate this is to do both -- rebroadcast a cell connection over WiFi, and do so intermittently and in varying locations to complicate triangulation.
However, among my colleagues (all very talented in their own unrelated areas) it generated a fair amount of consternation, because although they had a week to read it, none of them felt like they had a good grasp of it until after I had presented it. The key takeaways that had jumped out at me immediately were lost in the noise.
Whether or not a week is the right time, I can definitely empathize with taking more than a day to evaluate a paper, particularly in an area not very near to your own as there might be a lot of missing background to fill in. In contrast, my PhD advisor could flip through a paper in 30 seconds and pick up the key points it took me an hour to extract. In that sense, I really think that reading papers is a skill that can be trained.
[0]: https://drops.dagstuhl.de/opus/volltexte/2020/13109/pdf/LIPI...
If the question was "Which of these trips would you like to pay for twice?", then it's immediately obvious that the cheaper trip should be cancelled.
These things, which are usually things like diabetes, blood sugar problems, high blood pressure, elevated cortisol and so on, do correlate with poorer COVID outcomes.
My understanding is that, even when you control for these factors, outcomes for obese patients are still below what we would expect to see. This means that there is still a contributing factor that we haven't considered yet, and the parent study hypothesizes one possible reason.
There are 3 to 4 million devs in the US alone -- with a sample of that size, you'll get the full spectrum of people. Heck, you'd probably find some that like that the dislikes were removed. From their perspective, by blocking your extension they're actually making the world a better place.
It's shades of grey all the way down.
I think this is an understatement, considering that it's a core cryptographic library. It appears to have gone through at least five audits (though none since 2010), and includes integration with hardware cryptographic accelerators.
Suggesting a tabula rasa rewrite of NSS would more likely be met with genuine concern for your mental well-being, than by incredulity or skepticism.
I've been told the opposite -- in the recruiter view on LinkedIn, they can only see your 3 most-recent positions, and they almost never expand the fold to see the rest. Thus, it's critical to curate those.
For example, let's say you previously worked at BigCorp, but left to pursue your startup idea (Startup A). In the meantime, you've consulted at another startup (Startup B), and you're working at SmallCorp to make the ends meet until your idea takes off.
You'd be better off listing StartupA, SmallCorp, and BigCorp (or StartupA, StartupB, and BigCorp) as compared with StartupA, StartupB, and SmallCorp, since only the most recent three jobs will be shown, and recruiters tend to more heavily weight BigCorp signals.
Imagine a user chooses "Sort by rating", and they subsequently observe an item with an average 4.5 ranking above a score of 5.0 because it has a higher Wilson score. Some portion of users will think "Ah, yes, this makes sense because the 4.5 rating is based on many more reviews, therefore its Wilson score is higher." and the vast, vast majority of users will think "What the heck? This site is rigging the system! How come this one is ranked higher than that one?" and erode confidence in the rankings.
In fact, these kinds of black-box rankings* frequently land sites like Yelp into trouble, because it is natural to assume that the company has a finger on the scale so to speak when it is in their financial interests to do so. In particular, entries with a higher Wilson score are likely to be more expensive because their ostensibly-superior quality commands (or depends upon) their higher cost, exacerbating this effect due to perceived-higher margins.
So the next logical step is to present the Wilson score directly, but this merely shifts the confusion elsewhere -- the user may find an item they're interested in buying, find it has one 5-star review, and yet its Wilson score is << 5, producing at least the same perception and possibly a worse one.
Instead, providing the statistically-sound score but de-emphasizing or hiding it, such as by making it accessible in the DOM but not visible, allows for the creation of alternative sorting mechanisms via e.g. browser extensions for the statistically-minded, without sacrificing the intuition of the top-line score.
* I assume that most companies would choose not to explain the statistical foundations of their ranking algorithm.
Or "Uber"?
In particular, although these dispersion methods (as you pointed out) don't typically reduce the impact energy to zero, they offer a roughly 2 order-of-magnitude decrease in impact energy while requiring only month-scale warning.
In contrast, diversion techniques which can reduce the impact energy to 0 (e.g. by shifting the impactor to 'miss' our planet) can require decade-scale to accomplish their goal.
[0]: https://www.sciencedirect.com/science/article/pii/S009457652...
> The person doing orders of magnitude more work is probably only getting paid 10% more.
You've answered your own question. Transparency is undesirable from an employer's perspective because it encourages a closer alignment between compensation and productivity, and the mismatch between these currently serves as a significant profit advantage to the employer.
If I can get 1000% more work from someone, and pay them 10% or 100% more, I am highly incentivized to prevent them from becoming aware of the value of their efforts, because they might realize their (relative) exploitation.
At the same time, the less-productive worker also benefits from this lack of transparency because they get ~90% of the pay for 10% of the work. Disrupting the status quo would not be economically rational for them either.
Thus, only the small fraction of underpaid, overworked people benefit from increased transparency, and it is not surprising to find that the majority would resist its implementation.
I think they absolutely are taking that path with their recent push towards the eYuan. If they want to replace Alipay with their nationalized, centralized system, I imagine the steps would look roughly like:
1. Create eYuan (Done)
2. Disrupt other solutions (We are here)
3. Disallow other solutions
4. Done
I think it's possible to make persuasive argument that this already took place around the time that they killed OpenGL support and/or refused to allow Vulkan support. Requiring a proprietary API that only works on a tiny subset of gaming devices* seems like they've already made their position on this topic very clear.
* I'm excluding mobile devices here since mobile games were called out as a different market in the parent comment.