skysight-inc/HackerNews huggingface dataset:
Many thanks, indeed, Kabb. I hope the manifold is still working after, uh, seven years. (You're aware, of course, that it's covered by my exclusive 1,000,000 year guarantee.)
Even in hot regions, existing cooling systems may not be designed for higher temperatures happening earlier in the year.
Better than most site search engines, which I admittedly a pretty low bar.
Population reduction advocates never seem to argue that themselves committing suicide would be the moral choice, which reveals they are valuing the preservation of their own current lifestyle over the lives of the "others".

In practice, it seems like the majority of people who call for population reduction are white/western supremacists who lack empathy for humans born with less privilege.

Birth control should be freely available to every human on the planet. Beyond that, I don't think there is any moral policy available to reduce population.
I'm a consultant, been on thousands of calls with customers, partners, colleagues ... after all this time it is still truly astounding how many people wait to talk instead of listen, and cannot or will not exhibit professional empathy and curiosity.

It truly is just not in our nature.
For folks looking for a shorter / cheaper crash course I've seen this one pop up that seems connected to a practical environment to use long term.

https://developers.google.com/machine-learning/crash-course/

I'm tempted to try this to add SOME data analysis skills to my existing skills.
Amazingly, the GOP just last week formed a Conservative Climate Caucus with something around 60 members. They even explicitly admit climate change is man made

https://www.usatoday.com/story/news/politics/2021/06/25/utah...
Investors would be happy that they get to participate in a project of a bigger company. Typically those opportunities don't exist.
This is by design a temporary solution according to the NCAA but I wonder if it will just end up being permanent.
Thanks for the luck Travis! Def something we've been edging around for a while. From what we've been seeing, a lot of PMs and no/low code folks already do this kind of thing manually, and don't have tooling for it. RF automation is now way better / easier to use than when you were with us (imho, of course).
FWIW, I have a kid (and a second on the way), and I want to go to an office, my office - not back to the office. That is, I want a separate place to work from, to make work-life balance easier and better insulate myself from the kid-related chaos during work hours.

But this can be solved with just renting a separate flat and using it as an office; something I actually considered, except small flats are the new fad for real estate investors (at least where I live), so prices are ridiculous.

Going back to the office, the company building, removes a lot of the flexibility and freedom that are important to me, and bring in heaps of crap that I don't want to deal with.
The easy part is the copy-paste-from-SO part ;)
Do Amazon care about jurisdiction, UK registration is ~£200, perhaps any registered trademark will get you recognised by Amazon [in all jurisdictions]?

If someone is squatting one's trademark you can still sue them with an unregistered mark, and perhaps crucially if they're using Amazon then Amazon should be up for contributory infringement.

This is not legal advice and represents my personal views only.
If you're in a major metro like the bay area, 1.5 hours still doesn't get you far enough to afford anything like enough land for a hobby farm on anything short of a FANNG salary.
Renters Could Collect Home Down-Payment Points with Credit Card
For anyone that wants to help with this, check out the Archive Team Warrior project. You can donate bandwidth and some CPU cycles to archiving different parts of the web. There's a VM image you can download that makes it really easy.

https://wiki.archiveteam.org/index.php/ArchiveTeam_Warrior

You can choose to help archive reddit, pastebin, URL shorteners and other ephemeral parts of the internet

https://wiki.archiveteam.org/index.php/Warrior_projects

I've also taken to updating the citations in Wikipedia articles with archive links.
Part of the issue, IIRC, is that you want regulators who are experienced with what an industry does, and practically speaking the easiest way to get that is to hire from within the industry. We should probably keep that bit of the revolving door working.

The bigger problem is the reverse; we should really have the government do something like finance's "garden leave", where leaving employees are paid while banned from industry employment, so that whatever competitive info you had is outdated by the time you can take a job in industry again.
The global water cycle is the embodiment of scale and even though engineers would learn a lot of interesting new things and make mistakes in the process of implementing desalination at scale, the brine problem is trivially solvable with existing technology like longer pipes and flow control (changing the exhaust concentration based on ocean currents and seasonal factors).

The problem is the criminal mispricing of water in most of the world. Anything that interacts with saltwater - especially brine - is in a completely different class of infrastructure that requires constant maintenance, something that most political systems are especially bad at. It's compounded by the artificially low price of water and accompanying lack of funds.

Humans have built over three million kilometers of natural gas and oil pipelines globally. The longest undersea pipeline is over 1,200 km long, which is at least twenty times longer than the longest pipelines we'd need to build for ideal brine dispersion in the worst case geographies. For better or worse, the problems with desalination are economic and political, not technological. We just need to spread out our impact so that it's within the margin of error of ocean currents and evaporation.
I'd say voting in officials who are willing to pressure these nations
The right person for doing QA for code written by developer A is developer B, who is motivated to show that there is breakage in the code written by A. This is just good old peer review, in the sphere of development.

The industry uses dedicated QA people based on the assumption that you can get two for the price of a developer.

In fact, if you have two developers, one of whom is more clever than the other, you want to give the code cranking to the less clever one, and use the clever one to verify the code cranking and make improvement suggestions.

If you have clever people designing the system, and clever people finding problems in the commits, you can just have average coders cranking out the bulk of it. Most code doesn't need cleverness, just persistence and consistency.
This presumes that trees cause wealth, or that wealth causes trees, rather than the other possibility with correlation: the same traits that make one rich make one likely to plant trees.

There is a saying 'society grows great when old men plant trees under whose shade they'll never sit'. Such long-term thinking has been shown to create wealth. Like money, trees take a long time to grow to full size and experience exponential growth (at least until they reach some terminalish size).

We ought to expect that those who plant trees have those traits which make them money in the long run, which -- contrary to popular belief -- is how most 'rich' people end up acquiring money. Boring, long-term investing, in trees and money.

Either way, fixing the problem by fixing the appearance is unlikely to change the problem.
Are National Security Letters still a thing? Are the requests the Microsoft executive mentions NSLs?
Why? They're often part of the same ownership class that stands to make a lot of money from the status quo. Even if the world goes to shit, they're wealthy enough to insulate themselves from the fallout, and probably wouldn't mind being lords of the ashes.
Lopis, you're right. Forward planning has never been my strong suit, and backward planning doesn't seem to work for me. There are some smart people in the world who can predict demand. Not me!

And, about twenty minutes ago, I ran out of large Klein bottles. It'll be September before I can get more, what with shortages of borosilicate glass.
That is a valid use case despite being small and incremental. I think it will still be helpful to some people.
There are 241 coal power plants in the USA.

Get 50 people chained up in front of the gates, and stop workers and coal coming in.

Maintain this human blockade until the last coal power plant is shut down. Ignore arrests and ignore the police.

Screw the impact on the 'investment'. The grid will handle the loss of electricity anyway.

That's about 12,000 people across the USA who could actively shape the future of humanity.
> In a large business, no one understand the whole business maybe except legal department and CEO.

lol... what?

A CEO of a 20,000+ person company literally sees projects as revenue sources and a deadline, nothing more.

To get it delivered, he/she walks down the chain of managers until they gets answers. It's might as well be a black hole.
And what would you accept as proof? Meteorological models showing the jet stream gets "wavier" with increased temperature?
Geelong is in Victoria, Australia

This is very fine detail, it’s like Google Maps but down to 1mm I can see grass blades in detail
Devs doing QA worked fine for us. You need to have a team that actually cares about the product, and you need figurehead devs - not necessarily seniors or team leads, but charismatic people others will fall into line with - who model the behaviours you want.

The problem with almost anything else is that it increases the number of hand-offs between groups of differently-aligned people on the route to production. If you're aiming at multiple deployments per day, with sub-hour commit-to-prod times, the latency in those hand-offs adds up way too fast.
That's why I said "in the 21st century". As far as I studied this, patents are a really solid idea in theory, and perhaps they even worked as advertised at some point in the past. But the way they work today, they're thoroughly gamed - patent owners get the benefits, the society doesn't get its promised returns. But I agree, it's a pretty nuanced topic.
Slow, yes. Klunky? Absolutely not. When you make a request to the Internet Archive, you're searching through a massive amount of data. The fact that it only takes a few seconds to pull up a decade-old webpage is amazing.
France would react. If people start mass dying in Algeria, many of them will try to get to Europe.

Algeria being a former French colony, being close by, and already having a large population of Algerian descent (https://en.wikipedia.org/wiki/Algerians_in_France says there are 10 million people of Algerian origin in France. That’s over 10% of the population), France probably will be a major destination.
Cloud-connected smart appliances are banned in my home for that reason. All they do is become landfill the second that they fall off the tail end of the upgrade cycle.
I've had a couple goes at teams trying to roll out cucumber tests, and I still don't understand quite what the point is.

Nobody but developers could actually manage to write any tests, and it was harder than just using the normal tools, plus maintaining all the glue besides.
Hey! Socrata is awesome :) The basic idea here is that you can write a Splitgraph plugin for any type of data source [0], so we like to use Socrata as a convenient example. Each plugin includes a Postgres Foreign Data Wrapper (FDW) to translate from SQL to whatever upstream query language (e.g. Socrata FDW [1]).

By default we don't copy any data into Splitgraph (although we do cache query results keyed by AST). When a query arrives, we parse it for any table identifiers, and "mount" a temporary foreign table for each, using the appropriate FDW. Foreign tables are mostly transparent to the Postgres query planner, so a JOIN will work (example [2]), and an FDW can even optionally implement aggregate pushdown. But yes, especially in the case of cross-dataset JOINS, there are some pathological cases. When your use case outgrows live querying (e.g. due to pathological JOIN queries), you can ingest any data source into a Splitgraph image, a versioned snapshot of data similar to a Docker image. [3]

Our focus right now is on the internal enterprise use case. We use the Socrata plugin as a demo, but our customers are more interested in plugins for data sources they use internally, e.g. Postgres, Snowflake, Google Search Console, CSV in S3, etc. We support all those too; you can mount them all locally, and you can also mount them on Splitgraph.com (or an internal deployment), but still thin docs / no web UI yet.

[0] https://www.splitgraph.com/blog/foreign-data-wrappers

[1] https://github.com/splitgraph/splitgraph/blob/master/splitgr...

[2] https://www.splitgraph.com/workspace/ddn?layout=hsplit&query...

[3] https://www.splitgraph.com/docs/concepts/images
I agree with you, but I just was trying to understand the fly.io post. They also wrote:

"Most GETs are reads, but not all of them. The platform has to work for all the requests, not just the orthodox ones."

So I think it all depends on which level of the application you take the decision to gracefully fail and replay the request elsewhere. In some case, it is trivial: as soon as you see a POST/UPDATE/DELETE, because you trust your app; sometimes you may need to take the decision later, or at a lower level.

In the simplest scenario, fly.io could just forward the request to the right region, without even bothering the app server to reply with an error, but that would work only if GET requires no writes.
Grey Watch Dealer Vanished with Millions of Dollars in Inventory and Funding
Say what? Why would brokers need to put up their own collateral to back customers’ long-settled cash? Because if the risk (to the rest of the market) that the broker doesn’t actually have that cash? That seems seriously messed up.
I assume China is also taking in a proportional amount of climate refugees as well.
But then you're settling for low quality testing. There's an excellent methodology a good test team uses on devs that throw it over the wall. They throw it back with the first bug report.

That said, it's sometimes the right thing for the team when something gets thrown over raw. A good test team should be fine with that and play their part.
If the choice is reducing emissions or saving lives from dehydration, I wonder which is the appropriate course of action.
Edit: Here's a really well executed online tool that someone else made: https://pinfruit.com/

------

Went digging through my old files, turns out this was almost 10 years ago!.. and looks like I left it unfinished.

I was using nltk to convert cmudict words into MM sequences using phenomes.

Then I was basically brute forcing all the different ways you could slice the given sequences into sub sequences. Then the idea would be to try and identify the "best" sequence.

You'd want to restrict it to using relatively common words, preferably nouns. Really you'd want to avoid any words that are ambiguous or could be easily confused.

Even better would be able to find grammatically correct sentences that fit the sequence.. but I think it's unlikely you'd have any hits.

Anyway.. this is the broken/unfinished code I found in the depths of my hard-drive: https://github.com/johtso/mnemonic_major
Just like Obamacare... income taxation is the foot in the door to basically allow the government to arbitrarily meddle in the personal finances of every single citizen.
> The official Catholic stance - essentially "teaching" people are no different from cattle, sexuality-wise

The church is perfectly fine with promiscuity, artificial insemination, sterilization etc. among cattle or pets.

The same behaviors they tell humans are immoral, because they think humans aren’t just cattle.
> It's amusing to see k8s used in such a different way and one that often uses a lot more hardware while driving up costs.

To be fair, google runs its own datacenters with teams doing research & optimisations on all levels of the stack: hardware and software and most importantly an amount of engineering resources converging to infinity.

The rest are stuck with VMs that share network interfaces and have to monitor CPU steal, understand complex pricing models, etc. Engineering resources are scarce so most companies will over-provision just to be safe and because profiling the application and fixing that API call that takes too long is expensive, will spin-up another 50 pods.
I’m sure getting an Oric and Blake’s 7 reference in a single post qualifies for a special upvote around here! Thanks for sharing, both great sites. I’ll dig out that Atmos I have in the basement!
Most of the effective opposition has come not from environmentalists per se, but rather from NIMBYs who don't want to live near a nuclear plant. After the incidents at Three Mile Island, Chernobyl, and Fukushima it's difficult to convince local residents that newer designs are inherently very safe. Even if they support nuclear power in principle they want it built somewhere else.
Each individual meme or video might not be important, but then I don't think future historians are going to spend much time studying individual artifacts in detail in the same way that current historians do. We live in the age of big data and I think future historians will be focused on aggregating and automatically analysing that data. They probably won't be reading your comment or mine but they might analyse large sets of HN comments with a view to drawing conclusions about how particular demographics act, think and feel today. And if large swathes of those comments are lost the conclusions will be skewed, particularly if the loss is not random.

Our society is characterised by the constant generation and exchange of massive amounts of information. It's one of the things that sets us apart from previous generations. Preserving only a small subset of that data that we deem worthy or important will not allow future generations to fully understand today's society.
Modest proposal:

If Microsoft really wants it to stop, just start releasing the complete records of every law enforcement official who requests one of these secret orders to the public. Maybe the need for privacy and due process will be made apparent to investigators when it is denied to them.
Why can’t the QA people just live on the dev team? Why do they need to be siloed away or not exist?

I had this in my past job. Have 1 QA per two developers, the QA sits with those two developers, and you are constantly telling them when a build is done and on staging. They write tests, do some manual checks, and then tell you how it is going relatively immediately. They also handle the problem of reproducing bugs and narrowing down exactly where they occur, which is not trivial.

For all the faults in that organization (including letting our test runner be broken for months), we didn’t put out a lot of bugs and we found all manner of strange edge cases very quickly.
> virtually no retail consumers should be doing

Yeah, well, I regularly read on HN about how retail consumers are locked out of investing in stocks, that only rich people can.

Robinhood blew that argument out of the water.

I've been a retail consumer stock investor my entire adult life, and would be pretty unhappy if regulations locked me out of that.
I've seen them used to do a decent smoke test to allow the QA people to make forward progress on other testing. I worked at a place that had a large number of computers running some testing software (robo something?) that ran through all the mainline scenarios. They constantly added new scenarios so the QA folks were working on much deeper flows until those too became automated.
The broker doesn’t have some way to credibly lock up the money so the buyer can’t back out, regardless of jazzedness or bankruptcy status?
Me SOLshare: Peer-to-Peer Smart Village Grids
Percentage are broken in many cases because they are ambiguous, and often difficult to compose.
+50% then -50% is not identity but ratio 3/4.

A plain explicit ratio is sometimes better. Ratio in decibel, or "doubling number" can sometimes be valuable alternative, could be used more often.

+1 doubling -1 doubling is identity. Same for decibels.
Having previously spent a decade in that role for a $1B company: I never got a veto right before stuff got sold to customers. I really, really wanted that in the beginning.

In the end what I ended up doing was spending a lot of time packaging the product as well as educating the sales force. If you don't have well-packaged products, the sales force will sell anything, even if it doesn't exist. And they'll get backed up by a typically slightly disconnected exec team, because they also want revenue really, really badly.

This strategy worked surprisingly well. I think both the sales team and the ever slightly disconnected exec team benefited from the artificial structure that I spent so much effort making up. I guess people instinctively just like following clear structures over chaos.

(This was 5-10 years ago, and not in Silicon Valley.)
To make such a conclusion based on this research is a logical fallacy.
Also the vast majority of contracts these days have "Arbitration clauses" that require all disputes to go through an arbitration process rather than lawsuits in the courtroom.

While there is a great debate to be had that many "Arbitration clauses" far too often curb consumer rights to civil courts (so called "tort reform"; putting limits on what your legal rights are as a consumer), arbitration has "always" been seen as the default first and lawsuits as the necessarily hard next step if arbitration fails (and if a given arbitration clause allows someone their rights to a fair trial in a court of law).
That's what code coverage tooling + human code reviewers are for. Look at the change in product, look at the amount of changes in tests - do they make sense? E.g., product change adds a non-trivial function with 10 if/else branches, but UTs touch only happy path - that's a legitimate blocker on the PR.
Regulating warranties and 'fitness for purpose' are both ways in which the state can enforce a level of quality/reliability on the manufacture of goods.

As an example, let's say your jurisdiction decides to make the following requirements on the manufacturers of food refrigerators;

1) The refrigerator must have a working lifetime of no less than 10 years from the date of sale, when maintained per the manual.

2) Repair parts for the refrigerator must be available for 20 years past the date of the last sale of the refrigerator to a resale outlet.

3) Information on the serviceability and repair of the refrigerator must be available to any party for a reasonable and non-discriminatory cost.

Those regulations say nothing about how much you can charge, how you manufacture it, or how you differentiate it from your competitors, they just make a requirement that the person who buys it can rely on it for 10 years and that if it breaks you must repair or replace it to give them the full 10 year lifetime they expected when they bought it.

What that does is force choices in design, manufacturing, and materials that reduce cost at the expense of expected lifetime back on to the manufacturer. As a result they gain no advantage by using cheaper stuff that fails more readily to get a cheaper price to "undercut" the guys who make the 10 year refrigerator.
simonw was referencing the replay overhead number. His request hits Los Angeles first, the rails app in lax says "go to Sydney", and the request gets replayed in syd.

The entire request to Sydney for me (from Chicago) takes 516ms, 15ms of that is "replay overhead".