skysight-inc/HackerNews huggingface dataset:
Apparently computers are crappy along the enitre DoD huh, I've heard that form every branch now. Your job definitely sounds interesting, did you have to go through SERE or is it just pilots?
It was kind of a mix of stack ranking, fire X% on a periodic schedule, and up or out, you've got X years to get promoted or you'll be fired. Microsoft says they stopped stack ranking, but it's not clear if they did. Facebook says they don't force a ratings curve, but they did while I was there. Just because something has fallen out of favor and companies acknowledge that it's fallen out favor doesn't mean they don't do it.
I do think that her "the mainstream scientists are doing it wrong/lying/wasting money" shtick advances mistrust in science in general. That worries me.
I gave up on it, but for a different reason. Strava is basically "done" in that all the roads have been ridden tens of thousands (and even hundreds of thousands) of times. Take away the cheating and the ranking on climbs just becomes ossified over time. It basically started out as a fun activity and turned into a public performance that nobody else cared about.

There are plenty of other apps out there you can use to track your personal progress that don't have the "social" bit attached.
Subaru was able to hack this by making their Legacy station wagon a truck since Chrysler was able to game the system with the PT Cruiser "truck".
I guess if you put it that way, the statement might be correct. But the disparity between US and UK being so big, I feel like the argument is a bit weaker. Using the average on such a small set doesn't seem to be so useful if there is such an outlier.

There are some interesting lists here: https://en.wikipedia.org/wiki/List_of_countries_by_Nobel_lau...

I guess you could also look at laureates by country born, considering many people went to the US in WW2. But I imagine it'd just devolve into senseless nationalism.
Thanks for the link, it's really helpful.

Just wondering is there any good reference books on designing and writing ICT security policy including backup strategy?
>I find that people with much more C/C++ experience (>5 years) tend to appreciate Go the most. Present company included.

In our shop there's plenty of former C++ devs who are now writing in Go and enjoying it, myself included. Initially everyone was skeptical and dismissive of the language to say the least ("no generics? ha!") but as soon as we started developing and releasing our first microservices people began to appreciate how smooth and painless the whole development process had become. I remember with horror our C++ projects' 2 hour long rebuilds, 1 GB debug binaries, days of chasing memory corruption heisenbugs... It's symbolic that the last C++ talk I attended before fully transitioning to Go was by a guy from Intel who spent 2 hours talking about how they abused templates to write allocators which allocate other allocators at compile time... Fortunately Go devs don't have this cult of overengineering that's plaguing C++, we're getting things done and release cycles are now much shorter and with less stress.
So, the fully fleshed out form of this in databases is usually called Bitemporality. The official SQL standard has included this for some years now, but it's not widely implemented by databases.

An intuitive way to think of bitemporality is it's like MVCC, but with 4 timestamps per row version. One pair describes a range of time in "outside" or "valid" time, ie whatever semantic domain the database is modeling, the other pair describes a range of "system" time, which is when this record was present in the database. This lets you capture and reason about the distinction between when a fact the database models was true in the real world, and when the database was updated to reflect this fact (some people call this "as of" vs "as at"... the terms here aren't fully settled but the basic distinction is). So you can revise history, do complex time travel queries, all sorts of stuff. It's a very useful model that directly aligns with what sort of questions businesses need to answer in the context of a court case or revising their ground source of truth due to past bug or error.

The downside is your database balloons with row versions, and many queries become far more complicated, perhaps needing addition joins, etc. Also from the perspective of database implementors there's a ton more complexity in the code. So that's why it's not widely supported despite the standard.

There's also a niche of databases built around this model from the ground up, usually based on Datalog instead of SQL. There's also overlapping work with RDF and Semantic Web thinking (as awry as all that went).

In practice how most organizations address this is operationally, by keeping generational and incremental backups that let them restore previous database states as needed. Though as the original post we're here for proves, that kind of operational solution can bite back hard when it goes wrong.
A Curiosity of Spirit (2010)
In the recent Go critiques posted in HN I got really annoyed because the articles came across as snide and such-and-such miscellaneous things (that I expressed in a somewhat poor, reactionary way last time)

In my humble opinion this article is very well written. While it leans more negatively and is a critique, you're being very professional and respectful. I appreciate your write-up and perspective. Some of these issues flow into problems I've also had with Go, particularly in trying to use it for a GraphQL API (which was a horrible idea!). Feeling cautiously optimistic about generics :)
The stack you already know and are comfortable with. For me, that's unquestionable Groovy & Grails, but for somebody else, the answer could be completely different. For the auth stuff, I default to using CAS. Again, just because I know it and am familiar with it, not because it's necessarily objectively "better" than the other choices.
> The stereotype that women barely ever date "below" them, in wealth, height, status, remains true. Your character still matters, but only after checking the above boxes. Men are selected by utility, with disastrous consequences for those that get left behind, as there's no mercy for them. You can't explain the harsh "be 6' or keep moving" requirement or the open ridiculing of short men on evolutionary selection alone.

If it was this cut-and-dry, 80% of American women would just be single at any given point in time, or they'd all be in polyamorous relationships, or dating their own gender. Only 20% of American men are 6'0".

I'm assuming that it's not this cut-and-dry, and that most American women are willing to date the other 80% of men.
Off the top of my head, airbags, anti-intrusion beams, ABS, pedestrian protection (the hood has to be higher, which makes the whole car taller), rollover protection (the pillars are much thicker to prevent the roof from collapsing).

They're sensible things, but each adds weight. Most of them scale sub-linearly with vehicle size, so the burden literally weighs heavier on small cars.
Instead of that folded-up piece of paper, if you have a box of business cards you'll never get through, those double as wallet-sized durable scratch paper. :)
You think that poor and working class folks pay income taxes? You'd have to pair it with a fully refundable tax credit to make it even somewhat viable, but even then, folks won't care. All they will see is money leaving their pocket every time they visit gas station. I think you over estimate the rationality of people.
> No, it wasn't. There was a huge body of experimental evidence already about gravity. It was true that all of that evidence, except for the anomalous precession of Mercury's perihelion, could be explained by Newtonian gravity; but general relativity, as a proposed new theory of gravity, had to also account for all of that experimental evidence. In other words, in the appropriate limiting case (weak fields and low speeds compared to the speed of light), general relativity had to reproduce all of the correct predictions of Newtonian gravity. That was a huge, and very important, experimental constraint.

Yes. I assumed that reproducing Newtonian gravity in the classical limit would be considered theoretical, as we had a solid theoretical understanding of Newtonian physics. Implicit in that would be a bunch of empirical evidence; but Einstein wouldn't need to explicitly think about the details of what evidence supported Newtonian mechanics (beyond the general understanding that it was all in the classical limit).

> Not if the differences between its predictions and the predictions of the previous theory (in this case Newtonian gravity) are only measurable in astronomical observations at the time the new theory is proposed.

Such a theory is not "useful", for many definitions of useful. Astronomical observations allowed us to verify Relativity earlier than we otherwise would be able to; but eventually technology advanced to the point where we could conduct satellite based experiments to directly confirm it. The theory was not practically useful until we had this technology.

> Technology can of course be developed on a purely empirical basis, if you're prepared to make a lot of mistakes along the way that you wouldn't make without a good theoretical foundation. If it hadn't been for the knowledge of relativity on the part of the scientists involved, the GPS satellites probably would have been launched without any capability for adjusting their clock rates.

Its not like we launched the entire GPS constellation then just hoped it would work. Before launching the GPS constellation, we launched the experimental Timation satellites to act as a proof of concept. Difficulties with maintaining accurate clocks in orbit would have been noticed then (if not sooner).
Show HN: Pyffr – a simple way to add payments to regular email
Pyffr allows you to add a conditional payment to an email exchange simply by carbon copying @pyffr.com with the amount. For example, to send someone a $20 payment, you just CC: $20@pyffr.com in the email you send them.

Hacker News members get a $10 initial spending credit to try Pyffer. Use the credit to send $5 to a colleague or someone whose work you want to support:

• CC: $5@pyffr.com in an email you send them.

• You'll get an auto-reply from Pyffr with a link to confirm your payment (and you would fund it from the $10 credit you get),

• Your recipient will get an email from Pyffr that your offer is confirmed and the $5 is held in escrow.

• You and and your recipient should CC: $5@pyffr.com as you reply to each other.

• You can close the offer at any time and release the $5 to your recipient.

• Your recipient can withdraw it via PayPal or Venmo.

The overall idea is to facilitate adding a payment to regular email communication (as opposed to just to sending a payment to an email “address” as in PayPal, Zelle, etc.).

https://pyffr.com
Proposals like that create perverse incentives. If gas taxes become a significant source of tax revenue, the government starts depending on them, and lower gas consumption starts looking like a threat. While consumers would have the incentives to reduce gas consumption, governments have many indirect ways of encouraging activities that generate tax revenue.
That’s not a problem in California because it’s not possible to buy anything to get the mortgage in the first place.
Modern stateless rest microservices are popular for many reasons, including ease of scaling and ease of reasoning about performance.

This entire system seems very stateful.

Also, in the real world, requests to one web service end up cascading out to multiple web services, with differing permissions models. For example user comes in with a token, makes a request to a web service, which then has its own secret store that it fetches an API key from to make a request to another web service.

Very rarely in life has it been as simple as "fetch data from this API". It is "fetch data from this API given this auth token and that API takes that auth token and uses it to get another auth token, attaches some tracing info for diagnostics in case things go wrong, writes some metrics to a DB so the team can track API usage, then goes out to a couple more services, gets data from them, collates it, and eventually gives some data back to the user."
every employment sector in the USA seems to attract intermediaries as fast or faster than the new workers.. the more imbalance or imperfect information, the more aggressive the intermediaries get in requirements, fees, conditions, oversight, control of recourse, control of information, access to new details, and more
There is a technique in mathematics where, if you can express the "same" problem in a different domain, i.e. if you can prove that the two expressions are fundamentally the same, then it may turn out to be easier to solve in one domain than in another. For example, geometric vs. algebraic. This seems like a similar technique, except that it is expressing the "same" problem in a much less emotionally charged domain, so as to be able to think about it more dispassionately.
My theory is that if you stay in a city, you are very likely correct. In a city you have to compete with men much taller and attractive. And women have access to hundreds of those men 24/7 through their cell phones constantly hitting on them. You won't win, but in a smaller city/rural town, you have much more chances.
Millions of bees die after Delta Air Lines mishap
Via Rob Henderson's newsletter:

Muscularity is the strongest predictor of mating success for men.

A study on males aged 18 to 59 found that muscularity is significantly positively associated with the number of total sexual partners and partners in the last year.

Handgrip strength is correlated with self-assessed happiness, health, social confidence, overall physical attractiveness, and overall number of sexual partners.

Researchers recorded short videos of 157 different men. Next, they had a group of male viewers watch videos of the men and asked, “How likely is it that this man would win a physical fight with another man?” Then the researchers had a group of female viewers watch the same videos and asked, “How sexually attractive is this man?” Eighteen months later, the men in the videos completed a questionnaire asking about their sexual history of the previous 18 months. How tough a guy looked to men was a much stronger predictor of mating success than how attractive he looked to women.

In this study, researchers asked two different groups of women to look at photos of different men and rate how strong the men looked. Results showed that the rated strength of a male body accounts for 70 percent of the variance in attractiveness (this is a massive effect size). From the paper: “None of the women produced a preference for weaker men…in both samples, the strongest men were the most attractive, the weakest men were the least attractive.”

See https://www.sciencedirect.com/science/article/abs/pii/S10905...

See also https://www.sciencedirect.com/science/article/abs/pii/S10905...

https://www.sciencedirect.com/science/article/abs/pii/S10905...

https://royalsocietypublishing.org/doi/pdf/10.1098/rspb.2017...
Lying about your height is actually an acceptable thing to do if it is to get over people's prejudices. In all honesty a good chunk of the people you encountered probably wrote you off prematurely anyways. But online dating and Tinder isn't great when you're trying to look past superficial qualities (your face, your height, your basic physical characteristics) so it's setting you up for failure, not to mention the way these apps are setup makes it really low effort for men to and woman to each have unrealistic expectations, and setup the vast majority for failure.

But if you're still looking for things to try, I would recommend you get some activities (sports, hobbies) and meet people outside of a purely dating context. People's guards will be down and they'll be evaluating you on your other qualities rather than height in these contexts, and the extra time you spend with them is exactly what you need for them to overcome their prejudices.
Heard that's not necessarily enough, "not specifically naming".
google: "filipino average height"

You might have some luck over there :)
IANAL but the laws have carve outs for backup retention, etc.

A simple technical solution is to store all data with per user encryption keys, and then just delete the key. This obviously doesn't let you prove to anyone else that you've deleted all copies of the key, but you can use it as a way to have higher confidence you don't inadvertently leak it.
As a lefty, I find that the reporter's notebooks are ideal for carrying out in the world. The binding stays out of my way, and every pair of facing pages forms a long column that works nicely for notes, snippets of code, and shopping lists.
If your bones get unusually hot, they may be mining Bitcoin for North Korea.
On the contrary, driving has never been safer!

https://en.wikipedia.org/wiki/Motor_vehicle_fatality_rate_in...

The only blip came from the introduction of smartphones (distracted driving). But I think people just need to know one of the tradeoffs has been fuel economy.
This was in currency more-or-less equivalent to the US Dollar? Was it made of vellum!? Even as a paper snob, $100 for a notebook elicits a visceral reaction.
its a really weird stock - has been traditionally super undervalued for the longest time. problem is its in taiwan so presumably the historical undervaluation relates to the geopolitical uncertainty surrounding taiwan's chinaness
60mg is the dosage sold for "12hr". 180mg is the "24hr" dosage.
I'd be interested to hear people's thoughts on the Zettlekasten system from people who have actually used it.
Certainly this is the only reason Germany is behind the UK. They were somehow the centre of the scientific world despite their less-than-ideal political conditions and then they ran their own talent out of their country. (And then they lost the war and the superpowers came and took the remaining talent, which was still formidable)
> You are arguing in bad faith, just like the OP.

Can we keep discussion civil? https://news.ycombinator.com/newsguidelines.html - "Assume good faith."

> There are several important differences,

Historically. But if the historical context of slavery did not exist, it would still be just as unacceptable to treat Black individuals differently.

In essence, historical context is largely irrelevant to whether an action is right or wrong. An action is right or wrong in itself (with respect to the contemporary common moral framework, (which may itself be influenced by history) etc.)

As such, treating Black individuals differently is not more or less wrong than treating short individuals differently.
Editorial work is close to sales in that it's clear that editorial quality impacts sales and it can be clear who did the editorial work on an item that sold. (Depends on the editorial process though, if you do a lot of group work, maybe it's hard to say who did how much).

As opposed to IT work where sure, if the editors computer doesn't work, it's hard for them to do their editing, but there's not much connection to a specific item.
People address some of these issues piecemeal with linters and code generators, but maybe there’s an opportunity for someone to create a Go++ language that accepts Go syntax but also extends it with sum types, nullability annotations, no default values, checked error handling, operator overloading for collection, etc. I remember people were excited (and dubious) of the Go-like language V.
I'm 159cm/5'2.6" and people quite often mistake me for a woman.

In school people did call me short but in time I learned to ignore it and to just not hear it. Because there's really nothing that I can or even should do about it.
Akamai claims Multicloud and Multi-CDNs architecture are deceptive
The original content has been deleted, check https://web.archive.org/web/20220430224148/https://webcache.... as well.
> Labor seems to be one of the few things where supply and demand dont apply.

I don't understand this. From my perspective, the labor market in the United States today is possibly the best example of supply and demand mechanics.
Yeah, it would be far cheaper too :-/
Microsoft aren't exactly known for privacy, given how much data they collect continuously from Windows users (e.g. details on every application you launch, hard-drive wide program sweeps, etc). Also with Github specifically they used everyone's code to fuel their machine learning product without asking permission.
Lee Smolin's 1997 book, "The Life of the Cosmos" was where I first learned about the idea of universes evolving through black holes. I don't recollect if it was his idea, but it is certainly creative.
This is pretty par for the course, though. Who else is incentivized to determine what is "good enough" wrt user experience/safety on Google's platform? Microsoft, Apple, Canonical, Samsung, Steam, Amazon, etc are all the arbiters of what's "good enough" (or safe enough) for their respective platforms (and marketplaces) because it's their brand at bat when something _isn't_ good enough (or safe enough).

"Android" (by Google) takes a reputation hit when someone downloads malicious APKs from anywhere, including Google's store. Google, therefore, wants to reduce the availability of bad apps in their ecosystem; maintaining an app store that enforces their standard of quality is one approach to accomplishing this goal, dissuading unknown apps they can't vouch for is another.

Obviously, there are both pros and cons to these approaches (from both Google and the end-user's perspectives), and they could definitely be improved, but they accomplish a concrete goal of "reduce malware on Android".
> In Structure and Interpretation of Computer Programs, Abelson and Sussman describe an arithmetic system in which the arithmetic types form an explicit lattice. Every type comes with a “promotion” function to promote it to a type higher up in the lattice. When values of different types are added, each value is promoted, perhaps repeatedly, until the two values are the same type, which is the lattice join of the two original types. I've never used anything like this and don't know how well it works in practice, but it seems like a plausible approach, one which works the way we usually think about numbers, and understands that it can add a float to a Gaussian integer by construing both of them as complex numbers.

Julia uses this in pretty much all of its math functions and probably elsewhere as well, and it works unbelievably well. The type promotion system makes math Just Work, even (and especially) in the face of different-sized numbers. The result is that 99.9% of the time you simply don't have to think about the types of your numbers. Here are some examples from the docs:

julia> promote_type(Int64, Float64)
Float64

julia> promote_type(Int32, Int64)
Int64

julia> promote_type(Float32, BigInt)
BigFloat

julia> promote_type(Int16, Float16)
Float16

julia> promote_type(Int64, Float16)
Float16

julia> promote_type(Int8, UInt16)
UInt16

And not only are types promoted, but in well-typed Julia code, the deduction of promotion types happens at compile time instead of runtime, so there is almost no performance cost to this either.
Tobii can sue whoever they want, too. You sure you can afford better representation than theirs? If they're as assertive about their license terms as it sounds like they are, I'd think hard about it first, I suppose.
Ideally they'd encrypt the customer content with a key provided by the customer and destroyed when the customer requests account deletion. The customer would still be able to use their key to decrypt backups that they get prior to the request. If the customer changes their mind, they just upload the key again (along with the backup, if necessary).

Of course, this means trusting Atlassian to actually delete the key on request, but there's not much reason for them not to.