skysight-inc/HackerNews huggingface dataset:
Thanks for the reply. I definitely feel that my idea of where it started is polluted by where we are now. However, the minimum viable product for evolution is essentially 'trait inheriting chemical structure' and even the simplest examples that we have of that today are incredibly complex.

>I get the feeling you're perhaps paving the way for a theistic argument. If you don't believe that god the creator exists, the proof that life is possible regardless of your stats is all around you

Nope. It's really not. There's no way for me to prove it, and I'm glad you said it out loud so it could be addressed, but it's really not. This honestly came to me out of my career in information security and tangents into encryption. If you think of those 'critical sections' as passwords or encryption keys to life, our current thinking just seems to be totally fucked by impossibly small probabilities.

The place where the ball settles in the saddle for me is panspermia OR that there is something that we don't quite understand in general about emergent phenomena that drives 'chance' in a certain direction.
Postgres doesn't natively support multi-master. (Although there are a variety of open source/proprietary offerings that add support for it to various degrees.)
> hence, stuff like this "Some teams go even further and require that the issue number is tracked in every commit." well, I was on a team that did this and a lot of other stuff listed here but as it happens it wasn't one of the most productive teams I've ever been on.

This shouldn't be interpreted so narrowly. In situations where you are adding small features for fixing bugs to an existing system, having a separate issue per commit really helps communicate the background and intent behind the commit, because a lot of problem solving takes place before any code is changed, and can be very helpful for people who have to change the code later on, or reviewers of the code just prior to commit.

If however you are working on a new concept by rapid prototyping, or working on a single large feature comprised of multiple commits, it makes more sense to have a single issue that represents that effort, and all commits related to it point to the same issue. This minimizes issue management overhead while still maintaining the link between the commits and their motivating rationale.

Either way, a link to the human conversation that gave rise to a commit or series of commits is very important for understanding the intent behind the code change.
Right, but the "platform immunity" thing applies equally to all platforms. You're instead proposing to extend immunity to some platforms and not others based on how they choose to recommend things. If you (like I do) believe that recommendation is a form of speech, this creates government favored classes of speech.

To word it differently: "Platforms that recommend/aggregate speech in government sanctioned ways are protected from liability, while those that do not are not". That's, while not open and shut perhaps, certainly spooky.
Database engines typically operate within a giant block of memory allocated at bootstrap which is used quite differently than a heap. Mutable references to the address space necessarily exist outside the address space, which presents problems for conventional memory safety models. There are also no pointers per se because almost all memory is directly paged -- objects have no fixed memory address over their lifetime. Most shops use a thin wrapper that implements a pointer-like interface (in the style of std::unique_ptr) that hides the paging and scheduling mechanics. The scheduler design, which is where most of the safety and guarantees that resources can't leak happens, is often verified with a model checker. It is perfectly safe to hold an arbitrary number of concurrent mutable references to an object because safe execution will be resolved dynamically at runtime (which is cheaper than it sounds). There are container libraries designed to work seamlessly in this type of memory model. To a developer writing code against this abstraction, it feels similar to a garbage-collected concurrency-safe language. No locking, no resource management. The abstraction isn't general purpose but it works very well for the kinds of data infrastructure applications where people use C++.

In many of these systems it is standard practice to generate arithmetically limited types pervasively. This is almost transparent in C++17. While it is possible to verify much of this at compile-time in theory, it almost never is because it isn't worth the effort (C++20 may start to change this) and testing at runtime has proven to be nearly as good. People underestimate what is possible with the C++ type infrastructure in this regard.

This type of software design was originally done because it allows for exceptional performance but has become popular for safety reasons. It uniquely allows you to make guarantees about runtime behavior under diverse adversarial workloads that would otherwise be difficult to make.

Bugs in practice tend to occur at the interface with third-party code, which requires dropping out of any internal type system, or in the form of performance anomalies due to unexpected hardware behaviors interacting with the scheduler design. Logic bugs in the core bits tend to be found in testing.
U.S. tech giants are reportedly providing services to blacklisted Chinese firms
Ah, I need to make a run to my local IKEA.
The problem also works in reverse. Probably the biggest example is Plate Tectonics - this idea took decades longer to be accepted than it needed to because the generation of expert geologists who were the gatekeepers for the journals refused to consider it seriously, and the guy who came up with the idea wasn't a geologist [0].

Scientists are just humans, after all. Subject to human flaws. And the scientific method works "in the end", not immediately.

[0] - https://en.wikipedia.org/wiki/Continental_drift
I’m glad you are able to move your use case easily!
Please read the site guidelines: https://news.ycombinator.com/newsguidelines.html. They say: "If the title includes the name of the site, please take it out, because the site name will be displayed after the link." That's why a moderator changed it: the submitted title was "Jepsen: MongoDB 4.2.6".

I don't mind making an exception, since exceptions are things sometimes. Jepsen is famous on HN, so the current title is not an issue. Indeed, referencing a specific finding would arguably be misleading, since this article is the Jepsen report about MongoDB 4.2.6. Btw, I don't know what you mean by "The first title (that specifically referenced a finding of the analysis) was best". The submitted title was "Jepsen: MongoDB 4.2.6" and it has only ever rotated between two states, one with "Jepsen: " and one without. Are you confusing this thread with https://news.ycombinator.com/item?id=23285249?

It's very silly to have this be the top comment on the page (I've since downweighted it, but that's where it was when I looked in). Yesterday I briefly swapped the URL of this article into the other thread, but then reversed that because it seemed that thread couldn't support a more technical discussion (https://news.ycombinator.com/item?id=23288120). I invited aphyr to repost it instead, which was quite a break from our standard practice of downweighting follow-up posts, but seemed like the best solution at the time. What technical discussion was our reward? Bickering about title policy!
I would not shrug that off for obvious reasons, but as they say, "the death of one man is a tragedy, the death of millions is a statistic"
No, the toll roads are pretty undeveloped but they’re a fast way to get places because they’re also lightly traveled except for people that absolutely have to and can afford to. The thing is, there’s really nothing along them except more suburban strip mall wasteland.
A deeper dive will find that it’s not conclusively proven yet, and I can’t find much evidence for the “one guy’s fuckup” assertion.
During the Corona period, 25 richest people in the world became richer
I am saying about blocking native main thread not js one for sure. 90% of the time people saying it is not shutter are 1) use very simple ui that does nothing or 2) it shutter they just have low bar for Android in general.
Download iTools iPhone Manager
Nice work! I really like the art style. It captures the minimalism of the original, while not resorting to voxels or a "hipster flat low poly" look.
Find something that you repeatedly do and try to automate it. Create things that save time.
> [top of readme] lockdown a newly installed linux os

> [bottom of readme] Supported OS: Debian

Not all Linux is Debian or a Debian derivative.

> Remounts /tmp /proc /dev /run to be more restrictive

Unfortunately it only appears to remount, which will not persist across reboots (unless I’m missing something).

> Restrict access to compilers

Is this actually meaningful from a security perspective? If one can get some source onto a machine and execute a compiler and then execute that binary, how is that substantially different than them just getting a binary onto the machine and executing that instead?
If vendors are selling hardware with early iOS decrypted on them, you can bet the Communist Party of China has access to these and has likely already found more than on 0-day exploit on there they're using against dissenters.

So while Apple battles the FBI in courts in the US, they have known (And likely the FBI and DOJ have too) that the most highly guarded corporate secrets they possess, iOS source code, has been compromised by bad actors in China.

This is much bigger than anything in the news at present since the ramifications for global affairs, supply chains, and Apple as a company continuing to manufacture in China are profound.
Ask. How do you search for topics in HN
Gnome Geary
> Filter by: all alphabets

Those are letters, not alphabets.
Most of the time I order delivery, I'm not trying to support my favorite places or really any places at all. I just want some noodles, and I'm entirely insensitive to where they come from. The restaurant industry has no intrinsic moral right to make money from my order; it's strange to propose that I should go out of my way to spend more money and waste more time just for the sake of some random owner's bottom line.

When I'm trying to support my favorite restaurants, the ones I do care about for their own sake, I of course go pick the food up myself. I think most people do the same.
OK, time estimate is fine. But it should be same for any kind of food.
Direct link to video: https://m.youtube.com/watch?v=H6Ma0SVjMHA
Interestingly enough, this was the raison d'être of the Rust project at the beginning, while zero-cost abstraction and memory-safety without GC (and the borrow-checker) weren't part if the initial goal. When Rust was first released as a research project it had green threads and a GC (interestingly close to Go actually), but it was already designed with data-race freedom in mind.
Boeing has Hilton Garden Inns hotels right at Everett field where the wide-bodies are made, and in Renton where the 737s are made. They're a sight to see because they seem very very out of place. But they do a steady trade in Boeing attendees coming in for training, as well as customers coming to negotiate, inspect, and pickup new planes. I got to play a private party in the Everett one, to celebrate a new plane delivery for a customer. The staff told they once had a super-rich Emir book out a whole floor and stay there for a few days while a private jumbo was being delivered. The idea of that happening at a garden inn amuses me.
> I'd pay 50$ for that.

That’s the other problem. The thing you just described is worth 6-figures when sold as a consulting deal. Why do you expect to pay just $50 for the book version?
I posted elsewhere[0] in this thread about my employer's successful practice of replacing shared spreadsheets with web applications.

Here is another option that we use instead of CSV import.

Our applications support custom reports and custom fields.

Users can define new reports and run them on demand.

They can also define custom field types with validation, data entry support, etc.

This combination provides some of the extensibility of Excel while retaining the advantages of an application.

Edited for wording changes.

[0] https://news.ycombinator.com/item?id=23292374
Tesla owner stops carjacking, thanks to connected Model 3 and dumb thief
I'd love to see an article on how to create psychological safety in the first place where non exists or where the opposite is true.

From there all sorts of good habits can take root but without that things like feedback week can become bitterly political events.

I suspect creating psychological safety boils down to things like the rewards and incentive system, org structure and transparency of decision making but I'd love to hear if anyone has first hand experience
> the 'official' dell dock

Do you use Linux? One of the reasons why I chose a thinkpad is having a docking station that reliably works on linux. Any past experience with thinkpad docks? How do they compare?
The first design constraint with so much python development is the battle to stay single threaded. As you point out, debugging concurrent python code is horrendous.
These days they sell location data to other companies. Map names, location based user advertising, and everything in between. Check out their website, it’s insane the amount of data they collect and have.
> My question isn't whether you can test enough to catch all bugs. My question is whether time spent wrangling types gets you more value than time spent writing tests.

Yes, by a tremendous amount, in my experience.

> Are they? How so?

Tests are only as good as the person writing them. I could see a model working where the person that wrote the code isn't the person that writes the test, but that's definitely not how most development orgs work. If a dev is good enough/capable of writing comprehensive enough tests to accurately test the correctness of their code, that's great, but almost none are (I say almost because I actually mean "actually none" but am leaving room for my own error). If you're an average dev, you'll write average tests (neither of these are insults), but that means you still won't catch everything (by a lot).

I think another comment of yours on my posts actually summarizes the core disconnect between your thinking and mine.

> But in the vast majority of modern software, it mostly just matters that you catch and fix bugs quickly--whether you catch those bugs at compile time or runtime is usually not as critical.

I couldn't possibly disagree more with this statement.
Job Market: companies that are hiring/frozen/layoffs
This reminds me a bit of http://www.taco.com which is delightfully 1996 vintage design. I wonder how much money they've been offered to sell or lease the domain for something like ubereats/doordash Mexican food delivery.
Yes, are you aware of what their managers make?
> High functioning teams start with high functioning individuals.

There's a spectrum between a team with no high functioning individuals and one with all high functioning.

In my experience, only 1-3 people in the team need to be "high functioning". Also in my experience, if the whole team is high functioning, then the chances of dysfunction go up significantly.

In my career, I've been in a bunch of teams that were full of high functioning folks. And not one of those teams acted as a team. The management almost always graded you based on your individual achievements and not on how you helped the team. As a result, every one of those teams had instances of individuals doing brilliant things that hurt the team effort, but would get rewarded for it. Everyone of those teams had the majority of team members working against each other to get their idea to the fore, due to the reward structures.

In every one of those teams, when something went wrong, the focus was on finding out which individual(s) were responsible.

I don't believe that what I saw will always be the case, but the correlation is high and I think it is the natural state unless actively guarded against. In other teams where not everyone is high functioning, the focus on working as a team was much greater, and much more successful. It wasn't "Who is responsible for snafu X?", but "How did we allow snafu X to occur?"

But of course, a team with no high functioning individuals will be mediocre.
> psychological safety is a pre-requisite for a retrospective to be useful

The first heading in the article is "High Psychological Safety". I didn't see any claims of directional causality.

> It's like winning the lottery and then writing about how you chose to spend the money as if that is going to help other people win the lottery.

She notes that she's also worked in non-lottery conditions.

A big part of discussing these experiences is to show that they can exist and that when they do, there are a number of beneficial outcomes for folks who are involved. I've worked at the same company she's writing about and my experiences gel with hers.

The lottery-winning incident was being hired. After that it was all due to sustained, deliberate efforts by many individuals over a long time frame. Investing time and effort into being a safer, kinder, more humane workplace isn't buying a lottery ticket. It's investing time and effort. You divert some of today's time and effort to make it happen.
Wow nice! This will be useful both for expert users who can go through and learn about various security options and apply manually, but also useful for non-expert users who can just run the script.
Check out https://trends.co/

They release their research on upcoming trends. Some articles are awesome and lots of people seem to start side projects based on it. In addition, the community and FB group are solid. You can meet lots of makers if you have questions about a specific industry.
This is awesome.
Do you have a website with a list of features?
Does it support outlook and chime?
Psychological safety is 10% job security and 90% how comfortable you feel with the people you work with. Simple to understand, hard to make happen - you need to hire well.
Nope, that'll eat precious NAND blocks on that SSD, eke out that endurance by putting your temp folders in a ramdisk if you can spare the memory.
I've been moving domains from Namecheap to Porkbun due to ever increasing renewal prices, it's something like $5 cheaper per domain with Porkbun. I didn't see the 15x increase you saw though.
I'm currently enjoying a front row seat of the destruction of a High-Functioning team I managed to build over the last year.

I'd fascinating in a sad way how fast the wrong manager can destroy a software team.

And it's all about High Psychological Safety.
Werewolf: A parlour game became a tech phenomenon
Will do, thank you. At this point I just set it aside because there's no real way for me to answer the question and there seems to be even less that it will do to drive my decisions, but it's still there.
Average here is € 59 814 / year
> Is the Dell as serviceable as a thinkpad? Easy disassembly?

You can check it for yourself, every Dell model has the full repair instructions posted somewhere on the Dell site (go to the Support page, select the model, and open the manuals tab). For instance, https://topics-cdn.dell.com/pdf/latitude-13-7390-laptop_owne... is the one for the Dell Latitude 7390. I always check these guides before buying a laptop, to make sure I'm not getting something like non-replaceable RAM.
Black List – Most popular not-yet-produced Movies
Right, so you're working in a very particular style of application. The style of programming you're using doesn't work for most software and dodges the source of some memory safety issues.

Presuming that this style works equally well for all software seems presumptuous and perhaps naive, does it not?
Quora makes data available to Socialgist
a simple search engine in 200 lines - https://gist.github.com/selimslab/7d63349e4e247fbcf7ff9dd01c...

a simple blockchain in 100 lines - https://gist.github.com/selimslab/4ea8e87792dec4e23ecedfd435...
No, that sounds like leadership. Being a brilliant jerk, to my mind, is making thoughtless changes constantly and rapidly.

There are times when you have no choice but to be disruptive. The trick, as I see it, is to only be as disruptive that you need Be and no more. And when you are disruptive, be prepared for breakage that needs to be repaired, and be ready to communicate - extensively.

Also: you had better not be wrong in your disruption.
> SELECT most_common_vals

> FROM pg_stats

> WHERE tablename = 'json_test'

> AND attname = 'json_column';

> {"{\"name\": \"john\"}"}

Hmm. Looks like it does though. Not that it makes a damn bit of difference because if you haven't got a functional index (i.e the stats are next to useless) then you're doing a full table scan, and in that case it sounds like you “expect full table scans to always be fast” :)

And sure, the statistics don't help with the query planner, unless you've got a computed column, but again see "I expect full table scans to always be fast" and re-consider the statement "postgres doesn't keep statistics on json columns" given the fact that it actually does, just like any other column.

Read up indeed!
Why do you say that?

I believe concurrent.futures is meant as a way for asyncio to spawn threads or processes -- which lets you essentially call sync code from async and not have it block the event loop.

From the docs[1] -

The concurrent.futures module provides a high-level interface for asynchronously executing callables.

The asynchronous execution can be performed with threads, using ThreadPoolExecutor, or separate processes, using ProcessPoolExecutor. Both implement the same interface, which is defined by the abstract Executor class.

[1] https://docs.python.org/3.8/library/concurrent.futures.html
This is the guy who created the Black List: https://en.wikipedia.org/wiki/Franklin_Leonard
And yet, lots of software developers do quit and spend a few months off, and then go work somewhere else. Because managers do threaten and bully employees. This is considered 'normal' for the field. One running joke in my circles is that developers never 'take vacation'. They simply wait a few months between jobs, because they're never at one job for more than a year or two.

The other way to look at this is: companies pay programmers ridiculous salaries because the working conditions are so hated. Junior programmers (even those who have never been to college) are paid about as well as dentists, and they still often quit after a couple years. This is way above the $75K happiness threshold. We literally can't pay them enough to stay working for us!

Hypothesis: software development is one of the few industries that I've interacted with where the workers haven't organized yet. When there's no union for collective bargaining, what lever does an individual employee have, other than asking for yet more money, or quitting?

P.S., In what industries do you commonly see managers threatening or bullying workers? I haven't seen that at all.
How did you find out, eventually? That sounds like it might've been a very awkward moment...
More and more... the idea of packing a hardrive with a back up of my files plus a copy of wikipedia together with a Raspberry Pi in tin foil, inside a galvanised steel bin... is sounding less crazy :D
You would have to be resizing a tremendous amount of images to overwhelm a $2k server.
The mysterious infix – Wenzel P. P. Peppmeyer
The reason I avoided synology in the past was due to the lack of an ability to automatically detect and repair data corruption. It seems nowadays that their systems with BTRFS can automatically repair data corruption with the checksum. (https://blog.synology.com/how-data-scrubbing-protects-agains...)

Does anyone have any experience with this? Has it correctly caught data corruption for you? How does it compare to scrubbing on ZFS?