skysight-inc/HackerNews huggingface dataset:
You can bet that there are a lot of social science researchers within Facebook (I know at least two), but they've learned to never ever publish the results of that research and only use it to increase revenue.
So, (if I could write LaTek in here I would)

The limit as JavaVersion —> Inf = Kotlin?

I won’t complain.
I'm sorry but that's wrong because that's trying to twist the meaning of words. No money, no healthcare isn't universal obviously. With no single-payer, government-funded, healthcare system, only doctors and patients who have to pay for everything themselves, that is in no way "universal healthcare."

The problem with charging poor people for healthcare is that they get sicker and sicker and then need emergency care, and that's more expensive than giving them free healthcare in the beginning.

It's unethical and classist to pick-and-choose who gets life-saving cancer treatment based on their income. Doctors with integrity would be abhorred at being presented with such a decision because it goes against the fundamental values of their profession.
why is it?
I very much prefer to generate svg charts on the server. Not only is this more sensible when you have a huge number of data points, but it even works with js turned off (unless you need interactivity).
Technical Writing – Google Developers
I guess it would only help if the dependencies can be statically analyzed somehow - e.g. a change in X causes a compiler error in Y etc etc - or you have really really really comprehensive integration tests.

In my experience this is not always the case and the problems creep in in other places that are not easily statically checked or tested, but which come up at runtime, e.g. specific runtime content/data, or serialisation of some message/object that happens at runtime.
> The market SOTA Abbyy is far from being accurate.

While Abbyy is likely the best, it's also incredibly expensive. Roughly on the order of $0.01/page or maybe at best a tenth of that in high volume.

For comparison, I run a bunch of OCR servers using the open source tesseract library. The machine-time on one of the major cloud providers works out to roughly $0.01 for 100-1000 pages.
I like it. The answers to the management question are what I’d want a boss to do in that situation. If only bosses read this page and let it sink in!
You can get those compile time checks with PMD. It plugs into all major Java IDEs and build tools.
Absent a contract on availability that doesn’t sound like something you would have a case for.
Completely agree with you that the study is trash, however ...

>but an unimportant journal in psychology.

This is untrue. It's comically untrue.

I was doing my PhD in cogsci when this came out and everybody was surprised that PNAS would publish such a bad study, given that we were more used to seeing things like this: https://www.pnas.org/content/pnas/106/5/1672.full.pdf and this https://www.pnas.org/content/pnas/112/2/619.full.pdf.

PNAS has an _excellent_ reputation in psychology, especially in the psychophysics and EEG/MEG crowd.
Chinese team finds Covid-19 has mutated with 2 subtypes
There was a bunch of abuse that already happened with host candidates, was fixed recently though! [0] Tor also did a bunch of really great work figuring out all the ways you can be fingerprinted.[1]

When I shared [2] a lot of people gave me flack for enabling malware. I don't come from that background, so hard to think 'how can people abuse this technology'

It is too late now to roll back all the WebRTC stuff in the browser now though :) Definitely would be mind blowing how much data is flowing because of it (and how much money is being made because of it).

[0] https://webrtchacks.com/dear-ny-times/

[1] https://trac.torproject.org/projects/tor/wiki/doc/Snowflake/...

[2] https://github.com/pion/offline-browser-communication
Integrate PMD and enable its errors as broken builds, done.
That's right, I forgot a method parameter:

jshell> class Foo { void foo(Object o) { System.out.println("Super"); } }
| created class Foo

jshell> class Bar extends Foo { void foo(Integer i) { System.out.println("Sub"); } }
| created class Bar

jshell> Foo f = new Bar();
f ==> Bar@7f9a81e8

jshell> Integer i = 1;
i ==> 1

jshell> f.foo(i)
Super

jshell> ((Bar)f).foo(i);
Sub
Turns out the latest hype is a dud for most companies ^_^

There are good reasons to use microservices, like when you have 100+ engineers working on your planet-scale cloud or social network. At that scale, you need to have internal API documentation to ensure people that never met can still work together productively.

But if you are a normal company, you will probably never have enough engineers to make microservices worthwhile in the first place. So just put everything into one big git repo and call it a day.

Also, the ability to do rolling restarts and no downtime upgrades by running multiple versions in parallel adds a lot of work and complexity. But for most small to medium companies, a planned 5 minute downtime in the middle of the night is completely no problem, so all that zero-downtime-upgrade work is just wasted effort.

I mean, even my bank has a fixed offline maintenance window every night from 3:00 to 3:30 am. As does Amazon RDS.

So don't solve problems that you don't have :) Most companies do fine without microservices.
Behringer Faces Criticism over Bizarre Attack on Journalist
Moreover, when you get an existence proof of a bug, it's usually easy to change such a system to seem ok.

As Hoare also said, "There are two methods in software design. One is to make the program so simple, there are obviously no errors. The other is to make it so complicated, there are no obvious errors."
The effect size is barely a blip on the radar...

This study is barely worth the paper it's printed on. Everyone in my lab was left scratching their heads that PNAS would publish such a weak result.

If you think this is important or period-defining, you haven't been paying attention to the field.
Yes, I forgot a method parameter there.
I think it was because Let's Encrypt had to revoke 3 million certs today: https://community.letsencrypt.org/t/revoking-certain-certifi...
Although its a preference, I don't seem to share your concern.

A half yearly summary of distilled main themes, decisions and learnings has been crucial for me to continue my journalling process.

When I want to know what I was doing late 2017, I go through my summary. Any detail I want to re-visit is available in my running log.
That's what this number is. Mortality rate of patients with COVID-19.
A lot of military and civilian signals intelligence outposts are out there, so they probably wouldn’t be so happy
The author needs to do some basic math on his example pricing. The way it is stated it encourages me to upload terabytes of random noise.
It's weird to think that Razor scooters or skateboards might be a privacy tool of the future.
Yes you will be doing software development, but only for what matters to your employer and nothing else.

Savy UNIX IT can take care of it, apparently the experience of what meant working in UNIX shops with thin terminals is now lost.
It is kind of sad to see. The carriers saw "hey all these people are giving away WiFi for free and not giving us money", so they fixed the glitch and just made their own version of WiFi that they get money for when you use. Imagine a world where the WiFi alliance said "fuck it, 802.11 is dead, we're going to use modern technology" and just developed 5G technology but in an open way that anyone could use? Things would be a lot better. But here we are, with backwards compatibility for 802.11b that eliminates any chance of ever getting good performance (except in an RF test chamber), and so companies are just routing around the damage and turning WiFi-alike into a profit center.

At one point the mobile carriers were just planning to just flat-out steal the unlicensed band: https://en.wikipedia.org/wiki/LTE_in_unlicensed_spectrum

I haven't heard any arguments about how 5G is going to come to rural areas, however. I think the backhaul requirements are pretty heavy. So in Manhattan, probably going to work out quite well. In the middle of nowhere? We'll see about that.
> Most people don't enjoy having a human driver who sometimes smells bad and tries to talk to you

god forbid another human being trying to make smalltalk.
He obviously meant $0.01/GB for the first TB, pricing $0.001/GB for the next four TB, etc., without the discontinuities, just like your taxes.
Or they’re just taking pride in their work?
> Your service can support a high amount of throughput (otherwise you won’t be able to earn as much revenue if you can’t service the amount of usage customers demand)

It's interesting to see this point under that angle, although it makes perfect sense: you only get paid after traffic has increased, therefore the service should scale first, then generate money to support infrastructure billing.

The bidirectional coupling of used resources vs revenue makes a lot of sense.

Now on the question of predictability of pricing (on the customer side), usage-based pricing, in some cases, should have caps to avoid over-spending. I'm not talking about rate limiting and DoS protections, but rather a way to tell your customers when they are about to hit a defined threshold, so they can plan their billing accordingly. This can give the customer the feeling of a bucket plan, but with optimal pricing and adapted resource usage.
Docsend’s Pre-Seed Data Shows Relation Between Number of Founders and VC Funding
As a metric, "social mobility" does not mean what most people intuit it means. Someone who, in real PPP terms from the same base, doubles their income may be wildly "socially mobile" in one country and not in the other, even though their absolute outcome is identical. This is because it is a function of income distribution which varies widely and is partly a function of country size.

Many people who are "socially mobile" in a country with compressed income ranges, like Denmark, will be objectively worse off economically (PPP) than many people who are not "socially mobile" in a country with wide income ranges, like the US. Income distributions need to be similar for social mobility comparisons.

Most people readily prefer a "non-socially mobile" increase in income if it is greater in absolute PPP terms than smaller "socially mobile" income increases. In these comparison cases, which are not uncommon, there is literally no benefit to being "socially mobile" in a country with compressed income ranges.
> the latest and greatest cancer drugs.

My understanding is that cancer drugs are considered to be experimental, so there's no "latest and greatest" with any guarantee.

Also, US doctors usually prefer to not get cancer treatment when interviewed, since they know "how the sausage is made."
The subject is interesting, but there's barely any effect. Look at the d scores!

>a massive (N=689,00!)

Your critique reads like someone whose never done any research or serious statistical work. Big N's don't automatically mean the results are robust.

I'm sorry, this isn't the groundbreaking paper you want it to be.
Why Every Company Needs Top-Notch Endpoint Protection?
> A startup has no business running microservices. Microservices are only when the engineering team can't scale properly because they keep stepping on top of each other.

While I generally agree with you in the vast majority of practical cases, it can make sense in some circumstances, namely, if there is a very clear logical abstraction between one service and another.

A microservice is just another layer of abstraction, similar to functions, classes, files, libraries, and programs, but even higher up the food-chain, and it comes with its own characteristics and peculiarities. If you have high confidence that one component is (1) logically extremely different from all of the other components, (2) has no side effects, (3) is not I/O bound as it's going over a network, and critically, (4) is on a separate development timeline, then you have a solid candidate for a microservice.
Options are a derivative, meant for hedging. It's relatively recent that they've gained so much attention as a primary security for speculation. There are decent strategies to make consistent income, especially in selling options, but it takes discipline and capital.

Most people just want the high leverage and quick wins which usually ends badly.
Yeah, but that kind of fits what I was describing, you are using standard SDK tooling, and it looks to me it being game engine like.
I literally make them, and they're powered by QMK. Check out http://gboards.ca/ and http://combos.gboards.ca/ for the fun stuff :)
I don't understand what this even means. For everyone involved in a startup, time is the most precious resource they're investing. If the startup is doomed, pretending it isn't and keeping employees on the hook is the worst thing a founder can do. And what is "blood equity"?
As a guy who can talk shop with mainframers, and taught Linux Security to to a classroom of them at a big blue building where such machines are manufactured, I concur.

There was the technical divide ("Buffer overflows? Meh, we just kill them and start a new instance!") to the generational divide - I was near-30 and this was near-2000. I think I was the only person there who didn't (yet?) belong to a charitable secret society.

This stuff is only very quickly hinted at in my CV. Trying to explain it in interviews is painful at best. It's a past job experience I've just kept mainly to myself when it comes to resumes. The age thing happens in both directions, and seems damn near unavoidable.
Problems like TSP are terrible examples because we have an excellent and affordable approximation for lots of them. A working general quantum computer (if anybody builds one) will be an expensive way to slightly improve those results. It's the gold-plated HDMI cable of quantum computer applications.

Factoring isn't like dispensing tape, it has one of the few applications (breaking conventional asymmetric cryptography) for which an expensive but working general quantum computer gives you a clear benefit (with Shor's algorithm) over just buying a lot of ordinary computers.

And all these press release "breakthrough" machines can't do it because it's hard. They're at best a stalling tactic, to buy more time/money to solve the hard problems and at worst they're essentially a con.
Being a QA guy myself, I am of the opinion that this sums it up pretty well:

https://en.wikipedia.org/wiki/Project_management_triangle
What was the difference between the rich and the poor family? Who is the parasite? What is it exactly that the rich family does better or gives to this world that they deserve the exceptionally better lifestyle?

Are they more intelligent? Surely not, since they were duped by the other family. Do they really care about other people and what's going on in their surroundings? Not really, they never bothered to figure out any of it, they are blissfully unaware of the of the less fortunate, untouched by the reality around them until it affects them directly. They don't care who serves them. Are they more virtuous? Not exactly, look at how they behave on the party when the girl gets stabbed. The dad takes his boy who fainted and tries to pick up the car keys, all the while pinching his nose in disgust of the 'poor people smell'. Does he help any of the wounded people? What are their actions?

> The rich people were never mean or overbearing to less well off people and treated their workers well.

How about the part when they act like they own them? One example is dad having to wear a costume for the boy because the boss is paying overtime for his non-working day. The driver dad is not exactly in a position to refuse or he could ruin his position (we saw how easy it is to get replaced), so he has to put up with it, humiliate himself and play the clown. The rich dad doesn't see how this is a problem, money should buy everything after all.

The movie is an allegory and it requires a deeper look and a bit of thinking. Contrast and compare this movie to 'Us', you will find similarities in how it deals with social class.
That could be the place that has https://www.ouroborosfarms.com/

Interesting aquaponics greenhouse. Worth a visit.
One of the takeaways:

> Usage-based pricing with automatic volume discounting incentivizes both parties to grow and win together.

Highly agree, especially if you're trying to see how viable a small project is. And if it grows quickly, I know I'll get even more value from the service provider and won't worry about leaving money on the table at the end of each billing cycle.

> Bucket-based pricing creates an adversarial relationship between you and the customer because the customer is always going to pay more for your service than they want to.

I do see the viewpoint from the service provider as well, as they know they have N number of users at P price point, and can more accurately estimate their monthly revenue, plan out growth budgets, or show higher profits on price increases.
I can't figure out one light pollution source in Poland in Sluchowo (54.77550N, 17.94972E). The map from 2015 shows some factory of sorts, but it disappears on the map from 2020, all you can see is an outline what it was. I really wonder what kind of place this was and why it emitted relatively a lot of light.
I use a Ploopy that's been modified to run QMK (just needs a ISP flash, nothing crazy) and has my onboard chording engine. It's a mess, but having 2^n inputs and a trackball is very fun and hacky :)

https://www.ploopy.co/
> but it’s no worse than a library of books

That's not my complaint in the first place. The problem is that while we progressed beyond books on the device side in terms of even just the viewport, we seemingly can't move past the letter-sized paged format. The format may be a bit better than books—what with it being easily distributed and with occasionally copyable text—but not enough so.

I'm not even touching the topic of info extraction here, since it's pretty hard on its own and despite it also being better with HTML.
The compliance world isn’t quite as fast-moving as tech. Even a “high priority” business continuity post mortem at a financial institution is going to take at least a week for all of the lawyers & senior management to agree on the language.
Especially lawyers, who by definition aren't too bad at screwing over others legally themselves.
That’s really interesting ! Do you have any feedback on how simple an API can be to be still useful and how you decide whether to start using one rather than build a service yourself?
The canary has been updated, but for some reason they rolled from SHA512 back to SHA1. Does not inspire confidence in their crypto-nerdery. Also, their logo is a bee. Bees make honey. Just saying.

Operators of these services tend to fall into 3 camps: the cipherpunks, the crypto AG's, and the one coin's.

I keep a strong prior on option 3, which means I need to be convinced a service is actually less hostile than whatever FAANG has on offer.
Totally irrelevant, but when you put the string "wicked problem" together twice like that, my brain refuses to scan it as anything other than a problem with a wick.
https://kodyrabatowe.ogili.com/cat/opony/
Great idea. Need that! I'll try it soon.
And Trump populism is another example of the poor rebelling.

Although them voting in a billionaire kinda defies logic, but hey, there's only two parties, plus Trump! :)
Caregiving, in-home nursing care, rehabilitation and long-term care (assisted living/nursing home/hospice) should be provided by a different social safety net department because of it's specialized and complex nature that also requires licensure and auditing (making sure elderly and disabled aren't abused or neglected).

Single-payer, universal healthcare should also include (all but cosmetic and elective procedures):

- prescriptions

- mental care including therapy, psychiatry, rehab and commitment

- dental care

- vision care and prescription glasses

- hearing aids (avg cost is $3000 USD)

- mobility and safety aids for disabled and elderly

- gym memberships for people below a certain income level

- smoking, drinking and substance abuse intervention, counseling and cessation assistance (medications, tools, relocation assistance)

- weight-loss for obesity/significantly overweight with effective, tailored, holistic approaches
How PropTech Is Impacting Real Estate Market?
Back then there were a lot less stackoverflow copy & paste mistakes.
Python Time-Zone Handling
Microservices only have two versions you should worry about: the one that's currently live and the next one. Two for each micro service you are responsible for. IMHO roll backs are not a thing. Instead git revert and roll forward when you need to deploy a fix. So once a service has been fully deployed, you permanently stop caring about the previous version.

Microservices should not be mass deployed together but be managed separately. That vastly simplifies the combinatorial explosion of versions you need the worry about: the currently live ones.

The rest is just applying SOLID principles to your microservices and avoid having services with poor cohesiveness or tight coupling (most of the SOLID principles boil down to affecting these two metrics). Bad service design with tight coupling where deploying service A also requires redeploying B,C,and D, is basically a design problem and not a micro services problem. There's a lot of bad design in our industry. Monoliths allow you to get away with that but it's also the reason that breaking them up is a hard problem. Just because you are getting away with it does not mean it is not a problem though.

You can further mitigate integration issues by deploying using modern practices like blue green deployments where you gradually move traffic to a new versions and adapt on things like error rates and other metrics, AB testing, etc. So if it breaks, you don't end up breaking it for everyone and you can fix the problem and try deploying that in a controlled way.

Basically your goal is to keep your customers (aka. dependees) happy and make sure you don't negatively affect them (which you should be actively monitoring). Likewise if you have dependencies (to whom you are a customer) and they stop working when you deploy something new, you probably want to detect and fix that before you break all your customers. If that is a regular thing, consider having integration tests, contract tests, etc.

Staging environments are a controversial topic in this context. My view is that they don't make much sense in a properly run micro service deployment since you are not testing in a real environment with real users, real data, and lots of things happening concurrently and features interacting. And of course your customers doing real things they care about. The only realistic environment that has that in most complex micro service deployments is called production. Once you add serverless and edge computing to the mix, these things become even more true. The bigger the organization, the less feasible it becomes to have a staging environment.

Update. I forgot to add this but doing continuous deployment means small deltas that are low risk. Any bigger change can be behind a feature flag. There are a few more strategies.

Also, I'm not actually a microservices proponent for small teams. It just creates deployment and operational overhead (read go to market bottlenecks).
Europe timezone | Remote

I've worked remotely for 2 years as a lead developer in a fiber optic company backed up by Xavier Niel, setting everything up from scratch. I have CS degree, 15 years of professional experience.

I'm looking forward to contribute in a small team with real, humble persons.

Email: yoricm [at] free [dot] fr
Personal Website: https://yoricm.com
LinkedIn: https://www.linkedin.com/in/yoric-mangeart/
StackOverflow: https://stackoverflow.com/users/4119809/yoric
A coworker pointed out that this is a huge point in favour of GraphQL: because it forces clients to explicitly ask for every field you can log those queries and use them to spot when a field is no longer in use.