skysight-inc/HackerNews huggingface dataset:
Diagram.Codes Studio – use a simple set of text conventions to generate diagrams
Indeed, and in fact there are systems that adapt between the two paradigms. For example, taking a system based on IBM 3270 screens and turning it into a series of web pages to enable a web portal for an existing mainframe system.
I myself directed teams of developer up to 35. Do not know beyond that scale. Teams simply worked on modules and main designers made sure they complied to a shared interfaces / state machines in more complex cases. Not a big deal. The law was: I trust developer so here is your module interface and constrains. Now go away and come back with implementation (which would still compile to a single monolith). As I was lucky to work with very good programmers bar couple of bad apples I've never had any real problems with the delivery and its quality
"Human problems" is even more vague than "software issues". Any details as to what in the process is actually the bottleneck or failing?
> Consider, for example, that 1/3 of the country is on a rent strike right now

Errr - no, no they aren’t. This month had approximately 12% more people miss their rent payment than last April.

That’s high - and bad news for people like my retired aunt and uncle, or father in law, who rely on the income from their rental property - but it’s hardly a national rent strike.
Something very nice is that the issue tracker is nothing but an SQLite database. You can customize it any way you like, running arbitrary SQL queries on it, and generating any html you want. I use it for notes, among other things. In addition, you can extend it in any language using a CGI program.
It's already been done.

https://today.rtl.lu/news/science-and-environment/a/1498185....

'These research findings have already provided some indication on how the virus works, as Streeck clarified:

“There is no significant risk of catching the disease when you go shopping. Severe outbreaks of the infection were always a result of people being closer together over a longer period of time, for example the après- ski parties in Ischgl, Austria.” He could also not find any evidence of ‘living’ viruses on surfaces. “When we took samples from door handles, phones or toilets it has not been possible to cultivate the virus in the laboratory on the basis of these swabs….”

“To actually 'get' the virus it would be necessary that someone coughs into their hand, immediately touches a door knob and then straight after that another person grasps the handle and goes on to touches their face.” Streeck therefore believes that there is little chance of transmission through contact with so-called contaminated surfaces.'
That is a great video! It also reminds me of Dan Wang's essay on How Technology Grows: https://danwang.co/how-technology-grows/. It introduced me to the Ise Grand Shrine, which is a wooden temple that's rebuilt and torn down periodically so that the knowledge of how to maintain it doesn't get lost.
> It seems the audio is not sent over WS until the capture is complete.

The info block indicates this is by design - 20s seems like a lot of latency, but possibly if it's got to pull down the entire audio blob before it can start playing?
Now people who simply care about privacy are “extremist”

Perfect way to begin marginalizing people who care for privacy
Agreed, although I've been using Ripcord for almost two years now, I typically use it for casual Discord use.
I'm not familiar with South Korean church practices, but there is an instance of a choir practice in the US that spread COVID-19 fairly effectively. This suggests that singing, a common practice in US churches (in my experience), spreads the disease. An article on the event reports that the choir members attempted to distance themselves from each other and use hand sanitizer.

https://nypost.com/2020/03/30/washington-choir-rehearsal-tur...
Molecule+Mattress+Savings+15%+Off+Plus+$300
Use it more. Get to know its lurks and perqs. Then you'll find out its capabilities as well as its shortcomings. What is familiar is what is comfortable.
If you're converting it to SSA form, is there really a difference between

int a = 5
int b = 2 * a
// don't use a again

and

> int a = 5
> a = 2 * a

?
there's no button the government can press - the broadcast data is short term identifiers that can't be linked without know the day key. The identifiers are literally just a random 16 byte number derived sequentially from the day key.

The day key is only known if the user elects to publish those keys.

If you have a collection of day keys you don't know who published them as there's no device information in that.
The spec seems nice, but we need a unique app with a unique set of "diagnosis servers".
When you take an international flight with one or multiple connections you are in contact with people from many different countries,
should you install all the available contact tracing app available on the app store ?

If you have one app per country, you could have the "diagnosis servers" of all the countries federate and exchange data,
but in the end it's easier and more effective to have 1 official open-source app from say the WHO.
If you read about the religious sect, it has huge services where people have to sit on the floor because they are 'packed in like sardines'. Not quite the same as your typical church.

So, maybe this could be an argument against the massive mega churches. But, not a blanket ban on all religious gatherings, period.
It didn't when I tried it - IntelliJ does support it on some level, but doesn't offer the same depth of automatic refactoring etc. that you get with Scala, to the point that my colleagues generally favoured using VS Code.
Just the Senate? What about the House?
Nothing about this change applies a change in quality. It's the opinion of a few vocal people that this is bad, nothing more.
I'd imagine that if you got into a car accident in a nuclear-powered car, it would blow up like a mini-nuke just like in Fallout
Exactly and figuring out all the logic with code that's been refined and built out of 20-30 years.

Any developer saying, "Hey, go and rewrite the code" underestimate all the edge cases that end up all over the place in the application.
The reason it's my pet peeve is because I use "begging the question" in its correct form all the time to describe an otherwise difficult concept. Once you put a name on something, it's much easier to understand and talk about. But when the name is confused with a much simpler concept "raising the question", it kills the original meaning so I have to explain the concept in far more words. For example, "The man is assuming a fact for granted and using a fact that follows in order to prove the original fact." is much more wordy than saying "The man is begging the question."
Keep us updated on how that goes. Serious
It's amazing that this actually used (or was supposed to) a real fission reactor.

I've always thought that the possibilities of radioisotope thermoelectric generators were under-utilised. They would be amazingly practical for off-grid living. Surely it must be possible to make a relatively safe one by packing it inside a solid metal case and then burying it in the ground outside your home.

I wonder how far an EV could travel with an RTG in the trunk.
Its clear that you could afford to not use microservices (which is great! You didnt burden yourself with the cool approach since it wasnt necessary). Not everyone has those requirements though and may NEED them
Same way SEC deals with everyone else.
Hmm maybe you could explain that further? not sure what you mean? Or do you have any recommendations what this could mean for me to do?
ok! Perhaps I am wrong then. I could not find Keryx on the historical catalyst site I use (likely because it merged so the ticker is gone?)
The members also averaged 63 years old, right in the most likely age group to catch the virus.
Tyler Cowen on the future social and political implications of Covid-19 [video]
If you're using Slack/etc. primarily for "optional conversations", where not-reading or not-participating is no big deal, then Braid's design adds nothing for you.

But, if you are trying to have necessary conversations with your remote team, make decisions, etc., then I think Braid's approach helps.

Say in Slack, in your team's #dev channel, a conversation starts: "should we do X or Y for this feature?" with several replies. A few minutes later a new conversation starts "for this other thing...", more replies. And maybe a few other topics.

You happened to have been on a call for the last hour (or getting some focused coding done) and pop into the channel to see 50+ messages spanning 4+ conversations. Hmm... it looks like your colleagues overlooked something important about topic #1, but, the last 40 messages have been about topic #2, #3, #4, and they're currently talking about #5. You can try to restart the conversation about topic #1 (interrupting the current in-progress topic), or try to juggle multiple topics in the same room at the same time. It's doable, but it's a mess. The more active the channel, the harder this is to do well. Result: you train yourself to keep checking so you can participate at the right time.

If everyone was using Slack's threading ability, this would less of a problem, but, in practice, Slack's threading UX is an after-thought and I see Slack threads being used rarely.

Braid allows you to be a part of multiple separate simultaneous async conversations "in the same channel" (we call it a tag).
I would love to be a dictator ruling over a country whose protected rights were defined so loosely. You would never get me out of power.
This is what I do, I just develop monolithic stateless API's in Docker containers and run them as serverless Cloud Run apps or as Kubernetes pods, if one of them fails it's no big deal.

For particular usecases that fall out of the wheelhouse of my preferred language, I'll typically use single OpenFaaS functions + endpoints for these things (think doing ML with Python, or really heavy computation with Go/Rust).

This combination of containerized Mostly-Monolith with single-purpose endpoints for particular usecases works really well and is very productive. If something is much easier in another language (due to tooling/ecosystem) for example, then I can just build that method or sub-system out in whatever language it's fastest in with this architecture.
Welp, I know what my project will be during the self-quarantine.

https://adversarialfashion.com/pages/diy-resources
Apple and Google planning to work on contact tracing of coronavirus
they're short term ids, setup to explicitly prevent linking to any other hardware characteristics, etc
It's oddly natural to see them together.

Many years ago I was at a black market in Beijing filled with every possible fashion counterfeit, and I found one black leather belt that had both Gucci and Calvin Klein logos on it.

It similarly seemed natural for a second ("even more fashion, right") until my brain did a double-take.
This made me laugh out loud. Early this afternoon I walked by a local church on the way to do some shopping and there was a group of 8 or 9 people kneeling in front of it praying. They were holding signs with various slogans, one of which said exactly that: Churches are vital business.

I should mention this is a Catholic church that serves the Eucharist during every mass where multiple people hand out wafers to eat, using their bare hands.
[edit: grammar and additions]
The app using the API is provided by a local health authority. In order to trigger an alert to other users you need to have tested positive by the agency whose app you are using.
Anyone with ML development experience know what changes are needed to make this work on a CPU without a CUDA GPU? Seems heavily coupled to CUDA.
I absolutely agree. I always feel like commits are trying to serve two masters:

- Describe the immutable history of work done on the project by individual programmers. ("Then I fixed X but broke Y", "then I fixed Y", "then I committed before going home")

- Describe the semantic history of features / bug fixes. ("Merge feature X", "Fix bug Y", "Refactor feature Z")

Both of these logs of history are valuable, and git commits conflate both of these ideas to the detriment of users. The natural affordances of git seem to push you toward seeing commits as simply logging history, but having a history of features & fixes is more useful. (Because of git bisect, and it makes git log more useful, and so on). But throwing away all that information about what actually happened seems unnecessarily lossy to me. Its like we're trying to paint a revisionist history of our work. And retroactively modifying commits with rebase and so on works against a lot of git's other design assumptions - like commits being content-addressable)

I wish there were ways of flagging commits as "oh and by the way, this commit isn't just me committing for convenience. This commit merges feature X into the project. We've run all the unit tests. If you run git bisect, use this sha but not the others. Whitelist this sha in git log by default."
May I ask what high availability has to do with the microservices? Since many of my servers were designed for relatively large companies (like TELCO) high availability/reliability requirements were always there. Running 2 or more monoliths in parallel with the appropriate logic built in does not make them into micro services
Wouldn't an SSH app be doing the same thing?

Once you're using wifi you're using the Internet's TCP/IP protocols anyway.
I'm aware of the impracticability of everyone divesting out of USTs right now. Your points are entirely valid and are the reason the system is still being held together.

My point is there exists some set of circumstances in which that assumption changes.

As an example, at some fed balance sheet level + inflation level, your options are either:
1) Do nothing and end up with nothing
2) Do something and end up with more than nothing

I've lost count of total fed pledges at this point, something on the order of $8T? Say things drag on and that goes to $12T+? And say inflation takes off, is the fed really going to fight inflation? It can't.

You start seeing high double digit inflation while the fed is printing money and keeping rates at zero, and at some point you have to move your USTs into something. If you don't, you'll be left with nothing.

I realize this is incredibly hard to imagine given the current system, but things that can't go on forever wont'.
> someone who feels compelled to do good work. They feel a responsibility to make sure a task is completed as successfully as possible.

Just because someone feels compelled to do good work does not mean they actually take steps to do good work.

1) They might neither know how to nor know how to ask.

2) They might have a problem which is really hard for them to solve but really obvious for everyone else they know -- consequently they don't have anyone they can ask.

3) They might be deliriously sleep-deprived.

4) They might have no idea how priorities work.

5) They might be confused but too embarrassed to ask questions.

6) They might have fallen behind on their piece due to some normal reasons and then fallen into a spiral of anxiety.

7) They might be mis-judging how good their work is.
UV LEDs probably won't do much against cameras. You want NIR, around 700-800nm. Security cameras are generally sensitive to it, unlike UV.
it's explicitly not a tracking technology.
Is there a guarantee it would not associate with other viruses (possibly other strains, or even something worse?)

And the lack of testing to "save time" actually does not look like a good idea for a live virus you want to give to the whole earth.
Maybe, maybe not.

If we make these (very questionable) assumptions:

- Most qualified mainframe COBOL programmers are in an age bracket for which COVID-19 is very dangerous,

- and most COBOL shops are reluctant to allow all-remote teams,

then it might be harder to fill those jobs than it is to hire risk-tolerant / risk-ignorant young adults to flip burgers.
I hear your concern. Would the ability to "disable auto-creation of tags" solve your problem?
You die with no food.

You do not die missing a Sunday service or a few.
I'm not sure why you're speculating. There are plenty of resources online about why they are gathering, if you are actually curious.
> You're off by a factor of 100. It's .01%.

> For who? Someone who uses opioids? Maybe, on average, again you're off by a factor of 100 or more.

No, lol, it's not. Those are averages across the US population. Your lifetime odds in the US of dying in an automotive accident is 1:103 [1].

I should have said accidental poisoning which is 1:64 [2] but half of that is actually opioids (1:96) so you're still more likely to die of an opioid overdose than being a party to a car accident. Most people don't set out to get hooked on Oxy, they get hurt or undergo surgery, are prescribed them, and that's that.

There's 40,000 deaths per year related to car accidents, which if you multiply out by the average lifetime (78.69 years) is right around 3.2 million, or 1%.

This is fair to compare against COVID because due to its extremely limited propensity for mutation, the COVID mortality rate does represent what approximates lifetime risk. (i.e. unlike the flu, you won't get it again).

> South Korea is probably the best current testbed here...

I argue the best testbed is the German study I cited where they actually tested... everyone. CFR is not mortality rate, its about an order of magnitude higher, again, I cited my data. And in my intuitive explanation that you're not factoring out adverse selection risk of only very sick people going to the hospital in the first place.

> Normalized by population, Sweden has seen more deaths and more infections than California.

Because everyone in California is inside. I'm sure they've seen an order of magnitude more flu deaths too because nothing spreads when you're inside. They're probably seeing infinitely more car accident deaths, too. Life's risky, and you're not comparing honestly.

[1] https://www.iii.org/fact-statistic/facts-statistics-mortalit...
This is a really good idea. This has nothing to do with the current crisis but if you could somehow credibly guarantee hosting for 50+ years people could read stories to their yet to be born grandchildren. People with terminal diseases and a two year old could still read to their children after their passing. Consider it.
Is the poster a demon, a god, a bot, a human, or speaking on behalf of one? Of course I know the poster's intent, but the point is obviously controversial, so I was just calling it out. Plenty of religious people on HN with as much or more evidence to believe what they believe as the op has for their beliefs, but who don't feel the need to antagonize.
Firstly, the German study analysed one small particularly hard hit town, so how you are extrapolating this to "people" in general is puzzling.

Secondly, there is a very wide range of reported fatality rates, with myriad factors known and unknown, so why you've chosen the lowest one globally (which, by the by, has always been an outlier and in any case is edging up past 1%) as the "actual" rate is, again, puzzling.

Finally, you are making a giant but unfortunately common logical error in using these already questionable death counts to make the case for an overreaction without attending to the obvious fact that without this "overreaction" every town, village and city on Earth would be Bergamo, where army lorries are conscripted to transport the dead from overwhelmed mortuaries, or worse.

Do better friendo.
> Considering how standard it is, we might as well just make it a part of a software developer certification/license that you have to do once to break into the industry.

I think it is only a matter of time for this to happen. All it would really take would be two major companies deciding to standardize on some set of criteria, and smaller companies would follow suit for the sake of simplicity (and because no one really feels like they know what they're doing anyway).
Interesting, but shouldn't this be labeled 2007?
https://archive.md/ns6F8
Great satire! haha

There should be one of these videos for reactive programming as well. Misuse of observable pattern can quite quickly turn an app into a mess, making code navigation / minor change requests a nightmare.
Evidence of Neanderthal fibre technology: cognitive and behavioral implications
I’ve has the same thought on my ears... yeah OG AirPods I would constantly forget I had them on or think I had them on, these and just a source of annoyance. I just got off a call, I was laying in bed and I had to readjust them 10+ times in the span of as many minutes... really annoying.
I resolved this by adding a blob of PVC glue (using a hot glue gun) to a specific spot so the shell of my ear holds them in place. The trick is making it so it’s still possible to close the case.

It’s not perfect. But it was a big improvement in my case. And it’s non-permanent.

https://share.icloud.com/photos/0Gc9TrO4UWwv-kOns_o1sGmig
Only to humans.
It sounds like you want to ask

1. What motivates them.

2. How they communicate in the face of roadblocks.

-----

I suspect you want to do more thinking in order to be more precise about what you really want.
Sounds neat but I couldn't follow what problem this was solving. Having an internal network that uses Lets Encrypt certs and updates automatically?

I solve that with Traefik in a docker container. It's setup with Cloudflare as my DNS provider using the DNS challenge and Lets Encrypt to issue certs. By slapping a few labels on any Docker container I get to use https and a subdomain on my real domain name. Everything is automatic and, while configuration was hard, I didn't have to custom roll anything special. I don't need an external VPS (but I do need Cloudflare to act as my domain provider, for free). Seems like that might be way easier for most people?
Uh, I wouldn't expect the WHO to have a progressive agenda here as well but why all people in the book is dark skinned and no one is white?
The wildest 5G-coronavirus conspiracy theories explained – and debunked
> For instance, it allows programmers to quickly create user interfaces by declaratively describing them, in a so called SCREEN SECTION.

By the way if it seems odd to have I/O like this in your language:* this reflects the architecture of mainframes; because the CPU was so important, I/O was managed by external devices (typically themselves a cabinet of electronics, at a time when the CPU took up two or three cabinets itself). You'd write essentially a small program describing what IO you wanted and then let the IO channel controller be busy dealing with minutiae like dealing with the tape drive motor or input from terminals.

So the language would set up data to be slapped to a terminal (this would have been a decade or more after COBOL was written, once terminals with screens were available), which the channel controller would send to the appropriate terminal. It would then deal with input and once all was ready, tell the CPU that it had a bunch of input ready.

Terminals like the 3270 were even half duplex so would process the input and then send it off as a block, to make the channel controllers more efficient!

In the ARPAnet of the 1970s, the ITS PDP-10s and -20s took this further with a protocol called SUPDUP (super duper) which allowed this kind of processing to be done on a remote machine when logging in over the net (as we would do today with ssh). So you could log into a remote machine and run EMACS, and while you were editing a remote file with a remote editor all the screen updating would be done by your local computer! Even the CADR lisp machines supported this protocol!

* At the time not doing IO through the language itself was considered oddball. I seem to recall a line in the original K&R where they described C's I/O and made an aside, '("What, I have to call a function to do I/O?")'
The senators are probably thinking "What can you do?".