skysight-inc/HackerNews huggingface dataset:
An engineer at Coralogix, a full-stack observability platform, recently shared an intriguing solution to translating SQL expressions with null semantics into OpenSearch DSL. This challenge arose while building the DataPrime query language and engine, which needed to maintain backwards compatibility with OpenSearch.

Key points:

The engineer confronted the disparity between SQL's three-valued logic (TRUE, FALSE, NULL) and OpenSearch DSL's binary filter system.

They devised a method to reduce three-valued logic to two-valued logic by considering the context of expressions, such as WHERE clauses.

The solution introduces is_false_or_null() and is_true_or_null() functions to bridge SQL and OpenSearch DSL.
Boolean operators are handled by analyzing truth tables and deriving corresponding OpenSearch DSL translations.
This approach enables the translation of complex SQL expressions to OpenSearch DSL while maintaining correct null semantics.
The team implemented additional optimizations on the intermediate representation to enhance query efficiency.

This solution allows Coralogix users to seamlessly query both Parquet files and OpenSearch using a unified query language. The article offers valuable insights for developers working on query engines or database compatibility layers, demonstrating a creative approach to a common challenge in data querying and observability platforms.
"more than one middle name" :)
From the article:

For now, you can still view Google’s cache by typing “cache:” before the URL, but that’s on its way out too.
They don’t, but California essentially dictates them because nobody wants to cut themselves out of the richest state’s car sales
My homestate [Texas] does not require federal/state agencies to follow local building codes.

My new state [Tennessee] just ended government construction inspections.

Pay - to - play, folks.
> HN won't probably like the tone of this one. But one thing I want to emphasize from the post: you don't need to be innovative

I don't know anything about founding nor am I interested about it, but at least it was funny. On some other topic, I've found this kind of post to be refreshing and relieving, even if your inner voice says "yes, but...". It is kind of popping a couple of the nested bubbles you're in when you are deep in a project.

This line about innovation reminds me what one of the (founding) member of a band says in a masterclass session [1]: the music you make doesn't have to be entirely new all the time. They show an example with one of their own song and compare it to another famous one: "That's the same thing".

[1] https://www.youtube.com/watch?v=rwpXTeKhWYs
This sucks. Cache basically guaranteed that whatever Google thought was on the page could actually be found.

These days Google will offer a result where the little blurb (which is actually a truncated mini cache) shows a part of the information I'm looking for, but the page itself does not. Removing cache means the data is just within reach, but you can't get to it anymore.

Internet Archive is a hassle and not as reliable as an actual copy of the page where the blurb was extracted from.
It lists languages designed by commercial companies too.

The main reason it avoids showing languages created by individuals is that it can be hard to narrow down their location. Also, it would count as doxing.
I call that rich
OP,

You can start by reading this post:

https://news.ycombinator.com/item?id=41545495
Why are people surprised when two heavily sanctioned nations start colluding?
Speaker directionality gets interesting once you get to arrangements for festivals and concerts. Ideally the audience should all be able to hear well, which is difficult to achieve over such a large area and with multiple sources.

But you also don't want the neighbours to complain about the thumping bass. A number of subwoofers pointing backwards, with the right phase delay, destructively interferes with the most offensive frequencies and reduces the sound intensity behind the stage. It's called a 'cardiod' arrangement, because of the shape of the resulting sound intensity distribution.
I would say all software is chaining APIs together.
What??? Oh no. I love that feature so much. What should I use in the future then? IA can be a solution but often the link I am interested in is not there. For example, foreign news from developing country.
I wonder how many people understand your username (I my case, having a Hungarian friend helped).
OK I bought some water resistant bone conduction earphones
Yeah that. We just do what everyone else does in our sector. And do a 20% less shit job for 20% less money. And that not a hard bar to meet when everyone else’s products are dire and incredibly overpriced.
> The world unfortunately is lot more diverse than that.

It is, but only at the surface level.

99% of the actual problem of driving in urban areas is the same everywhere on the planet, because all human cities are pretty much the same, because all humans are pretty much the same - once you start comparing with the rest of the universe, and not just with other people. San Francisco, Moscow, Cape Town and Prague are almost entirely unlike each other, yet they're all obviously the same when you compare them against ant hills or forests or coral reefs.

Self-driving is a physical reality problem, not social diversity perception problem.
It's incredible realizing that I have two decades of work experience, and have peers that have been "in the field" for less than a few years!

To each his own. I think higher education in America is primarily designed to degrate and beat students into submission.

As I've heard repeated elsewhere, the road to tenured PhD is paved with grad-student bodies.
You are not the smartest person in the world. You are lucky if you get one thing better than everyone else, but you never know everything better than everyone else. So sorry, but fuck hubris and I'm going to follow the best practices whenever I don't know a specific reason why I can do better.
The solution to this is to code your own things for fun.
This looks pretty nice, seems you’ve put alot of work into this. A suggestion, if you haven’t already the following things could really help for software development tesms:

* Ability to connect issues with branches on github/bitbucket etc. (so you easily see, and quickly navigate to, related code submissions). We mostly use JIRA and this is a crucial feature for our project management.

* Ability to set a category/group for your tasks, and in these categories specify additional fields (just simple text/drop-down/radio button fields). Projects often have individual needs, and cluttered forms is a nightmare.

* Time tracking on issues.

* Parent issues which tracks the collective time spent on child tasks, to get an overview of time spent on pieces of a project.

If you can make a simple enough interface I think this product may be viable, even if the market is a bit saturated. JIRA for instance has a horrible interface, even making minor changes is a dreadful experience. Almost cost me a keyboard and screen last time I had to modify what fields should be available for a particular project.
The Hard Thing About Hard Things - Ben Horowitz

This is probably one of the best

Shoe Dog - Phil Knight.
A great read about the struggles of how Nike started. But was left unsatisfied as the book ends with the company going public but doesnt cover its ascension in the late 80s/90s and how that went down.
I think the point is to avoid pointless hard work.
I remember finding this funny back in the 90s but it’s just kind of sad to me now. Today he just seems like a very unhappy, psychopathic character.
Input:

> Thank you for participating in our hiring rounds. However we regret to inform you that we decided to proceed with other candidates. We hope we stay in touch for future openings.

Output:

> Translation: You didn't get the job. Don't call us, we'll call you (but we won't).

Validated.
THis paper from 1947 sums up the state of the science(and opinion) at the time: https://jamanetwork.com/journals/jama/article-abstract/29572...
Closed-source applications or games, I'd say.
The sprint goal is a team target. If you're sick that shouldn't endanger the sprint goal because anyone in the team can pick up any work. Of course in mediocre or low-performing teams that's almost never the case but still not the fault of a product framework
> Cancer — What We Have Been Thought

Taught, not Thought. Good Lord!
I’ve never really been a fan of the concept of “retirement”. It feels very much like a Silent Generation/ Boomer idea that has run its course (for reasons both good and bad).

I watched grandparents on both sides retire and their mental decline tracked their decline in active engagement with meaningful activity.

The way I have always looked at it is that want to “retire from _having_ to work” and promote myself to working on things that I _want_ to work on.

Having said that, I like your “5, 4, 3, …” approach. I’d just be switching out “have to work” days with “want to work” days.
Perhaps he is thinking of how marriage does not change your last name, but rather gives you an extra, optional last name. [1] The French ID card has two last name fields!

[1] https://fr.m.wikipedia.org/wiki/Nom_d%27usage_en_France
That was never Google's job anyway. It boggles my mind how there is very little public investment in maintaining information, while tons of money is being wasted keeping ancilarry things alive that nobody uses. We should have multiple publicly-funded internet archives, and public communication infrastructure fallback, like email.
holy hyperboly, clearly i picked the right example...
This guy has clearly never worked waterfall, the progress bar doesn't look at all like in the graph. Instead, there are even more milestones throughout the project. Granted, they are usually spread out further than every 2 weeks, there is no such thing as just one final deadline where you can slack the first half of the project.

Month 1: Specifications need to be frozen, because month 2 all the test plans need to written, so that month 3 all the test cases can be implemented. Then month 4 all code should be written and month 5 we put everything together to test it. Hoping that what you wrote down half a year ago is still relevant and the most important thing to work at now. Add a complex web of dependencies to other teams on a gigantic gantt-chart with fixed dates and you will have deliveries regularly anyway.

Usually, by month 2 you are already overdue on the first milestone. The time plan is not going to shift because of it. Meaning you now have even less time to meet the second deadline, obviously it will be missed, repeat throughout the remaining milestones, resulting in constant stress throughout the project.

That's not to say that the graph doesn't exist, its just not called waterfall. It's longer deadlines with more autonomy between.
The leader needs to have both vision and an understanding of the job separation you described.

Many don't, in my opinion.
TBH this is why I'm partial to Microsoft Recall or something similar, because inevitably it's going to get monetized to address link rot... and private data. Too bad there isn't a P2P option where you can "request" screenshots of cached webpages from other people's archives. Maybe it's all embedded in LLM training data sets and will be made public one day.
Its slightly more strange than this as both are true. It's already baked in the model but chain of thought does improve reasoning, you only have to look at maths problems. A short guess would be wrong but it would get it correct if asked to break it down and reason (harder to see nowadays as it has access to calculators).
> Sometimes musicians use dispersing devices mounted on the speakers, like "beam blockers".

Beam blockers seem to be the most common thing employed, though to my knowledge a much more effective measure is a "Mitchell donut". Basically, a soft foam disc with a soup can diameter hole cut in the center. The disc is sized to completely obstruct the speaker when mounted in front of it on the grill(cloth). With properly chosen foam of the right thickness, frequencies above about 1khz will be attenuated except when traveling through the center hole, meaning they'll behave more like they're coming from a point source and the constructive interference that causes the beam will be much reduced. Equalization may need adjusting since some highs are lost, and because if the player adjusted initially for on-axis sound they are now hearing the off-axis sound.

From a stroll through the audio cyclopedia, I think "mitchell donuts" are more properly called "acoustic lenses". A key difference between them and most beam blockers I see is that the blockers assume high frequencies come from the center of the speaker (cause that's where the beam is, and when close micing that's usually where you get the most treble), whereas donuts/lenses assume the entire speaker emits the highs, and that it is their constructive interference that causes both the beam and the trebliness of close micing a speaker on axis. I have not fully verified all the physics yet, but so far my understanding is that this later explanation is correct, at least in the context of guitar frequency ranges.

The consequence of that is that beam blockers usually/likely add a comb filtering effect from what I've read, and will still develop some beaminess in the far field despite removing it in the near field. The donuts/lenses should be effective in both the near and far fields. Anecdotally, my experience confirms the donut behavior. A previously painful-on-axis 4x12 was almost completely evened out by the addition of donuts.

If anyone has good pointers for honest to goodness physics books on speaker drivers and speaker cabinets, it would be much appreciated.
I happened to be reading an article by JD Vance so I pasted in a random paragraph:

> Yet there is more to glean from our government’s efforts to help Appalachia than a renewed skepticism of government aid. We’ve learned, painfully, that for the multigenerational poor, home might be the worst enemy. Appalachian loyalty to the land is the stuff of legend, yet the stubbornness of poverty in the region means that those who stay risk being poor forever. When the government paved thousands of miles of roads in Appalachia, it hoped to provide employment for the masses and infrastructure to sustain future economic growth. But the best and most lasting effect of those roads was to give people a faster way out. If we cannot improve the urban ghetto or the mountain hollow — and the evidence suggests we can’t — then the best anti-poverty program is a ticket to somewhere else.

The tool did really well at not sounding like ChatGPT!

> Turns out the government's "help" for Appalachia mostly taught us that staying put keeps you poor. Those famous mountain folks love their land, but clinging to it means eternal poverty. The fancy new roads they built? Great for getting the hell out of dodge. Can't fix ghettos or hollers? Here's a novel idea: move somewhere else.
> People whose first book was Hitchhiker followed the trajectory of reading the same book hundreds of times

I have never met anyone meeting that description. Back in my day, nerdy pursuits were not very tribal. A franchise did not form someone's identity mostly because there wasn't enough content about it to devote oneself to. You watched a movie, read a book or whatever and liked it. A superfan would be someone who sought out a game or a graphic novel but it gives you only a few extra hours in the world at most. A fan club would be a yearly magazine or something. You had to find other things to entertain you.

My friends were pretty core Hitchhiker generation with very similar background/humour to DNA. It was a pretty common early book. We might have reread it, played the infernal video game, loved the radio show, and could recite the famous bits but there really wasn't anything you could fall into some solipsistic hole about. There isn't enough there. It would be something to obliquely reference as an in-joke but wasn't something that could even sustain a conversation other than complaining about that game.

Hitchhiker fans were also likely Python fans, Tolkien fans, Pratchett fans, Harry Harrison, Asimov, Arthur C. Clarke, graphic novels, Red Dwarf, Warhammer or like DNA, very much into the birth of the home computer which really was a bottomless pit of discovery and conversation.
A backup system which can be ran on hydrogen or e-fuels when the time comes to tick off the final hard problems.

https://reneweconomy.com.au/a-near-100-per-cent-renewable-gr...
It's sad to think about how little of our resources are dedicated to work like this. Although I enjoyed the Marvel movies growing up, it would be nice if similar funding could be found for a project like the author describes (and, of course, you could have a sort of documentary showing people what they discovered).
I have had consequences for not cranking out work fast enough. Usually PIP or PIP-larping processes are run. I then resign find another gig.
Love the project, too bad it didn't get more votes
Fixing the headline...

One in five genetics papers have errors caused by mistakes in the use of Excel

As if longhand calculations never have errors?
It is very intellectually boring to have the view that the only things which are possible is what we have already done.

Meaning, with your own logic the French nuclear buildout was impossible since no one had done it before.

It was possible. Just like renewables are today.
Pakistan has had nukes for decades now, and would wipe India off the face of the map if they could. Ask yourself why they don't, and vice versa, and look at the middle east. I don't relish Iran having nukes but it would be a mistake to assume the winning move now is first strike while we can. A reality of my childhood was MAD and we have been complacent about it for far too long. Welcome back to the 1950s and 1960s.

Quite why Iran helps a nation state which willingly slaughters their co-religionists is beyond me.
I can't believe how well this works. Brilliant stuff.
Getting Real, 37signals
> If those students/graduates move to other European countries (which they mostly do), they'll be counted in their destination country, evening things out

If they move to the Netherlands, the NL will only count what % of its citizens have degrees, not everyone else (because many may go back or move elsewhere after finishing their studies, you can't count them easily alongside the rest of your population; students are usually counted as some sort of temporary resident, if counted at all). And then there's also the UK which is a top study destination for Eastern Europeans.

> Where did you get the idea most Europeans get a degree

I come from one EU country, live in another, have friends from all over the EU, have visited as a student and now working adult. Most young people pursue degrees, even in forestry or tourism or whatever topic. Of course some will fail getting them, but 30% of under 30s is absurdly low for stats to be reliable.
That similarity is superficial. It is observing that no ideology perfectly survives implementation - which is true, but there is no alternative option so it isn't a useful observation.

We don't have any successful countries that use communist ideologies because central planning is destructive and the abolishment of private property is catastrophic. Calling for communism is tantamount to wishing for death and destruction. The path to success through communism is something like China where they eventually learned to do the opposite of communism and got great results.

We do have lots of successful companies using Scrum. They hire Scrum masters. They see Scrum as adding value. The scrum ideal is generally a bit of a compass towards higher value add. So scrum as an ideology seems to be net-successful even if implemented wrong.
You are telling me that we do not have a way to clean build human from DNA source. That's a real continuity risk.
I wonder how this even works, as PID 1 should exit right away, no? And I thought this would lead to an immediate kernel panic?
Nuclear power plants still can’t insure themselves on the public markets.

When the need for the insurance subsidy is removed then we can talk about it being as safe.

https://en.wikipedia.org/wiki/Price%E2%80%93Anderson_Nuclear...
A Look at the New Prometheus 3.0 UI
Good reminder to say "no" more often.
There isn't much relearning needed since errors like the one described in the article illustrate that people don't know much about this tool either

And Sheets isn't "really better", yet gained a noticeable share
This reads as if The Dude Lebowski was a software engineer. And that's immensely refreshing, almost as entertaining as Mataroa's blog posts (https://news.ycombinator.com/item?id=40725329).

In line with other commenters, I think the biggest value of the post resides in remembering folks to think critically and not going full cargo cult.
Right, and my point was that you had someone to be accountable to on a regular basis, so it helped keep you motivated and on track to produce results to report.
The difference here is that the excel errors are systematic so should be more easily avoidable, whereas long hand calcs are more varied and harder to correct.
> it’s difficult to look at people like Graham — people who aren’t as bright as they think they are

Graham’s (alleged) arrogance about his brightness isn’t really the issue here. Let’s face it, he is bright. That’s not what is causing this boredom/dismay, though.

The issue is that somehow the rest of us became entranced by the “cult of Graham” and his thinking about startups/founders, and collectively we made his way into the way, ostracizing those that lived their life outside the idealized startup paradigm that Graham crafted. Creation of this dismay isn’t on him alone, it’s on all of us.
“Hand waving” we can store it easily for millennia.

The US was founded ~250 years ago as a perspective.
Another reason why we should only allow Canadian nationals to own real estate in Canada.
I learned scrum back in college and I hated it so much. I remember we had to meet 2-3 times a weak. And for each meeting we had to present something, with slides as well. We spend more time thinking about usercase than writing the code. I guess that's good in its own way but honestly I don't have such superpower to report something new every meeting. In fact most of my meeting back then were "I am still coding X" and that was it, then the scrum master or the leader would talk about big picture over again.
> Being able to easily reference existing edges and faces for future operations

God, yes. Allegedly the BOSL library has some support for this kind of thing but I've not got around to trying it yet.
Input

> The latest maintenance release Git v2.46.1 is now available at the
usual places. Unlike maintenance releases in the recent past, this
one is _not_ about security fixes, but primarily about fixes to
various commands that can work outside a repository barfing due to
lack of initialization of the hash function. IOW, it is not the end
of the world if you did not update to this version for a few weeks,
or wait for 2.47 ;-).

Output

> Git 2.46.1 is out. No security fixes this time, just some tweaks to stop commands from puking when used outside a repo. No rush to update - you're not gonna die if you wait for 2.47.
Okay, I am telling you to use Flax.

Its high level API is quite similar to that of PyTorch. So, you will feel right at home.