skysight-inc/HackerNews huggingface dataset:
Hmmmm.

I am not a network engineer (any more, thank the hypothetical deities) so I have no skin in this game.

But in the 1990s, I moved networks from IPX/SPX, or NetBEUI, or AppleTalk, or DECnet, and almost any combinations thereof, to IP. I added IP on top of existing networks. I migrated systems from 10base-2 to 10base-T to 100base-T. I stitched together WANs. Then I moved IP networks from static to DHCP, from no name resolution to DNS to WINS, and so on.

I am not a total rookie to this stuff.

So when you say

> I don't think humanity has ever tackled a migration project of this scope and scale before.

I have to disagree.

The IP rollout itself was bigger, and yet, it happened much, much faster.

We moved the networked world from a dozen protocols to IP, then we totally re-architected how IP worked, from static networks to `hosts` files to name resolution to dynamic IPs and dynamic name resolution.

Then we rejigged it all again for a world of proxies and gateways, and firewalls, and NAT.

You make out like this is some vast super-hard thing, but in fact, the world of networking is way older than many people in the modern IP-only world realise, and we've rebuilt it over and over and over again repeatedly.

When a new technology comes along that offer compelling advantages, then the world moves to it, not in one smooth operation but incrementally and piecemeal, but it happens.

It hasn't happened to IPv6 and my argument, and much more importantly the arguments of the Avery Pennarun here and of Dan Bernstein, are that it hasn't happened because IPv6 isn't good enough.

It's good but it only fixes 1 problem and that one, while big and important, is not the whole problem and it's not even the most important problem because there are workarounds for simple IP address starvation, and the workarounds are _good_ workarounds with their own advantages, and some of those advantages are compelling.

The world has, overall and on average, decided that IPv4 is good enough to mean it's not worth the pain of moving. It's better to fix what it already has.

It is the same issue as Plan 9 vs Unix.

Plan 9 is better by almost every objective measure, but Unix is good enough, so the world decided to stay with Unix rather than the pain of moving.

For me, what is an interesting question here is "could we fix Plan 9 to make it worth moving to?" The Plan 9 people don't care, though.

Similarly, although it's not my area, it's an interesting line of questioning to ask "what is wrong with IPv6 that the world didn't move to it, and can we fix that?"

But when someone proposes it, the IPv6 proponents treat it as heresy, not as a simple, relevant question.

That in itself is interesting too, IMHO.
Show HN: Free,fast and unlimited Stable Diffusion XL generation, online
Hollywood calls time on golden era of cheap streaming
Yep. My Sony headset too. The WH-1000XM3. Once, this blinking blue led messed up with the dreams of the person sleeping next to me. Turn it on? Blinking forever. Pair it? Fast blink for almost 10 seconds, then blink again for a while. Trigger an action by mistake or because of your sweat through its touch interface? Blink 6 times, slowly. That last one is particularly crazy, there's already an audio feedback for this, no need to tell the world I decreased the volume of my headset one step.

It also screams loudly and for long times whenever I power it on and when I want to switch the ambient noise mode. At the point it can be heard by someone close, despite the closed design. Especially that the default is active noise cancelling, and it's broken most of the time, making a loud blow noise in one hear, and that the mode in the middle, that badly recreates the noise around, for which I have no use. Tough luck if the device establish a Bluetooth connection when it's speaking, it cancels the operation and the process needs to be done again. Please, please remember the last mode I used, this is the one I most probably want to use next time.

This device is gratuitously both noisy and very luminous. The latter can be somewhat fixed with some good electrical tape, the later requires a mobile app I can't install and it would disable any feedback, and reverts next time it needs to be reset. Despite its comfort and good sound, when it dies, I'll probably buy something else.

But I have to admit, a blinking eye mask has to be a whole level of craziness higher.
In case you missed it in the article, the author seems to address this in the section titled 'Effectively Managing the Norm'.
https://archive.ph/lfunT
Illinois passed a law in protecting financial rights of children of influencers
It’s a mix of that. This introduced a race condition and a frustrating rendering experience, but yeah it’s a flavour of this.
I think the software industry itself has accumulated enough bugs over the past few decades. E.g.

F-22 navigation system core dumps when crossing the international date line: https://medium.com/alfonsofuggetta-it/software-bug-halts-f-2...

Loss of Mars probe due to metric-imperial conversion error

I've a few of these myself (e.g. a misplaced decimal that made $12mil into $120mil), but sadly cannot devulge details.
The quoted tweet is still available on archive.org at http://web.archive.org/web/20201119112006/https://twitter.co... and reads:

>Welcome to tech. It's less likely malice and more likely you have a pretty dumb product owner that "doesn't see business value". And there you have agile....

I agree with you - the tone is quite disrespectful, especially starting off a message to a tech expert with "Welcome to tech."
Will be patched.
> It's because you cannot have native performance on something that is still the virtual machine

JIT compilers are a thing, so this statement is just plain false.

Also, apples to oranges comparison. I’m not saying that in this particular case it is not true, but that can’t be deduced from this datapoint.
I’ve been working on a Jekyll SQLite plugin: https://github.com/captn3m0/jekyll-sqlite.

Jekyll let’s you use CSV/YAML/JSON files as data source, but they’re unwieldy since the schema is fixed.

The plugin is meant to let you reshape your data before you use it within Jekyll. You get complete flexibility of SQLite, to let you join tables, use indexes etc.

What I can’t figure out is how to best do “dynamic” queries, say a query that needs to show the number of reviews on the restaurant page (restaurants is the table). Each of these page will need to run a dynamic query with the page.id variable.

SQLite Injection isn’t a big issue, since this is all trusted input. But I’d like something better than just Templating queries using liquid.

I’m doing some parameterized queries on the global level (see README). Need to find a nice way to do them locally.

Maybe just putting them in metadata would be a good way?
Nice Guys in that context are often self-identified though, "I'm a nice guy, why do I keep getting rejected?". I'm sure it originated from rejections in the form of "You're a nice guy, but..."
Shout out to another student on my university course. We had to implement this algorithm as a class exercise. Most people "discovered" the same kind of algorithm which solves it in 3-4 steps. However this other student came up with an implementation which seemed almost supernatural: It would get the right answer in a single step!

The random number generator on the old Sparcstations we were using used the time_t and PID as a seed, and the exercise test harness used a random number straight from rand(3) to generate the secret. The student's implementation simply worked out the answer from the date and process PID and knowledge of how the linear congruential generator worked.
APL (along with Matlab, K, Mathematica, etc.) was one of the influences for NumPy anyway.
doesn't work with cheapo zinc-carbon batteries. You can normally tell those though because they are lighter and if you squeeze them firmly they dent.
Isn't most performance problems down to the CPU waiting for something? (network - disk - memory - cache)
The lengths that engineering leaders will go to in order to avoid learning basic lessons about team building astounds me. “The norm” here is not very productive, it just means they are not killing themselves and each other.

People, like software, have different things they are compatible with, and if you try to shove incompatible things together then these problems arise. The managerial response is overwhelmingly “the problem is the incompatibility” and not “the problem is with our organization”.

Team formation is a combinatorial exercise where the best person to have in a team is a function of the other team members. Accept this basic truth and all else follows.

A difficult employee is a failing manager. Either there is something wrong in the organization or the employee does not belong there and you need to fix it.
If nothing else, eventually civilizations are confronted by questions (in math, say) that can only be solved by extremely large amounts of computation. We know there must ultimately be succinctly stateable problems that cannot be solved easily; this follows from the undecidability of math.
I should've been more specific. The statute is reasonable for young children; this method of enforcing it with AI is not.
If we call it Root Causes Analysis can we keep the acronym?
I don’t know, i agree it wasn’t in the react style but it was in the style of basic logic

On change detect new file is there,
Set file to variable,
Call api to save state.

The issue is setting the variable and calling save is now a race condition.
I have started putting electrical tape over leds. My external sound card had the brightest white flashing light when the computer was off but the sound card is still plugged in. Impossible to sleep with that obnoxious white blinking.
Oh nice, this could be my new favorite thing. It's less lonely than the usual. It's great for warming up, basically just trying to code from memory instead of relying on docs.

I love that it yells at me for naming my variables "xxx" too. I also love that it goes all "Candidate did not follow instructions" when it tells me not to use a specific function, but also tells me that the solution would get the right answer. It's just one of those things you wouldn't try on a real interviewer, but want to try to see if it works.

But $96 per year is quite a commitment for something that I could get bored of next week. Would be nice if there was a monthly option.
Beautiful Country, by Qian Julie Wang. Beautifully written memoir about immigrating to NYC as a child in the 90s. Poignant, sweet, honest, easy to read, fun, not too too emotionally heavy, but also full of lessons about trauma.
Aren't a lot of people an amalgamation of all of these characteristics?

The only time I've seen someone that does NOT have these negative traits, seem to be typically very silent, or not outspoken.

I've worked with some pretty good engineers that didn't have these negative traits. But they also didn't drive decisions. They could competently do something given to them.

But it seems like to be pushing boundaries, or driving to a solution, someone necessarily has some of these negative traits.
While I strongly support the idea of allowing users to control the location of their config files, I don’t really like the XDG spec, specifically the part where setting nothing ends up putting files in two or three disparate directories.

Also, it’s not “respecting your users” to change where their config is stored without giving them an option. Were OpenSSH to implement XDG, I may want .ssh to remain where it is, but the XDG spec would give me no way to specify that preference. Certainly a lot of tools would expect to find .ssh in $HOME but wouldn’t. And the systemd integrated stuff expects an active user session, which is not always going to be the case.

Sorry to say that it’s typical for folks like this to rant about respecting users while completely ignoring whole categories of use cases and insisting on breaking long-standing behavior for their own aesthetic sense of consistency.
That's why always go with cremation. No Vampire, no viruses
That's usually a good approach, especially scientific. When it comes to morals though, take heed. I'm not going to recommend anyone read Mein Kampf if they find the person behind it morally reprehensible.
This was a great book (especially audible). And I’m not even a gamer.
re: spants

Yes, people can have longterm pain (eg. headache) after the injections and without geting infected (which is one of the common long covid symptoms).

I guess it can't be answered by this study, given that it only studied peope with COVID-19.
>TI is launching a $0.40 (!) ARM micro soon. [...] It's just the new default in the same way that z80 was a default.

And yet many cheap electronic devices will continue to be built and sold with 4-bit microcontrollers because 32 bit is overkill for those use cases and $0.40 is too expensive when 4-bit dies cost $0.05 or even $0.01, and $0.35 in savings is huge in high enough volume.

You won't see any new products developed in the west using such microcontrollers but they're still alive and kicking and there's still developers for them in Asia.
Mixed Emotions: Compound Facial Expressions Will Be Important in Image Synthesis
Complex systems fail, but they don't all fail in the same way and analyzing how they fail can help in engineering new and hopefully more robust complex systems. I'm a huge fan of Risk Digest and there isn't a disaster small enough that we can't learn from it.

Obviously the larger the disaster the more complex the failure and the harder to analyze the root cause. But one interesting takeaway for me from this list is that all of them were preventable and in all but few of the cases the root cause may have been the trigger but the setup of the environment is what allowed the fault to escalate in the way that it did. In a resilient system faults happen as well, but they do not propagate.

And that's the big secret to designing reliable systems.
Only works with alkaline non-rechargeable batteries, but apart from that, yeah.
> Can perfectionism be "cured"?

I don't really consider it a "cure" but the way I manage my perfectionism (and holistic completionism) is to simply re-frame my goals to not meet perfect but to get as close to perfection as possible. As long as my actions get me closer to my goal, I am satisfied. It's a very brute-force and reduced version, but another way to say it is that if you want to go North, just never walk South and iterate in steps.

Also, I've basically eliminated failure from my personal language. Any task that doesn't achieve the desired result is simply a delay and I re-adjust immediately to find a new tactic that will put me back on track. If the time-effort to proceed isn't worth it, I dump the effort and change strategies. I long ago got rid of the idea that anything I create is special or worth saving. Outcomes are what matter. It's a very pragmatic approach and eliminates the perfection tendencies because it gets things done.
Update 3-Payments company Adyen's shares sink nearly 20% after earnings miss
i am an audiologist. this is my go-to method for checking hearing aid batteries on the fly, especially as it lets me work a bit messily.. for better or worse, i now have a habit of ripping fresh batts out out of a packet, without immediately disposing of the old ones i have removed from an aid, while my attention is focused on programming it (older aids often interface using a cable connected to a programming 'pill' which supplies power and data through an empty battery cavity... so i can be putting batteries in and out and programming cables in an out, multiple times in a session with a client... anyhow..) i no longer need to pay attention as to which battery is which, as i just pick up both together and drop them from about a 15cm height.. the old one bounces jauntily away, while the new one stops dead with zero bounce. it is a super accurate trick and the information never fails to astound clients.. it surprised me when i learnt it from an old salt colleague and it surprises me more that it is not common knowledge.. especially amongst my workmates.
My somewhat grumpy answer would be that web people almost never do their homework.

They are infamous for reimplementing things worse that were well available decades ago.
The evolution of complex grammars: Study measures complexity of 1,314 languages
Because Gitlab is blocked for my country.
It's >1 over what volume? The galaxy? The observable universe? All the unreachable volumes of space beyond that in our universe? All the many-worlds branches of this universe?
Oof!

> LK-99 is not a superconductor, but an insulator with a resistance in the millions of ohms — too high to run a standard conductivity test.
I think an article about "Working around difficult managers" would be more beneficial than marking almost any talented sweng "difficult" from the management perspective.
I keep hearing this, and sometimes people claiming it's not true anymore, so I decided to look into it.

Compressed hydrogen storage tanks are of 4 types [1]. Types 1,2 metal tanks, but they can be used only up to 300 bar. Their permeability rate is negligible. Type 4 is composite (e.g. carbon fiber) with a polymer interior lining. It operates at 700 bar (and various manufacturers state their product can work up to 850 bar). They have some permeability. Type 3 is similar, but with metal interior lining. Negligible permeability, but more expensive. I don't know how much more expensive, with these things all providers tell you to "call for quote".

In any case, the only problem is Type 4. They are the affordable alternative to Type 3, and they are also in much wider use.

There are some regulations and standards that govern them. Specifically EU 406/2010 and ISO 19881:2018 which prescribe a maximum steady state permeation rate of 6.0 Ncm3 of hydrogen per hour and per liter internal volume of
the container [2].

To be honest, I'm not sure how to read this rate. Toyota Mirai uses such tanks (2 of them), so it can't be that bad. Each has a volume of about 60 liters, and holds about 5kg of hydrogen [3].

The more important thing is that permeability is a function of the surface area. A tank 1000 times larger has a surface area only 100 times higher, so the permeability per volume goes down by a factor of 10.

Such tanks do exist and are commercially available. I'm aware of the Hexagon Titan XL that can hold 220 kg of hydrogen. The latest quarterly revenues of the manufacturer [4] show 57% year-on-year growth, so it looks like customers are quite happy with their offering.

[1] https://en.wikipedia.org/wiki/Hydrogen_tank

[2] https://www.sciencedirect.com/science/article/pii/S036031992...

[3] https://www.toyota.com/mirai/2023

[4] https://hexagonpurus.com/news/hexagon-purus-asa-results-for-...
I work on MonsterWriter. The Desktop app is on the market for some time now but now I'm working on a SaaS version.

Sign up is possible but the link is nowhere on the website:
https://app.monsterwriter.app/
> the ratio of speed of damage to speed of cognition?

yes, I too think this ratio is of vital importance (pun). I would not even call it "damage" (rather change) as this is quite anthropocentric and teleological.

But the acceleration induced when moving from cellular trial-and-error biological intelligence to human intelligence seems dramatic. Watching Oppenheimer reminded me of this "funny" moment when people calculated the odds of "igniting the atmosphere". While that is apparently not possible, igniting, e.g., the RNA is more plausible and I would not put it beyond what current societies are capable of.
https://archive.is/AfDVK
Software engineers, too, will have financial struggles.

Expensive illness in the family, divorce, triplets, cost of living crisis, natural disasters, accidents, unexpected salary cuts.

People's expenses typically track income, if your income for whatever reason suddenly decreases, a lot of folks, even "rich" software engineers can easily be in financial trouble.
> The situation is you are brought on board to do work, and you have in-house collaborators and you'll take the blame for their mistakes?

People really are like that, yes: Monday the boss says "X is now responsible for Y" and lo and behold, Tuesday EVERYONE already says "Y is not working well, X, do something, it's your fault!".

> Step back and find an outcome where your work doesn't harm their reputation/security. So how do you make them into allies? Or how do you not matter to them? Figure that out...

I have figured out part of that and I was genuinely asking if you have additional insights.
Wasn't that right around the time of Fukushima? https://en.wikipedia.org/wiki/Fukushima_nuclear_disaster
I didn’t find a single practical take away in the Voss book. The entire thing was him boasting about his “accomplishments”. I’d go as far as saying it was totally useless.
because much writing is like code so you start with an intention as to what you will need later, get done and realize you didn't need everything you thought, and if you're a junior or really tired or on a very heavy deadline don't do an adequate cleanup.
“ He, I know—for the question had been discussed among us long before the Time Machine was made—thought but cheerlessly of the Advancement of Mankind, and saw in the growing pile of civilisation only a foolish heaping that must inevitably fall back upon and destroy its makers in the end. If that is so, it remains for us to live as though it were not so.”

- H.G. Wells, The Time Machine

That’s one of my favorite literary quotes. From long before nuclear weapons, or climate change.

I think it’s entirely possible that technological civilization is unstable and self destructs. Certainly, at this point of our history, we can see what a fine line we walk. Had the twentieth century been but a little different at key moments, we could have already destroyed our civilization. As we speak there’s a land war in Europe from one great nuclear power, on the borders of the other. A third great nuclear power rises in Asia, as China is ramping up incredibly quickly - no doubt with a eye to deterrent over meddling in their aims on Taiwan. Their long term historical rivals in India, a rising economic power, will likely not sit idly by. They could be the fourth great nuclear power. That of course would force Pakistans hand to try to compete. Next door Iran desperately seeks the bomb to ensure they don’t get the freedom treatment from the West. Across the gulf lies their bitter rival Saudi Arabia, who warn they will have to pursue the bomb if Iran gets it. Meanwhile nuclear armed Israel has promised they will not tolerate a nuclear Iran. And that’s not even 100 years yet since we developed that particular technology. Nor is it the only technology we have that threatens to be more than we can handle.
There are of course losses when charging a battery, but they are orders of magnitude larger when talking about the creation of hydrogen versus the charging of a battery. Hydrogen simply isn't a good idea for a number of reasons, and the energy needed to separate it from water is just one of them.

Quoting "apples to oranges" here ignores the massive inefficiency in other stages of the process of storing and distribution of hydrogen, which is difficult and expensive to do. The distribution of electricity is much more efficient and cheaper.
That's close-ish to what I do, which is to have symlinks for frequently used directories in my home directory. And as most of those directories are actually on an NFS server, setting up a new PC is just mount the server, create the symlinks and then "cd someproject" or "cd ~/someproject' as usual (well, as long as you make sure you use the same UID/GID anyway).
In the Intro he cites a paper by Frankel, "Is there trade with other planets?"

https://scholar.harvard.edu/sites/scholar.harvard.edu/files/...
From Concept to Practice: Learnings from LLMs for Enterprise Production