skysight-inc/HackerNews huggingface dataset:
That can be boiled down to the “Rule of 3”.

My CTO often asks me to implement a feature to do X and make it “generic enough to handle future use cases”. My answer is always the same - either give me at least three use cases now or I am going to make it work with this one use case. If we have another client that needs the feature in the future then we will revisit it.

Of course, there are some features that we know in advance based on the industry how we can genericize it.
Don't most folks uses TOTP-based schemes with Google Authenticator?

Unless you're using HOTP to mean HOTP and all extending schemes.
I know you're probably paid to do so, but please stop recommending that site operators use SMS for a second factor.

https://www.issms2fasecure.com/
Hey that's actually a really good point. First aid kits, hospitals, etc. Could half of it simply be trashed?
The sticker on the door jam with the VIN usually has the month and year.

The VIN has an indicator for which factory it was built in. You may find rumors/wisdom/witchcraft around one factory having better quality controls compared to another.

Which day of the week your car was "Manufactured" probably isn't a thing that even makes sense. That's just going to be final assembly. Each individual part will of course been manufactured on a different day. Even if you believed the magic of Tuesday is the best day, do you want to know the day your doors were hung on the hinges, or the day the pistons were machined?
In the 90s, a startup called WebTV managed to negotiate and buy a perpetual SOURCE CODE license for Perforce (P4). WebTV built their own good version control system called "SourceDepot" on top of P4.

When Microsoft bought WebTV they got this license, which enabled them to cheaply roll out P4/SourceDepot to massive teams for whom it was a big improvement over what they had been using. With access to the source, they could modify it to their needs and scale away.

Google tried to buy a source license early on, but Perforce had learned their lesson from what happened with WebTV and wouldn't sell them one. That's how Google ended up doing elaborate projects for years to prop up and eventually replace P4.

Source : I worked at WebTV, Microsoft and Google.
> OpenBSD-current users are not affected, www/mozilla-firefox update is already committed and will be available soon on the mirrors.
In 1884 Robert Louis Stevenson wrote A Humble Remonstrance in Longman's Magazine, which explained to Henry James that James totally misunderstood the nature of fiction and art. James couldn't help admiring it, and they became very good friends.

http://www.gutenberg.org/files/30598/30598-h/30598-h.htm#pag...

"The whole secret is that no art does “compete with life.” Man’s one method, whether he reasons or creates, is to half-shut his eyes against the dazzle and confusion of reality. The arts, like arithmetic and geometry, turn away their eyes from the gross, coloured and mobile nature at our feet, and regard instead a certain figmentary abstraction."
Twilio offers a service to send SMSes via an API. Of course they're going to tell you to use this.
Ticking Stick [video]
Agreed. We are not just securing for today, we are securing for perhaps decades into the future. If we don't know for sure what the threat is, then the right measure of paranoia is as much as we can afford.

We are not just securing ourselves, but our social network too. Something you do can be used to discredit your kids and grand-kids a long time from now.
Why not 4% with robots handling the rest?
Very interesting, I had the opposite effect.

I grew up in a very “red” part of the US and was given a very negative view of the French (or anyone else for that matter). I was so surprised to find the people were friendly, kind and inviting. A small French restaurant even stayed open late because my friend and I had just arrived in Paris and had no idea of where to find food.

The city struck me as beautiful. Everything was so clean and manicured (my town by comparison was dirty, dusty and unkempt).

Paris destroyed my sense of exceptionalism.
Famous people are sensitive to hate because they get a lot more hate than you and I do. People with half of Graham’s notoriety get a constant stream of messages and emails saying they suck, the world’s worse for having them, wishing them various kinds of physical harm. The idea that you should listen to everyone who’s mad at you becomes completely impossible at a relatively low scale of responsibility.
I'm not advocating every application should do this as evidenced that this is a toggable switch that's off by default and even by itself doesn't actually have this particular feature (I was forcibly stopping the app through the inline instructions.). Just that it can be done is a capability that some people are very interested in. There is a category of security products called 'moving target defense' that this capability fits into.

As for the syscall/security argument I find that to be one of the weakest security arguments for unikernels. Fewer syscalls unfortunately leads to a much smaller set of applications that can be ran. Even trivial hello world style of apps can use north of 30-40 different types of syscalls. Not saying you should keep adding more but spending time trying to reduce what's there is kind of a non-starter if you want adoption.
Was always wondering about that, only occasionally misspelling a letter here or there to see if a transaction would get approved. Can anyone corroborate?
It’s still a net positive. If electric cars didn’t exist two ICE cars would be sold...
The squashed it pretty quickly too since in 6 months they launched StackOverflow together.
You want trust, but you also want code review. The example lacked both.
For low-stakes auth or simply duplicate user prevention SMS is sufficient. E.g. dating apps, sharing economy services, e-commerce sites.
I feel the code aspect could have gone either way.

It's the human part that went sideways. Egos are fragile & this is essentially "your code is bad and I can do it better".

I've been on the receiving side of this exact thing - also duplication. Fortunately the dup was bad enough that I could see I was wrong.
This looks awesome. I’m an F# developer and I agree with your intro paragraph 100%:

“One of the ironies of today's computer programming landscape is that functional languages directly inspired by the declarative languages for expressing abstractions and equations of logic and mathematics, have been sidelined for mathematical and scientific computing in favor of imperative, dynamically-typed languages like Python and Julia.”

Sadly, I’ve found that every road leads back to Python when it comes to deep neural nets. I tried using TensorFlowSharp from F# but found it very frustrating. Only Python seems to have full bindings to the TF API. Would love to give your wrapper a try.
DRY is good but like any abstraction it has tradeoffs. It might give you a warm feeling to do the refactor, but you might end up with code that's harder to understand and harder to replace.
PypeRaptor – Quick and easy multithreaded pipelines in Python
I didn't write Google Cloud but if you had your own server 5ms and even lower have been reported by OSv && NEC.

http://cnp.neclab.eu/projects/lightvm/lightvm.pdf

Nano/Pico is obviously unrealistic. :)
These are all super nice and I really wish more developers made use of these, but my main complain is not having username and password fields on the same page :/
Can someone tell me how you 'point' one of these things? It looks very 'concreted into the ground'...
Bullshit culture as it is.
Building an abstraction for React intl messages
Nix: A Safe and Policy-Free System for Software Deployment (2004) [pdf]
I don't think this is really a case of a "real name" policy gone awry. For starters, to be a Lyft driver, you have to supply your driver ID (including your official name). The issue at hand seems to be the names the drivers choose to be visible to users on the app, e.g. "Jon" instead of "Jonathan". If Lyft had a real name policy, they would just force drivers to display their name as it appears on their submitted driver's ID.
iOS autocorrect has always been terrible, it’s not exclusive to profanity. Both in terms of its performance and experience. Its incredibly frustrating to use when it autocorrects words 3-4 words later, and navigating text fields has become significantly more difficult on recent versions of iOS.

Android is the superior experience in almost every UX category imo, and text handling is the best example of that.

sent from my iPhone.
It is much easier to refactor and extend code that isn't riddled with duplication and mangled with hardcoded business logic. Abstract your code and write your implementations well, name things in a way that people can read it and write tests that describe what's expected from it.

Especially in a statically compiled language - “extract method”, “extract class”, “pull members up”, etc. is an automated, guaranteed safe refactor (ignoring reflection) .
Thank you Dan, your posts have been a great source for a lot of us out here.
Twitter seems to filter through the prism of US standards of speech. Woe betide you if you're Scottish and use the word cunt. In Scotland there's quite a lot of nuance in the usage of cunt. In fact I go so far as to say that the use of "profane" language is a bit of an art form in Scotland, but sadly not appreciated by our Facebook and Twitter overlords.

https://www.youtube.com/watch?v=qdCmFg4xIPI
SiliconValleyitis: why you are sick of the tech BS
Write your first beginner OS kernel in C and assembly
I saw it as well, before reading the comment pointing it out.

Therefore, there is some sort of signal that we're picking up on. That signal, almost by definition, is the aforementioned dogwhistle.

It isn't quite the right tone to not be somewhat obvious. Since it is intentional, it doesn't matter "how bad" it was: It's the conscious attempt to insult/denigrate/hurt that itself becomes the problem.
Isn’t the only reason we care about duplicate code that we don’t want to miss an instance of it for enhancements or bug fixes down the line? Don’t we have technology that helps us reduce that concern?
Micro-Services
Yes, financially this is similar to being good at picking credits. Some firms will default, some will not. Buy the ones that won't. Or another related analogy is convertibles, which are a sort of bundle package that is separable. That's not an economically useless activity at all.

The big question though is why does he think he'll be better at this than others? Or rather, for his investors, why will it be better after his fees?

He's got a first mover advantage by the looks of it. It takes some balls to buy a team with music experience to do this new thing. Of course you have the issue that some other guy will just do the same and compete with you, just like umpteen financial businesses (eg Private Equity).
They're just words. You can always turn the TV off.

See also:

https://youtu.be/78OevDyH7-Y?t=187
The crazy shit that happens when an address is entirely correct would make me hesitate before adding errors intentionally.
Are there any AAA studios using rust yet? I personally think it's not going to happen any time soon, but I'd be glad to be proven wrong.

My theory that it won't happen without some form of inheritance-like structure. Games, like many forms of simulation, are inherently stateful and tends to fall hard on the OO-side of the Expression Problem spectrum. Traits tend to give you the best of both worlds, but in very important aspect it falls short: the traits themselves do not have data members. I saw a proposal where you could link object data members explicitly to data members that the trait required, which would probably fill that gap...but I don't think it has gone anywhere. Anybody know what I'm talking about so I can look up the progress?
> "...are on record as implying" [citation needed].

Citation brought bellow in this thread, whether or not it implies what I believe it implies is probably not an argument to be had here.

> You obviously have no idea how much the Rabbis (or even the layman Orthodox) believe this stuff.

You obviously have no idea how different the notion of G-d as taught by some Rabbis is from the one that is presented to the layman Orthodox. For that matter the way that the Pope thinks of G-d today is not the same that the layman Christian does. And I don't believe that all of them believe in G-d allegorically but I think the foundational ones mentioned in the Talmud did, the Rambam (Maimonides) too probably.

> It makes no sense that the people who gave up their lives rather than give in on minutiae didn't believe in G-d.

It makes the same amount of sense for a literal belief as it does for an allegorical one, the 'minutiae' is a symbol for the underlying principle of self-determination.

> Without sources, your claim should be dismissed as projection or wishful thinking.

Precisely.
And OP themselves excluded "size". So I guess they are upset that people don't dress up. A'right.
Pipedream: List of Integrated Apps with Node.js
He really means "less correlated". Just about everything is glued to interest rates and the general economy.
I don't want to use HN to discuss politics, but notice that the 'Russian collusion conspiracy' is not a conspiracy theory. Donald Trump Jr himself published the emails setting up a meeting with a Russian lawyer which - he admitted - was supposed to yield information that'd help his father in the election. That makes it the very definition of a real conspiracy, right?
Old songs have greater surface. Many more people have heard it over something popular today which 20% might have heard of. New music is usually much cheaper. Even within the same artist. Would you lic. Bieber's Baby, baby O or something new. More extreme example would you lic gangnam style or anything newer by that artist?
I've read Koopman; fascinating stuff. Really solidified my understanding of the use of multiple stacks in Forth-like environments.

But I think it's instructive that none of the commercial architectures he describes (from 1989) have a contemporary descendant (although I think you can still get the RTX 2000 as a space-rated special order at an astronomical unit price). I think that tends to support my premise.
> I don't know how I feel about hidden surveillance cameras in public.

Me either. I mean, once people get used to just having cameras on them all the time, they'll basically just ignore the camera and act however they want. No real need for hidden cameras, just have to be patient.
It's pretty much the same as production software code.

I'm not talking about code to visualize data and present in some form of media. They are part of DS for sure but more for BI and analysts.

For instance, in my previous experience with data science we've built production pipeline to ingest, digest, create model, serve model on some API. The model updates itself every so often, all without human intervention. Code powering something living in production like that would be production DS code imo.
> It has to do with the tone and sharpness of the sounds.
Not implementing SMS 2FA doesn't mean a site would implement anything either.
Yes. And code review should enforce that kind of discipline.

I am not generally interested in individual commits from feature branches though, but when I do I can easily reveal them when needed.
I am. I don’t see how Django is getting it wrong, so I continue to use the auth provided there.
I bet it has a bus and lawyers in it.
I'm not a mathematician, but it sounds like what this is saying is that as soon as you allow a number to contain an infinite number of digits, you can get an infinite loop when you try to do a simple comparison. (For example, try to compare pi to an number that's not-quite pi. It might be a little more or a little less, but you can't know this without looking at all the digits, which is impossible.)

As a consequence, there are only two boolean-valued total functions: always return true, or always return false.

I guess that's why we don't use infinite streams of numbers for computation.
Excel is still king in finance and much of other demanding cases.

Google Sheets ate the lower end, though; it's a bit like iOS vs Android.
Is this a brand new essay, or is it one that pg has talked about / published before? Because I am having an extreme case of deja-vu right now. Was this originally published 10-15 years ago?
right, and

3. rosetta only emulated the actual app binary; eventually it called in to native libs, so performance for the most part held up really well iirc (for apps, not sure about games)
Paris Syndrome
it is true
Comic Sans is OK if sufficient white space is allowed between consecutive lines. I once visited a website where the descenders of one line mashed into the risers of the following line. It was pretty much unreadable as paragraphs resulted in rectangular blocks of squiggles.

I pointed this out to the website's author but he took no notice. I didn't visit his website again.
This seems a quite dangerous way of thinking. New attacks, methods to attack crypto are discovered regularly.

It's not, really, because there is obviously some security margin that is too high. It makes a lot of sense to consider and try to quantify what that is. If all we have is some vague 'well, there are always new attacks' then how do we know the current margins are enough? Why not double the rounds, crank up the hash sizes, etc? It's not really a meaningful response to Aumasson's work.
At that point it’s not even meant as a statement of fact, not really. Surely his response to an investor offering less than a $100B valuation wouldn’t be “you don’t understand the economy haha”. Some people just take the attitude that any claim which won’t get you indicted for fraud is a legitimate PR tactic.
I don’t know why it got removed; but how crazy is it that he implies the goal of climate policy is global socialism? It’s about the earth dude! How is that arguable!?

I don’t agree with him but I don’t like the intentional echo chamber tools of the vote system. It’s a chilling effect IF you do have legitimate criticism of any topic. I’m becoming bubble sensitive, I’m sure I’m not the only one.
Making of Disco Elysium: How ZA/Um Created One of the Most Original RPGs
> If you want to modify a method that has 10 unique contributors. Do you really need to talk to different 10 people to maintain to make a change?

I think the more apt example in this case would be if somebody made a modification in that file and you rewrote just their modification immediately after they done it without discussion. If the modification is necessary so soon it means that the feature/implementation were not discussed properly before and the process probably needs revisiting.

Of course if you are modifying part of the file, or doing some previously agreed refactoring effort then explicit author consent is not necessary.

> Secondly: version control. If you want the old version of some code

I think here we talk mostly about production code. The problem with relying on the source control for "I will revert this to the old version when it will become required" is that the code will evolve in subtle manners and it will be hard to roll back and apply all patches on top of it.
Welp, no more HN for today. See y’all with my new product on Monday
Wow...

At the point where you're professing sadness for Paris' dead culture in reference to the immigrant population, it's no longer a dogwhistle. It's just blatantly obvious standard-issue racism.

Also most of the people in the Banlieus are third-generation French. Thinking of them as "non-Europeans" is another big fat racist standard. And also part of the reason these people are having a difficult time succeeding in France.
A lot of people in the comments are wondering about using SHA-2 vs Blake3 for password hashing. The answer is, neither of these is suitable by itself for password hashing. Sadly there’s still a lot of advice on the internet (and, sadly, real systems) which do things like store md5(password) in a database and call it a day.

Blake2/3, SHA-2/3, and other cryptographic hash functions are meant to be fast, while also effectively guaranteeing no collisions or any way of reversing the hash (pre-image attack). This makes them ideal for stuff like checking file integrity, message authentication, inputs for cryptographic signatures and the like. But since they’re meant to be fast, they’re very poor choices for hashing low-entropy data such as passwords - attackers can test vast numbers of passwords (even if you salt!!) on GPU hardware.

For low-entropy data, you want a hash function that is slow and hard to parallelize. Use a specialized password hashing algorithm like bcrypt, scrypt or Argon2, and tune it so it’s slow enough without impacting overall usability (e.g. takes 50ms on your server). These algorithms are resistant to parallelization, so attackers will only be able to test a small number of passwords per second. This slows attackers down and can prevent them from recovering passwords that might be recoverable if stored using SHA-2, etc.
I think the principal is still the same. Surgeons do not perform surgeries every day. They usually have some days of the week they meet with their patients in an office setting. And then other days of the week they are in back to back surgery all day. It would be interesting to know what, if any, industry standards determine which days are allocated for which. Or if there is a hierarchy of surgeons who get "dibs" on scheduling their surgeries on Mondays.
> 2-pizza team

Unrelated, but since you spoke of this, I just want to tell you whoever came up with this term severely underestimated our teams appetite.
I do believe a browser app can do pretty much the same as a native one, but I agree that the important bit is they didn't see the big picture: mostly free tech, no installation, safer, low mantainance, out-of-the-box truly client server, etc.

Actually the web now is 100X more beautiful and responsive than at that time. I mean what you can do with an intranet server, not the radioactive media monstrosities.

Not really a spreadsheet person, I can believe Excel is better than Sheets. But is web vs native the reason?
Also in security for a long time, spending a lot of that with hospitals and healthcare organizations. My experience matches the parents. Your points are very valid but doctors can definitely be dicks as well.
This is one of Go's weirdest features. When you cast nil to an interface, you pay for extra storage so the runtime can do method dispatch on what type of object you don't have, even though every implementation is likely to panic immediately.
In Berlin. A great city: fast, honest, poor & sexy.

Stay away.
“Haters are confused admirers who can’t understand why everybody else likes you”

- Paulo Coelho
I wasn’t doubting on existence of a research team like that. I was doubting on the research mentioned. You cannot just say people who use a particular tool (like git or git5) are less productive. That’s just absurd.
I would like to see the performance of KanagarooTwelve in the same tree structure as BLAKE3, with AVX-512, on the same hardware (AWS c5.metal).
Off topic:
Docusaurus V2 makes a really clean looking blog via GitHub pages. Cheers
Or just not filter names on an app like Lyft. You can't even see other users' names. Who is potentially being harmed by even a malicious Professor Fuck?
Leaving common knowledge undocumented is, in itself, a misguided attempt at DRY.

Your common knowledge isn't necessarily everyone's common knowledge; what you perceive isn't necessarily what it is.

Every day there are many people just starting to code. There are cultural and regional differences. They might not have hit the exact spot in which this information appears.

Knowledge also disappears, fades, gets censored or destroyed, gets mixed up and remembered incorrectly. You might take something as a given and misremember it 20 years from now. You might read your own code 5 years from now and not know why something's there — something that was taken to be obvious.