skysight-inc/HackerNews huggingface dataset:
Just a quick glance at Letterboxd....

Banshees of Inisherin

Everything Everywhere All At Once

Both Knives Out movies

Parasite

Nope (probably just in the "good" grouping, not great)

-----

That's, uh... just from the "popular this week" screen. And only the ones I've seen, so I know they're good. But I'm pretty sure all those are last five years, or close to it.

-----

Digging back to 2018 and later (we can say 2018 counts since 2023 just started, right?):

Annihilation

Sorry to Bother You

High Life

Midsommar

Uncut Gems (god it's so good)

Jojo Rabbit

The Lighthouse

The Green Knight

CODA

Spontaneous ([EDIT] It seems very dumb but wow is it a gut punch, when you start to think about what you're watching and make some connections to real life)

Red Rocket (small-scale brilliance)

RRR

Watcher

-----

I just realized I misread you as asking for 5 good ones from just one of the last 5 years, not 5 total from the last 5 years, but I think that gets the point across? Despite my leaving off a whole bunch that may be more taste-specific, not having watched even 1/3 of the films from that span I have good reason to believe are good, not exhaustively mining that timespan (I bet I could double the size of that list without changing how I was selecting them), and also omitting a bunch of more-popular movies that I think were at least decent.

[EDIT] Hell some years you could get to 2-3 good ones just by looking at what A24 produced that year, nothing else.
Solo ic on a small project, you don't write tests? That's the easiest time to write tests! You don't have all the complicated context set up or writing test data, and saves you the run/debug loop for setting up specific situations.

My childhood not knowing about tests had a ton of wasted time trying to check that a change worked
Why build and maintain the entirety of the infrastructure for a national transport system: payment, timetables, rails, signalling etc. and then hand the very last bit - the only bit that actually generates revenue - to a private company?

It's just another example of the hubris of the Conservative party. We've seen it play out repeatedly over the last decade and even earlier in Thatcher's neoliberalism. Labour's lurch to the right resulted in displays of similar small minded arrogance. Their undermining of the NHS through piecemeal privatisation is nothing short of a crime.
It's relevant for two reasons.

First, lay people presented with competing expert arguments are generally reliable. Not universally, of course, but often enough that it's probative. It is useful to get a "gut check" from someone who isn't close to an issue, the comparative increase in objectivity outweighs the comparative loss in expertise.

Second, regardless of the abstract question of any particular hypothesis, the credibility of the scientific field in the eyes of the citizenry is important. Even if a scientist knew with certainty that the lab leak hypothesis were false, wasting credibility on that position without compelling evidence would be "damaging to science," in the sense that it decreases the influence of experts and, likely, their funding.

TL;DR: It's important because, when choosing a hill to die on, you have to account for the strength of your evidence and whether people are inclined to believe you. The opinion polls are relevant to the latter question.
Sure. You can't go halfway on monorepos where you check in all the code into one spot but don't build any tooling to manage that. You need to use something like Bazel/Blaze, Buck, or other tools that meant to own responsibility for managing dependencies between projects.

> Well, there aren't "subrepos" … it's all one giant monorepo.

I think op meant organizationally you still have logical components.

> And … no? No, CI tools don't. There's generally not a tool that has the dependency graph, and it's typically not recorded. (Excepting bazel, which set out to solve this problem; lo and behold it was designed by a company with a monorepo, too.)

Everywhere I've worked that has had a monorepo (Google, Facebook), that's definitely the case. The CI automation would query Buck/Bazel to figure out the set of dependencies impacted by a PR. Of course, some PRs would have outsized impacts (e.g. changing libc) but at the same time, there's probably not much better than that.

Apple was a bit different. While nominally each project had it's own git repository, you uploaded code to a central monorepo that organized everything by release. And it built every project incrementally and relinked/rebuilt whichever projects were impacted. They didn't at the time have a centralized CI system. But also Apple's system evolved from many decades ago and is a sane selection for building an OS from back then. Google's approach I think is generally accepted as a more effective strategy in some ways if you're going down that route. That being said, at Google scale you're shipping so much code there's still challenges. For example, there's so much code being changed at Google's scale, that they have to bundle things together into a single CI pass because there's just insufficient compute capacity available to do everything + avoid serialization of unrelated components. Of course, probabilistically there's a non zero chance that something is broken and they intelligently bisect and figure out what change needs to be omitted from the ship. Very complicated. But I think most people underappreciate that they'll never encounter these kinds of problems. If you just go all in on monorepo + Bazel + bazel-aware CI setup + build artifact caching, you're done and don't have to think about builds or code management very much after that. That's a really big superpower.
influenzation
> I don't see any meaningful distinction with how well thought out workflows need to be between mono and polyrepo.

You completely failed to parse the sentence. The point being made isn't "well thought workflows are only for monorepos", that applies to the "needing clever application specific tooling" part.

Vendoring/Versioning for discrete packages is a heavily invested in problem space for most tech stacks you'll come across. But if you build a monorepo and don't end up with a build system that takes on those responsibilities you end something that doesn't scale to even moderately large interconnected components.

OP has such a tiny project that I'm not convinced they're even dealing with dependencies in a traditional sense. But well before you get to Google scale, you'll run into situations where you just want to change one thing and don't want to change every single downstream dependency which normally would have been isolated via a discrete package that doesn't have to change in lockstep. And then that exact same pain starts to exist for deployments and needs to be worked around.

> I feel like this was true ~5 years ago, but these days the tooling around scaling monorepos is safely supporting O(100) developers without a lot of overhead.

Nothing about the above has changed in the last 5 years, it's kind of the ground truth of monorepos via multiple repos: You're the first person I've ever seen imply monorepos don't offload complexity to tooling, even amongst proponents.
The house remains privileged again, I see.
Can permanent magnets theoretically realize perpetual motion machines?
RISC changed everything just like CISC did. It was a product of changing times & tradeoffs.

Both RISC and CISC are effectively marginalized, though. The current trend for everything beyond embedded is somewhere kinda in the middle. With the some pretty pointless nitpicking about if something is or isn't RISC and devolving that entire movement down to just "but it doesn't do memory indexing!" or whatever.

It turns out what makes a fast processor is something that uses both RISC and CISC ideas. And that's what nearly everything does these days as a result, because speed is all that matters
What is spacetime expanding into?
It would collapse all of the society…if that were true.

But it’s not. The fed is regularly audited in the usual sense by independent third parties.

https://oig.federalreserve.gov/reports/board-financial-state....

Additionally, every security owned by the Fed, up to the detail of the identifying CUSIP number, is also available online.

https://www.newyorkfed.org/markets/soma-holdings
Bill Gates Doesn’t Think Web3 Is a Big Deal
I would love for something like this to exist in Canada. Unfortunately import fees make these much less attractive here.
> The idea of the Apache as a singular, extinct tribe, one that put up a notable fight in the face of a conquering aggressor, is at the core of Natives in Tech's grievance.

It's a bit bizzare to be upset at the logic used to come up with the name, rather than be upset at the name being used.

It would have been fine if the guy naming the product had been less ignorant of history, or just hadn't written the logic down?
Most of the time I don't need automatic mappers, but it's nice to have good, fast tools available.

When I'm building something in a more domain-driven approach, which I usually strive for, tools for domain model<->dto mapping (assuming the separation between application and domain layers) does not make much sense. Because even when I have a domain model/dto pair with almost the same attributes I will be creating the model via a well named factory method in the domain layer, with notification style validation. And for changes, even for HTTP PUT, specially for HTTP PATCH, I'll be updating a subset of the attributes and for that I'll be using proper entity methods with, again, notification style validation. On both cases manual handling is the way to go.

If you're mapping lots of open fields to your domain models... it's not domain driven. Might be a choice, but should be conscious.

And if a) automatic mapping makes sense for a subset of the application, be it for api dtos or internal matters (you might be dealing with dtos internally for some integrations), and b) we'll really will have a one liner (including a one liner config) instead of mapping N attributes in multiple situations, ok, but I'll consider to define some sort of simpler Mapper interface and put the tool behind it without leaking its details for application and domain layers.
> Cool, so we've established that I'm saying the tech stack matters.

Yes, and I'm telling you that all the problems you've raised are not dependent on your tech stack.

To make it clearer, it doesn't matter if you use CloudWatch Metrics or if you publish your metrics manually in an Excel file, as long as you have metrics being looked at.

"Having metrics" is not a part of your technical stack.

Similarly for speed, it doesn't matter if you use C or Python, as long as you write efficient algorithms and choose the right datastructure.

"Writing efficient algorithms and choosing the right datastructure" is not a part of your technical stack.
Unless of course your product is the stack
A unit test can succeed while being completely wrong.

Eg. You test code that calls a dependency that returns a bool, but your tests assume an object response

Unit tests imply assumptions about the integrations, whereas types specify those asumptions
I suspect you are right Sean - and I know you are a guy who has read a lot of papers and been to plenty of conferences.
Potentially, wouldn't star systems have planets where their orbital planes are at positions that we cannot observe transit event from? In fact, most planets?
Does anyone have access such that they can put things on archive? Bloomberg put all the details behind their paywall.

Here's the actual patent, unpaywalled:

https://patents.google.com/patent/US10945648B2/en

Claim 1 (as claim language goes, this isn't too bad):

1. A user-worn device configured to non-invasively determine measurements of physiological parameter of a user, the user-worn device comprising:

a plurality of light emitting diodes (LEDs);

four photodiodes configured to receive light emitted by the LEDs, the four photodiodes being arranged to capture light at different quadrants of tissue of a user;

a protrusion comprising a convex surface and a plurality of openings extending through the protrusion, the openings arranged over the photodiodes and configured to allow light to pass through the protrusion to the photodiodes;

and
one or more processors configured to receive one or more signals from at least one of the photodiodes and determine measurements of oxygen saturation of the user.
That was my first thought too. Engineers are famously bad at people-stuff. Not all engineers, but enough spectacular examples for me to cringe at the headline.
Non-video link:

“The Psyche issues are not unique to Psyche. They are indicative of broader institutional issues,” Young said at an online town hall meeting held by NASA to present the report’s findings.

JPL, he said, has an “unprecedented workload” of projects and the board found the lab’s resources were stretched thin, particularly in key technical expertise. “There is a large imbalance today between the workload and the available resources at JPL,” he said. “This imbalance was clearly a root cause of the Psyche issues and, in our judgement, adversely affects all flight project activity at JPL.”

https://spacenews.com/psyche-review-finds-institutional-prob... (2022)
It's a fine balance.

Software Engineering is a profession that deeply revolves around saving people time.

The tiniest fraction of software engineering involves goals other than "saving humans minutes."

The foundational knowledge of software engineering, mathematics, linking real world problems to discrete mathematical foundations.
Projection of subsets, grouping abstractions, logarithmic graphs.

It's valuable, because it saves time.

Almost the entirety of mathematics was discarded to identify that foundational knowledge.

Keep in mind, human life will always involve juggling multiple different worries at once, & compromising.

It's never a "do this, or do that" situation.
Yeah, I realize we're looking in the past and can't "see" ourselves (probably not even our own galaxy, depending how far out we have to look). But I guess the theory in itself is not any more "weird" or "outlandish" as the idea of an infinite universe.

And maybe if we actually look both ways, we could find another galaxy that could be proven to be the same (because of some particularly remarkable stars/quasars/supernovae etc. in them). Who knows, maybe the universe is smaller than we think and we just don't recognize the "same" galaxies on different images because they are billions of years apart?
Great idea but it violates the mushroom management rule of keeping employees in the dark and dumping on them. Knowledge is power, and power is to be held tightly.

Practices that reduce the social status gap of managers above employees are rarely popular.
The article is entire about the ways that your code and architecture affects the final product. Really, there is no other thing there than the complete opposite of your complaint.
Yep, this is the exact point I tried to make above and got heavily downvoted.

If you can't move fast when things are working well, you can't move fast when things are broken. Acting like moving slow is going to prevent things from ever breaking is just wishful thinking.
Patent law should, but does not allow for independent derivation.

It also fails to do anything about patent thickets.
Was looking forward to discovering the way to reverse the graying of my beard but seems that I have to suscribe first. T_T
The two-wheeled commute: Micromobility and your future
>> dithered images compres poorly

> Piping stuff like 1-bit dithered graphics through fast, lossy JPEG/MPEG-style compressors (i.e. quantized DCT) will yield absolute garbage results.

Of course dithered images compress poorly when using compression algorithms that aren’t designed for them, but I don’t see why, a priori, they should when the choice of compressor is free.

That current compressors for photos are better than those for dithered graphics may only be because there has been way more research in compression of photos than in that of dithered pictures.

You could, for example, try to compress a dithered image not by running a JPEG compressor designed for photographic images, but by searching for (search algorithm TBD) a low quality JPEG file that, when dithered, produces an image that is perceptually similar to the original dithered image.

For photos, I would expect that JPEG file to look better than its dithered version, but if the input is a dithered photo, I’m not sure. Even if it is, such an approach might still be useful. And JPEG likely isn’t the optimal compressed format.

But dithered images is a niche market, so I don’t expect we’ll ever know how good these images can be compressed. Even the demo scene probably won’t work on this. They wouldn’t build a generic compressor, just one that compresses the images in their current demo well.
I have worked at places that have micro-repos, places that have polyrepos, and places that have monorepos. From my observation monorepos are a sign of ossification and resistantce to new patterns and new technologies.
Customers might not, but it's probably effective recruiting.
I refuse to believe Agile is anything but a micromanagement framework.
Ask HN: What programming language best supports modularity?
What programming language would you choose if you wanted to make a modular monolithic architecture?
Apache Foundation faces name opposition from American Indian activists
> back up cameras

I have literally never heard a complaint about reversing cameras in my life
Even if we agree that this is the biggest threat (in fact I think echo chambers are not a problem — as long as the ideas echoing around them match my preferences, haha!), I’m not sure why we’d evaluate these experiment by that metric. Maybe they are trying to solve some other problem.
> PCP ignored escalating PSA levels.

He was ordering psa tests but just ignoring the velocity ?

I had similar discussion on HN last week

https://news.ycombinator.com/item?id=34251569
Here's the WordCat record for it [0], and some seem to have it as an eBook so it could probably be requested via ILL if you have institutional affiliation. From the listings I'd guess said ebooks aren't official and that the book has no official digital copy - hence the 'illicit PDF' part mentioned.

[0] = https://www.worldcat.org/title/12724773
I'm not really making a claim that the average voter is "as good" as an expert when voting. Rather I'm saying it's often not possible to optimize anything in the context of voting, so the degree of someone's expertise in some domain is really not relevant to begin with.
I know it's happened, but I find out about the error before I've run the tests, or I've used the types to guide me to the correct code rather than writing without and then testing to find out if it's correct.

The autocomplete and documentation are about preventing broken software. You just don't think about it like that because it skips the seeing it break part
Contract. They have to pay for the the bank for the wind turbines even if not used. They have to pay the land owners (or the bank for the land, and government taxes). You also need to pay various employees. Thus you don't open a wind farm without some form of contract.

On top of the above you want to make a profit.
This is wrong by an order of magnitude. It was already known thousands of years ago that the Earth is more-or-less spherical. The idea that people in recent history believed in a flat Earth is a myth.[0]

[0] https://en.wikipedia.org/wiki/Myth_of_the_flat_Earth
How does it compare to meilisearch?
It's only bad security if you assume that you own the account. You don't. Your employer is paying for it, and they have full control of it. They can access all messages. They can reassign it to someone else. All of this is by design.
Ads barely even sustain many ad-supported businesses now.
FWIW, the OP of the article is:

> Ben Balter is Chief of Staff for Security and Engineering at GitHub.
That seems like maybe an IQ 110 response, just barely more advanced than mass market media.

An actual 200 IQ explanation seems like it would be more like: "It's an evaporation/condensation cycle," with all the obvious implications left unspoken.
If I could rewrite that sentence, I’d replace “illogical” with “fictional”.

My point is that I have little interest in arguing against the claims in a book or books, written by men, claiming to be the infallible word of whichever god or gods in a discussion about an individual’s bodily autonomy and pursuit of personal well-being. I think it is as irrelevant as invoking any other random work of fiction.

Someone else can have that argument and I’ll eat popcorn, but as a child and survivor of a dogmatic and traumatic religious upbringing that taught me to hate my own sexuality, I have no interest in wasting more energy on it.
Congratulations on both implementing the game through to release and all you have done for the Common Lisp community in the process.
Ruby is still the primary backend language at Shopify. Node is popular amongst partners.
We issue it to ourselves, more or less like CirclesUBI is doing it in Berlin.

They're just letting it be inflationary and setting the payout to increase over time to adjust for inflation. So maybe you get $5 per week this year and $8 per week next year... This can be balanced so that it amounts to a more or less constant purchasing power.

Personally I prefer the demurrage approach where account balances just have a decay rate--that way you've got a better shot at $5 written down today having the same meaning to people who read it next year, but the economics are the same (more on the theory here: http://en.trm.creationmonetaire.info/ ).

It's gotta be decoupled from the government so that, as discussed in my model, it can act as a safety net while you're ridding yourself of wasteful bureaucracy. It doesn't really work if the bureaucrat you're deposing can threaten to take away your UBI.
We've never met and we probably never will, and it's a virtual certainty I'll never see the code of which you speak. But know this... I appreciate it. And I can imagine it. I certainly empathize with your plight. The feeling of a job well done is all the validation you need.
So there are now no longer electrical or magnetic fields?

Sounds tricky.

I would put it to you that this says more about them than anyone else, what the word means or implies to anyone is in the mind of the beholder.
Next: feed the dithered picture into Conway's game of life, then create animation of game played in reverse starting from final generation.
What are the indicators we have marine biology wrong to the level of the other mentions?
This one?

The Death and Resurrection Show by Rogan P. Taylor

https://archive.org/details/deathresurrectio0000tayl/page/n7...
Have you seen Rebelle?

https://www.escapemotions.com/products/rebelle/about
More like "Apple Is Doomed Without Steve Jobs" (not 2011 but you get the picture):

Elon Musk 2012: https://www.businessinsider.com/elon-musk-apple-is-doomed-wi...

Larry Ellison 2013: https://www.latimes.com/business/technology/la-fi-tn-oracle-...

Reaction from Gruber 2013: https://daringfireball.net/2013/02/hammer_nail

or even beforehand:

Gawker 2009: https://www.gawker.com/5251304/why-apple-is-doomed-without-s...

etc.
If someone links a different site source using archive.foo in support of their comment, how would a script know the difference?
Sure, but we do make intentional tradeoffs, at least sometimes.
And then there are the people who sell phone/tablet devices, and child-oriented apps and games through their walled-garden stores — and at the same time have banned the devices for their own children.