skysight-inc/HackerNews huggingface dataset:
I think it's more complicated than that.

Studies I have seen and first-hand experience suggests that people in positions of power are typically fairly competent and got to where they are because of their competence, so they often genuinely feel that people disagreeing with their position are just stupid or simply don't understand the problem adequately. Their first-hand experience backs up this assumption in most cases and fosters habits that end up de facto being "asshole behavior" in many situations.

As they accrue power, they get surrounded by yes men who massage their ego, either to curry favor or out of genuine fear or because they are sincere fans who recognize their leader's competence and aren't competent enough themselves to poke holes in anything their leader says.

It's inherently hard to figure out how to avoid that outcome. Powerful people often keep long-standing associations with people who knew them back in the day because those people may be the only ones who have any hope of giving them pushback that is actually constructive and not politically motivated (in an "office politics" sense of the word).

The world hasn't solved this problem yet.
What source do you have that confirms this? Everything I've read says it is not yet determined if this is the case.
"Considered Harmful articles are problematic, and that's a good thing"
You should still write semantic HTML, but that doesn't mean every character in an HTML page has to be directly tied to some meaning that isn't to do with styling.

Google and screen readers aren't going to be confused by you putting a < div class="spacer > < / div > tag in the middle of some < h1 > and < p > tags on a page.

I think coders just need to accept that it's a failed experiment to keep all styling data out of HTML. We've been trying for decades now and it's not practical, especially when you're adding a high level of polish to the presentation of your page while dealing with current web standards.
Do you honestly think you need PPE to phone someone from your home? Use your common sense.
Mayday Masks – Donate your N95 masks
But the example's disclosure in the link was not hidden in fine print at all. It is in boldface and uses the largest font on the paper: THIS IS NOT A BILL. THIS IS A SOLICITATION. There are scams out there but this one seems more like a dark pattern. You don't have to be that astute to identify it--you just have to be able to read and not go on autopilot.

Victims don't deserve to get scammed, but that doesn't mean they shouldn't exercise caution.
What about Bihar then
It is a pandemic. There is no reserve of uninfected, refreshed people.

I suspect a part of the reason for the call is to communicate that we are not in normal times and the idea of paying someone to make your problems go away doesn't work. Help or get out of the way, your payment will be a slightly less broken country when this is past.
Startups Jump the Gun on Home Kits for Coronavirus Testing
I don't see an effect due to increased testing- not a large one anyway. Doubling time is still a bit over 2 days, and has been for 10 days or so.
The name is great, as is the slack command /screen, just keep using it. Saying this as a user of GNU Screen. It's OK, approximately nobody is going to be confused by this in the real world.
Ask HN: A tool for Covid patients to “flag” people/places they may have exposed?
This is just a thought, but I'm surprised I haven't seen any effort along these lines.

It would be useful if people who have tested positive for the virus could flag people and locations they came into contact with in the days before they became symptomatic.

This might be useful on a variety of levels:

1) informing the potentially exposed individuals without requiring the patient to individually contact each person

2) let others avoid those who have a higher probability of exposure (or at least give them a data point to help them make a risk-benefit estimate)

3) identify "hot spots" (businesses, restaurants, etc)

4) making the spread or potential spread of the virus more tangible for people who don't personally know anyone who has contracted the virus

Plus it would just be a fascinating dataset for visualizing the spread through communities.

Of course, I see the potential for this to exacerbate panic and enable social shaming/exclusion. I expect the perception that you're "throwing people under the bus publicly would decrease utilization of this tool even if it existed. Any ideas for how to avoid that perception?

Seems like this could be implemented pretty easily on top of Facebook APIs for Friends and Business Pages.
O’Reilly’s in-person events business shutting down
That has not been proven or disproven at this point.
Coronavirus may already have infected half of UK population – Oxford study
Imagine you have a mask, you take it off for some reason (say to eat or drink) and put it in your pocket, it gathers tons of bacteria, you then put it back on your face. The warm and moist environment lets that bacteria spread, and you sit there breathing in through that colony of bacteria for the next two hours.
This made me crack up. I do this all the time and thought it was because I was "bad" at CSS, having not kept up with the times. Is there really no better way in 2020?
One thing I hated with GNU screen was how hard it was to google. I knew there was a certain fix for a special edge-case but the generic name made it hard to search for.

This project don't even have the GNU keyword to help.

I guess this is an aspect where search engines are much better today, to get the context. But still, the issue remains.
Same - brilliant and enjoyable on multiple levels.
I semi-agree with the point being made, but I don't like the solution. Spacer components isn't the solution, IMO, separating the reusable styles from one time styles is.

so instead of:

<div class="link"/>

<div class="spacer"/>

<div class="link"/>

<div class="spacer"/>

<div class="link"/>

We should be doing:

<div class="link space-right"/>

<div class="link space-right"/>

<div class="link"/>

This allows the reusable styles to be reused and the spacing to be one off.

P.S. since I'm more of a react/styled-components kind of guy, this is how I would look to do it there

const Link = styled.div`

//... styles

`
const LinkWithSpacer = styled(Link)`

//... margin

`

<LinkWithSpacer />

<LinkWithSpacer />

<Link />
Contract hours, minimum pay, tax implications for pensioners, availability. Sometimes things are more complicated than just writing a script. This is quicker and can be disbanded just as fast.
I agree. The cost will be minimal compared to the truly gargantuan package of measures announced so far, and would be a great way to help the self-employed now looking for work (who currently get nothing).
There haven't been any bailouts issued yet. Congress is still in the process of working out what the stimulus bill is going to look like.

You're referring to overnight loans made by the federal reserve to facilitate liquidity in the market. If you're not aware of the significance of the difference, this isn't the appropriate place to go over it.

Regardless, the stimulus package is going to have some form of social support in it. My point is just that it's not going to be a free win, it's more of a least bad option at this point. There's going to be long term economic and social damage from this even with the most generous of social support offerings.
JDK 14 Security Enhancements
My Proposal: Set a 3% limit on credit card interest for the next six months. If a credit card company complains, nationalize it. Use the six months to set up a debt-forgiveness plan that works for middle and low income earners. At the end of six months, consider lifting the limit incrementally.

Get spending power into the hands of common people and ease the cash-crunch anxiety immediately, without any stupid one time payments that will be too late, won't be large enough to help, and require the entire legislative branch to agree.
Quite the opposite. It takes one call from US embassy for the government to change course on anything. And giving workers no representation is part of the system: it is illegal for them to strike because of it so they do "cough on your manager" protest instead.
I name-called the "health professionals"? Help me out: what do they like to be called?
Who’s the idiot who made google docs and didn’t focus-test it for software docs? You need a third party add on just for code blocks ffs. I really wanted to use Google Docs for this but it just didn’t work. Confluence makes you switch between edit mode and view mode just like Markdown, and Notion is cool but has limited features for this application (no api)

Sadly there’s no really mind blowing solution for documentation in 2020. Crazy. Markdown for me for now
Can't we just use JSX or XML? Those both beat this house of cards formed out of one-off and nonstandard extensions, parsers, and pipelines built around Markdown, which in itself is deficient and prompts the creation of these fragmented ecosystems.
-If you haven't reread them as an adult, do yourself a favour and get started. I, too, loved them as a kid - but have found that Asterix resonates on many levels. It is definitely a comic for grown-ups too, gently mocking the grown-up world in oh so many ways.

I'll pour myself a generous helping of calvados and reread a few of the albums tonight. RIP, Albert.
We don't know that yet, but so far that seems unlikely.

https://www.npr.org/sections/goatsandsoda/2020/03/20/8190384...

https://www.genengnews.com/news/covid-19-reinfection-not-a-c...
Whether or not Markdown works for documenting your project depends on your definition of "documentation" and "works." Blog posts telling you to stop or start doing something are myopic and rarely helpful.
Two jacks also would have made it bigger.

If anything, it would have made more sense to have a branch jack in the iPod headphones.
From all the news I’ve seen (I watch Japanese news broadcasts most days), people there aren’t comparing the Japanese response to the US, but Taiwan, South Korea, and China. And the comparative failings are obvious and stark.
I believe you can get reinfected with a different strain of the same virus. Not the one you initially got infected with though.
> They will once their taxes start going up.

We can use a relatively small amount public funds to make targeted investments in electric grid infrastructure and scaling PV solar and storage. That will drive costs down and coal will disappear without any need for new taxes.

Heck, even if we don't make any public investments to accelerate the process, it will happen soon (< 10y). Coal is on its way out as a fuel for electric powerplants.

> Air travel should be restricted, or at the very least taxed in proportion to its emissions, because it's cheap, easy to implement, and doesn't impact the survival of millions of people, whereas increasing the price of electricity in developing countries does.

Soon enough, either microgrid PV solar and storage or utility-scale PV solar and storage will be cheaper than coal, even in developing countries. Microgrid PV solar and storage is especially attractive in developing countries where the electric grid is typically unreliable.

I do agree that the emissions costs of air travel should be internalized to the ticket price, but the regulation needs to leave enough room to allow airlines to avoid emission taxes by using carbon-neutral fuel.
Consider reflecting on what you or someone else might mean by "documentation". A submission from 3 hours ago titled "Please don't write your documentation in Markdown" was on the front page earlier: https://news.ycombinator.com/item?id=22675165 — but according to its author (https://twitter.com/hillelogram/status/1242502542212333576),

> most people are talking a different kind of "documentation". Most people are thinking of "basic instructions + API", I'm thinking "multithousand-word manuals and reference materials". The latter needs a lot of stuff the former doesn't

With this context, I think it absolutely makes sense that if you're writing something structured (like a book), Markdown may not be the best choice to capture that structure. Of course, if you aren't already sure you're going to have enough documentation "content", then the best choice is whatever gets you writing at all in the first place, whether it's Markdown or Google Docs or emails to colleagues or whatever.
PyLiveUpdate: Modifying running Python code on the fly
You make it sound ironical and cynical, but that is actually how things are done in real world. I mean, I admit I have done that sort of thing after I read first article about css after someone required me to move something first time ...
Angelo Gordon Halts Investor Redemptions
When You Die of the Coronavirus, You Die Alone
Does Google Rank Your Site Better If They Use It for Their “Knowledge Boxes”
I've used rst. It was an unmitigated disaster for anyone except the rst-fan who initiated the project. We eventually hauled the contents over to Confluence, because it was less painful that way. If you can imagine. Later on, we started using markdown.

All the fancy features and attempts to smooth over complexity are a hindrance to having text that is easily writable. The complexity is there for a real text processing engine, you can't avoid it.

I either write LaTeX or org/Markdown, if given the choice. Note that org and markdown are trivially usable if the renderer explodes under you.
My wife, Christine, started this to help find masks for healthcare workers. Her Mom is treating COVID-19 patients and has a single mask to reuse for a month, which she carries around in a plastic bag.
At least he's not vehemently advocating Word.
Yes, but certain calculations are inherently numerically unstable, meaning that rounding errors can quickly dominate the calculation.
Location: Riverside Co., CA

Remote: Yes

Relocate: No

Technologies: Python, SQL, Flask, FileMaker, HTML5, CSS, JavaScript

Résumé: https://github.com/chivalry/resume

Email: chivalry@mac.com
TripActions Lays Off More Than 300
The longer I spend engineering, the more I just want to get the job done and get it over with. I've built, and will continue to build, strongly-opinionated frameworks and platforms based on my experience. But this week's silver bullet is next week's anti-pattern: mostly because of a misunderstanding of when, how, and where to apply design patterns.

Truthfully, it's increasingly my opinion that design patterns (and by extension, anti-patterns) only exist in the context of focused, internally consistent systems architected by a small group of individuals and not a committee. Rails, especially early on, is a great example. Actually -- a huge chunk of programming languages are built this way. The web, however, is designed by committee.

With this framing, "avoiding margins" works for the way Max builds design systems -- and from what I know, he's very talented and the team(s) that work with him should adhere to the systems he constructs. I'd love to see an implementation of an entire framework / design system that avoids margins -- something like Tailwind CSS. I do not, however, really believe this is broadly applicable advice. Most people are just trying to ship something that looks nice, and margins can be overwritten and adjusted easily.

NOTE: I have components I've written that have margins I have to overwrite nearly universally, but can't remove because of other UIs relying on the margin behavior. So I understand where the argument comes from. It's just -- I'd have a hard time if anybody tried to pick a bone with a software engineer on the team about the use of a margin if the initial intention was good / legitimate.
A couple of my family members received letters 2 days ago, saying they are to stay at home for 12 weeks. That's in Scotland though, so things might differ elsewhere in the UK.
Then you haven't considered how obnoxious a title like "Make Margins Great Again" is.
> everyone has a 27" Thunderbolt display

Insert Game of Thrones too dark meme here...
If you want to contact her: https://twitter.com/christine_hall
Coronavirus Stimulus by House Creates New Digital Dollar
As we run short on tests it's likely that only the bad off will get tested.
I feel the problem is that this really doesn't provide actual value to its user.

It's one thing if they are getting contents behind the paywall, but it really only appeal to relatively small subset of users who has cause to support these sites. For the rest, they will keep using content blockers...

I understand providing access to paid contents would probably costs more than $4.99 collectively, but I feel this will be a hard sell without tangible benefits.
I used markdown for my documentation of a embedded liux system years back (https://brainyv2.hak8or.com/) and have been very pleased. While it's not a book, it's also not a single page document.

The rust official docs are also written in markdown and thrown at mdbook (https://rust-lang.github.io/mdBook/) to generate documentation of a similar style, but it's much more book like.

I am pretty much all in for markdown based documentation for almost everything. It does what I need and nothing more.

If I need more control over styling, that's a different story, but thankfully almost all my use cases are good enough without such control.
I agree with everything here except the reference to QE. Quantitative Easing works to control the money supply only because the central bank can quickly mop the money back up by selling the bonds it previously bought. The central bank can't mop up money it sent to people as wages, so if inflation started, they would have no leverage.
Japan actively avoids testing if those deaths are due to COVID-19. If someone recently dies with pneumonia, it's worth to test if this is the COVID-19 case. Japan doesn't and it claims that the public fear will overload and collapse their medical infrastructure. I don't really understand why this can even be the case, but this is a broadly accepted sentiment around Japan. And its annual death toll from typical pneumonia is around 100k, so Japan can easily hide it even if they had hundreds of the COVID-19 death cases by not testing it.

https://www.japantimes.co.jp/news/2020/03/24/national/tokyo-...

Meanwhile, Tokyo's governor is actively considering lock-down due to a potential explosive rise. Lock-down for a city like Tokyo (which has roughly one third of their entire GDP) is clearly a nuclear option. If you really have only hundreds of the cases, this can (and should) be handled by comprehensive testing and tracing like S. Korea. Or perhaps their confidential COVID-19 projection doesn't agree with Japan's official stats...
Giving up on some principles can also be a starting point for erosion of more principles. It’s a very slippery slope that needs to constantly be reconsidered. See the slow building up of surveillance states where the principle of privacy is slowly being eroded because of profit and safety.
One of the problems the UK has is that "The Big Society" was used as a political punchline for the best part of the last decade.
Pass. Markdown is pragmatic, works well and is most importantly, easy to learn and maintain.

Asciidoc is well-intentioned but is way too complex. Variables, extensible formatting language, and conditionals really don't fit for 99% plus use cases where you'd use Markdown... and if they do, they are as a part of a web templating engine that is being fed markdown.
It's the later. Heck, if you crash into someone's car, police might not arrive at the place and the guy whoes new car got fucked, might destroy your face.
Conda is a fine alternative, and perhaps superior to pipenv.
Hey there! I'm Richard, a freelancer who enjoys making web apps. I'm currently open to contract work only.

Location: San Francisco, CA

Remote: Yes

Willing to relocate: No

Technologies: React, Next.js, Node.js, JavaScript, Rails, Python, Django

Resume/CV: https://www.churichard.com/

Email: On my website!
Not joking; An acronym + virus is much better than china + virus, or Covid-19 (which is actually the name of the disease).
Hey evengelosdotnl, great comment. A lot to unpack here. To address both points:

>>>Why would you need to have a delay of delivery at the first place?

1) Emails - Let's say you want to send a reminder email a month in advance. You usually put emails on a queue to go out, but since this is scheduled so far in advance, you need a way to store the request and publish it back to the queue to send a month later. Then you could use schedulerAPI + your emailService to achieve this reminder email effect.

You could extend this to any service that needs a delay. Eg if you need to schedule billing, you can call schedulerAPI + stripe API, delay texts you use scheduler API + twilio API, where each queue message is a request to bill or message someone).

2) Handling retries - Sometimes if a message fails you want to retry with exponential backoffs. This requires re-enqueuing the message with longer delays. You could just call schedulerAPI w/ longer delays to achieve this.

>>> CQRS Implementation for handling queues

Thanks for sharing this, I have never heard about this before. CQRS seems consistent with both scheduler API and microservices architecture in general. From my quick read of this, it's basically saying to spread out a monolith service that handles all CRUD operations in one service into separate services if the model for each operation is different. So instead of one service that handles all writes and reads to a table, you have two: one that handles reads, one that handles writes because the models for both are different.

Queue message scheduling fits well with CQRS. The queues and scheduling are different problems. The queues handle high throughput messaging, whereas scheduling is more of a storage problem (if you delay a request you need to store it somehow and pop-it out when you need it). So it makes sense based on CQRS architecture to separate the two out because they are fundamentally different models. That could explain why scheduling queue messages has never been a first class citizen in any MQ so far.
Who Is Reality Winner?
Chloroquine Is a Zinc Ionophore
Markdown is far from perfect, yet it remains my format of choice for most writing that requires some formatting. I even write my longer emails in Markdown and then paste them into an email app (would be great if gmail accepted markdown).

If you require as much power for your documentation as demonstrated and don't mind the relative obscurity in the source, why not just write it in your favorite language and have it output to whatever format you want? Most languages have a means of entering muti-line strings. And then you can include all the bells and whistles your language and its ecosystem provides.
RIP Monsieur Uderzo
It’s a good point, but quite a bit of the US population lives in urban areas, no? Which is going to overlap with where quite a bit of healthcare system strain might occur, making volunteers necessary.

Will citizens heed the call? To be determined.