MurphyA/hacker-news huggingface dataset:
by hnbad | 2025-06-02 15:33:05+00:00
> “False color” was popular for a while but has fallen out of favor because it implies fakery.

I think that's getting the priorities wrong. The people who think those images are "fake" and fraudulent don't think that because of that term, they just see the term as a reaffirmation of their preexisting conspiracy theories. Flat earthers will literally deny the evidence of their own experiments when they don't align with what they profess to believe.
by OskarS | 2025-06-02 15:33:36+00:00
I think it looks great! Might be using this in a future project.

One note on API design: I think it's a FANTASTIC idea to have default `rand()` functions available, since very often, you don't really care about the generator and you're just like "just give me a random number, i don't care how". But if you do, you shouldn't have a `seed()` function, because that means you can then never upgrade it without breaking your API contract. It should always be seeded with entropy. This is why glibc's `rand()` is still using an LCG from the late neolithic, they can't ever update it without breaking a gazillion applications and tests. This is the classic example of "Hyrum's law". Doing this also helps with thread-safety: you can just make the seed/state thread-local and then it just works.

Basically, if you want the ability to seed your PRNG, you also need to specify the generator explicitly. The global one is for convenience only, and there should be no ability in the API to seed it.

EDIT: btw, this is a really nice thing about C++, doing this is dead easy:

int rand() { thread_local generator my_generator { seed_with_entropy() }; return my_generator.rand(); }
by raigol | 2025-06-02 15:34:10+00:00
——————————————

SEEKING WORK | Remote (EU/US) | Senior Product Designer – Design Systems, Design-to-Code workflows, Accessibility

—

Portfolio: https://raigo.design/case-studies

Email: hi@raigo.design

LinkedIn: https://linkedin.com/in/raigolilleberg

—

Services

UX/UI cleanup & prioritization sprint

For teams with messy or inconsistent UI – I review 3–5 screens or flows and deliver focused feedback, Figma updates, and a prioritized action list covering UX, consistency, and early accessibility wins.

.

Design system sketch pack

For teams overwhelmed by UI duplication and design debt – I analyze your UI patterns and propose a scalable Figma component system with tokens, naming conventions, and (optional) dev-aligned notes or html/css examples.

.

Design-to-code process tuning

For teams struggling with slow or messy design handoff – I audit your design-to-dev workflow and suggest improvements, including refinements to your Figma files and process alignment with engineering.

.

Accessibility review (early stage)

For teams just beginning to consider accessibility – A lightweight audit of 2–3 key screens against WCAG 2.1/EAA standards, with an actionable checklist and UI recommendations.

.

Fractional design partner (ongoing)

For lean teams that need a reliable senior designer – Bi-weekly async support across UX, design systems, design-to-code workflows, and accessibility—adapting to your team's specific goals and workflows.

—

I’m Raigo — a senior product designer with 10+ years of experience, including 7+ focused on web and mobile apps. I’ve worked remotely with startups and digital teams across the EU and US.

My strengths lie in streamlining design workflows, building and scaling design systems, and collaborating tightly with product and engineering. I work well in async environments with high autonomy and accountability.

Lately I’ve been deepening my practice in accessibility (WCAG, EAA, ARIA), design engineering, and AI-enhanced workflows.

If your product needs clarity, structure, or faster delivery—I’d be glad to help.

—

Let’s talk: hi@raigo.design

—

Raigo Lilleberg

https://raigo.design

https://linkedin.com/in/raigolilleberg

——————————————
by spiderice | 2025-06-02 15:34:23+00:00
But there very well might be a time very soon where human's no longer offer economic value to the software engineering process. If you could (and currently you can't) pay an AI $10k/year to do what a human could do in a year, why would you pay the human 6 figures? Or even $20k?

Nobody is claiming that human's won't have jobs simply because "we have accomplished everything this is to do". It's that humans will offer zero economic value compared to AI because AI gets so good and so cheap.
by thewebguyd | 2025-06-02 15:34:24+00:00
> I don't actually enjoy it, i generally find it difficult to use as i have more trouble explaining what i want than actually just doing it.

This is my problem I run into quite frequently. I have more trouble trying to explain computing or architectural concepts in natural language to the AI than I do just coding the damn thing in the first place. There are many reasons we don't program in natural language, and this is one of them.

I've never found natural language tools easier to use, in any iteration of them, and so I get no joy out of prompting AI. Outside of the increasingly excellent autocomplete, I find it actually slows me down to try and prompt "correctly."
by Elijahk | 2025-06-02 15:34:34+00:00
Location: NY, NY.

Remote: Open to remote or onsite work

Willing to relocate: Definitely for the right opportunity

Technologies: TypeScript, React, Python, Django, FastAPI, Figma ProtoTyping, MongoDB, Docker, Terraform, AWS, Azure, Firebase, ThreeJS

Resume/CV: https://elijahkennedy.com/resume.html

LinkedIn: https://www.linkedin.com/in/eliken/

Github: https://github.com/Elijer

Website: https://elijahkennedy.com/

email: elijahclimbs dot gmail dot com

Hi I'm Elijah! I am a fullstack web engineer with 5 years of professional experience, mostly in healthcare startups. I am open to both full-time roles and contract work.
by karambahh | 2025-06-02 15:34:46+00:00
Yeah, and especially as Vanta is adjacent... I think a rebranding is in order.

Vanta (and the auditors they market) is a nice company I'm happy user of but I'm afraid they won't be too pleased with this.

Your project is a pretty nice overview of what network level monitoring encompasses, I'd say it's more than a tool, it has obvious educational value. Would be sad to see it buried under naming issues.
by nickpsecurity | 2025-06-02 15:35:11+00:00
I believe you're way understating the difficulty of learning things like Alloy and doing theorem proving.

Let's say I want to teach them non-formal, high assurance. That will involve safe subsets of their language, functional style of programming with inputs to outputs, isolation of side effects, and code reviews. They can do this without any extra or unusual knowledge.

The basics of testing would likewise build on their existing knowledge. If their language supports it, static analyzers might work with the push of a button. Basic contracts might knock out many type or range errors without much thought. Basic tests go from their intuition to specific code implementing it.

OK, now let's build models using relationships expressed in Alloy or TLA+. Now, they have to learn to think in a totally different way. They'll need new notations, new techniques. They'll have to put time into these not knowing the payoff. They'll also have far less or zero resources like StackOverflow or GeeksForGeeks that can solve the whole problem for them.

Moving into theorem proverbs, they now have to know math or logic. They have to think formally. They have to specify the problem that way, keep it in sync with the English, do lots of work that might just be about limitations of the formal tool, and eventually they succeeded (or dont) at the proof. It's also a very, slow process vs informal methods of correctness checking.

So, it's quite difficult to learn these things vs alternative methods. They also might have low or slow payoff while others payoff quickly and often. That's why I push using the alternatives first. Then, learning others overtime to gradually add them to your toolbox for when it makes sense: data structures, interface specification, highly-critical routines, etc.
by thatguy0900 | 2025-06-02 15:35:12+00:00
My viewpoint is that a population collapse is very bad for society, can already see it beginning to happen in places like South Korea. I don't see how I could possibly retire with any comfort if Noone is having kids and we also don't accept immigrants. Human extinction is a bad thing to happen for the people alive when it's happening, philosophically in the grand scheme of things I think life would go on. I don't plan on having descendants at all and I am against the current mass deportations, especially the way it is currently being carried out.
by spacechild1 | 2025-06-02 15:35:15+00:00
Thanks for the leveled response!

> Sure, but memory ordering is orthogonal to LL/SC vs CAS.

Sure, but your original claim was that std::atomic has been designed with only x64 in mind. That's what I meant to argue against.

I agree that the omission of something like fetch_update() has been an oversight and I hope that it will make it into the C++ standard!

As a side note, here's what the Rust docs say about fetch_update():

> This method is not magic; it is not provided by the hardware. It is implemented in terms of AtomicUsize::compare_exchange_weak, and suffers from the same drawbacks.

https://doc.rust-lang.org/std/sync/atomic/struct.AtomicUsize...

So Rust's std::sync::atomic is equally "useless"? :)
Ask HN: How do middle schoolers talk to each other if they don't have phones?
by syedkarim | 2025-06-02 15:35:31+00:00
I have a kid starting middle school in the fall. She does not have her own phone and neither do any of her friends. None of her friends have home phones, either. So how do middle schoolers talk to each other over summer break? I'm assuming her situation is not unique, so this is a general question.
by thomasmg | 2025-06-02 15:35:34+00:00
So I'm a bit confused, the paper says "'Randen' ... outperforming ... PCG" but now you wrote "though slower than pcg64"? In the paper itself, PCG is faster but "these microbenchmark results are quite irrelevant in practice — which actual application repeatedly calls a random generator and ignores the results?" I wonder, was the paper peer-reviewed? (I'm not saying it should have been..., just wondering.)

My guess is that yes, Randen is fast, but it is not quite as fast as PCG or other pseudo-random number generators.

Whether or not it is relevant, that's another story. I can not agree to your claim "there are vanishingly few use cases" for insecure random number generators.
by jauntywundrkind | 2025-06-02 15:35:51+00:00
> Again, please check out the commit history -- especially early commits -- to understand how this went.

Direct link to earliest page of history: https://github.com/cloudflare/workers-oauth-provider/commits...

A lot of very explicit & clear prompting, with direct directions to go. Some examples on the first page: https://github.com/cloudflare/workers-oauth-provider/commit/... https://github.com/cloudflare/workers-oauth-provider/commit/...
by andrei_says_ | 2025-06-02 15:35:55+00:00
Yes. And in this case consider the ritual a part of the recipe, context, necessary environment for a certain complex healing experience.

Tested and iterated on through the years, and if your worldview allows for the concept of plant consciousness, consider that the steps may have been provided by its suggestion.

If one’s worldview is 100% materialistic, an encounter with some of these plants may change that.
by ben7799 | 2025-06-02 15:36:27+00:00
I think he's just using the wrong date range.

2012 things had already matured.

2009-2010 eReaders were a lot more expensive.

The "Kindle 2" in 2009 launched at $360.

So basically by 2012 prices had tanked, and there's a limit on how much cheaper they could actually make them in the years since.
by IAmBroom | 2025-06-02 15:36:48+00:00
I think that would produce a lot of false positives, and therefore a lot of disappointment for physically unattractive people. Some people aren't particularly motivated to pick only 9s & 10s; most people accept people in their own range or higher; and sure, some people who are 6s end up happy with 2s. But "We're really hitting it off!" followed by "Um, oh, sorry, I just remembered I left a pot on the stove BYE" is much worse than just not getting any "likes" at all.
by graemep | 2025-06-02 15:36:50+00:00
The "right to be forgotten" is not about preventing information from being sucked up by algorithms as stopping people from finding information about someone easily. It is more complex than that:

https://gdpr.eu/right-to-be-forgotten/ https://en.wikipedia.org/wiki/Right_to_be_forgotten#European...

In many cases URLs have been removed from search results but remain on the original site.

I have seen far more small sites blocking UK users because of the Online Safety Act than I ever saw blocking EU users because of the right to be forgotten.
by bloak | 2025-06-02 15:37:00+00:00
For a number of reasons, I don't like the duration of copyright depending on how long the author lives.

* It's age discrimination against older people.

* If the copyright ends up being owned by some corporation (or effectively owned: some corporation has exclusive rights), which is what usually happens for any valuable copyright, it seems weird that the duration should be based on the lifetime of the author.

* It creates problems later when it's not obvious who the author was or when the author died.

* It could easily be abused by authors adding their grandchildren as co-authors. (I'm a bit wary of mentioning this in case I give anyone ideas. It has happened already, but so far not very often, as far as I can tell.)
by puzzlingcaptcha | 2025-06-02 15:37:23+00:00
I bought a Kobo Glo HD for €129 in 2016. This would be €168 today.

A comparable entry-level model (Kobo Clara BW) today is €149 - 12% cheaper. It's also now waterproof and does bluetooth audio.

It's a niche product that doesn't really benefit much from economies of scale (think eInk displays of that size). I don't think anyone is getting ripped off here.
by TeMPOraL | 2025-06-02 15:37:26+00:00
> where I remain a skeptic is this constant banging-on that somehow this will translate into entirely new things - research, materials science, economies, inventions, etc - because that requires learning “in real time” from information sources you’re literally generating in that moment, not decades of Stack Overflow responses without context.

Personally I hope this will materialize, at the very least because there's plenty of discoveries to be made by cross-correlating discoveries already made; the necessary information should be there, but reasoning capability (both that of the model and that added by orchestration) seems to be lacking. I'm not sure if pure chat is the best way to access it, either. We need better, more hands-on tools to explore the latent spaces of LLMs.
by vlovich123 | 2025-06-02 15:37:45+00:00
This post overlooks a very important technique to get type hiding without the cost of boxing. Having an opaque public type that wraps the private one:

public struct SqlError(sqlx::Error) #[derive(Debug, thiserror::Error)] pub enum MyError { #[error("Database error: {0}")] DatabaseError(#[from] SqlError) }

It’s a bit more annoying to construct since result has to have a .map_error(SqlError) but that’s not that much honestly.
by mikepurvis | 2025-06-02 15:37:45+00:00
Yeah, and that's obviously pretty hostile when the best guide is reading the source.

I think the deeper problem that maybe isn't always considered in the "Nix needs better docs" discourse is that there are many tasks that simply don't have an optimal workflow in Nix (yet). It can be weird documenting how do some particular thing, but having to frontload that doc with a bunch of caveats about which particular set of tradeoffs the suggested approach is embracing.

For example with Python, a huge one is around how much you want to leverage the Python packages already in nixpkgs. If you want to use them, which makes sense if you don't really care about versions or you've got a lot of things with tie-ins to non-Python such as bindings packages, then you probably want the conventional buildPythonPackage workflow, where you manually package any missing deps, perhaps assisted by pip2nix: https://wiki.nixos.org/wiki/Python

But if you have a self-contained app that already has everything locked and you just want minimum friction, then you almost certainly want uv2nix: https://github.com/pyproject-nix

A lot of things in Nix are like this. Same story with containers where you've got dockerTools.buildImage but depending on your workflow nix2container is almost certainly the better choice. Nix's limitations around IFD are finally being addressed by https://tvix.dev/ but that's a rewrite and brings yet another potential split.

Nix is the epitome of being perpetually stuck in the 1000 flowers blooming [1] state of things, and in some ways that's beautiful, but it needs people to build a cathedral or two within the bazaar. Determinate [2] is trying, but they've also taken some heat from the community for concerns around OSS and governance.

[1]: https://news.ycombinator.com/item?id=10294833 / https://gigamonkeys.com/flowers/

[2]: https://determinate.systems/
by TwoSixTech | 2025-06-02 15:37:55+00:00
Two Six Technologies | Embedded Tool Developer | Arlington, VA | ONSITE | Full Time |https://job-boards.greenhouse.io/twosixtechnologies/jobs/550....... Two Six Technologies is seeking a Lead Embedded Tool Developer to transform innovative proofs of concept into robust capabilities that address real-world threats. We are also looking to hire embedded security researchers with experience in the following categories: firmware reverse engineering, hardware reverse engineering, and Linux/UNIX kernel development. Additional opportunities are available for embedded software engineers, electronic design engineers, digital signal processing engineers, hardware engineers, and firmware reverse engineers looking to enter the security field. We would love to hear from you if you work in the embedded security domain. Preference is for applicants who hold a TS clearance and have the ability to obtain SCI at a minimum. If interested, please reach out to our team @ recruiting@twosixtech.com
by kklisura | 2025-06-02 15:38:03+00:00
> “Reuters is lying,” Musk had posted on X, minutes after the story published on April 5, 2024, halting a 6% decline in Tesla’s stock.

> The executives knew that Musk had, in fact, canceled the low-cost vehicle...

> Musk’s post was so confusing to some senior managers that they asked him whether he’d changed his mind. Musk rejected their concerns and said the project was still dead...

How about we find out real truth via discovery on a class action lawsuit?
by c-linkage | 2025-06-02 15:38:05+00:00
I very much appreciate the fact that the OP posted not just the code developed by AI but also posted the prompts.

I have tried to develop some code (typically non-web-based code) with LLMs but never seem to get very far before the hallucinations kick in and drive me mad. Given how many other people claim to have success, I figure maybe I'm just not writing the prompts correctly.

Getting a chance to see the prompts shows I'm not actually that far off.

Perhaps the LLMs don't work great for me because the problems I'm working on a somewhat obscure (currently reverse engineering SAP ABAP code to make a .NET implementation on data hosted in Snowflake) and often quite novel (I'm sure there is an OpenAuth implementation on gitbub somewhere from which the LLM can crib).
by alanfranz | 2025-06-02 15:38:29+00:00
Carefully reviewed greenfield project; I don’t think this is astonishing, and I very much love they recorded the prompts.

Question is: will this work for non-greenfield projects as well? Usually 95% of work in a lifetime is not greenfield.

Or will we throw away more and more code as we go, since AI will rewrite it, and we’ll probably introduce subtle bugs as we go?
by diggan | 2025-06-02 15:38:45+00:00
> It's like complaining that you have to ask someone at Walmart to take a product out of the lockbox so that you can buy it.

Kind of similar I guess, but mostly not. Never been to Walmart, so not sure what I'd expect, but I'm guessing that if I ask them to give me that item, they'll give it to me?

Because that's not how Cloudflare's captchas work. Sometimes they'll keep on coming indefinitely, until you give up and try again another day. Doesn't happen often when I'm in Spain, but if I'm in Peru for example that happens a lot. In Spain I usually get away with filling in 3-5 captchas, then I'm good to go.

So I guess your Cloudflare experience is wildly different depending on what country you live in, which is why you see some of us being very tired of it, and others not caring that much about it, probably because they live in a country with lower "spam-ranking", or however they do it internally.
by k310 | 2025-06-02 15:38:48+00:00
I couldn't find a free copy of the paper, but search turned up this interesting paper at arxiv:

"I Feel Like I'm Teaching in a Gladiator Ring": Barriers and Benefits of Live Coding in Classroom Settings, by Caroline Berger, David Weintrop, Niklas Elmqvist

> Live coding for teaching-synchronously writing software in front of students-can be an effective method for engaging students and instilling practical programming skills. However, not all settings are conducive to live coding and not all instructors are successful in this challenging task. We present results from a study involving university instructors, teaching assistants, and students identifying both barriers and benefits of live coding. Physical infrastructure, a positive classroom community with psychological safety, and opportunities for teacher development are practical considerations for live coding. In order for live coding to be an active learning experience, we recommend that tools support multiple mechanisms for engaging students, directing audience attention, and encouraging student-led live coding.

https://arxiv.org/abs/2504.02585v1
by brandon-johnson | 2025-06-02 15:38:50+00:00
Location: San Francisco, CA Remote: Yes Willing to relocate: NO Technologies: React, Next, JavaScript, TypeScript, Tailwind CSS, Supabase, AI, AWS Résumé/CV: https://drive.google.com/file/d/13TMudJ44vE-XMEvnf5zm6P18zqimtN5A/view?usp=sharing Email: brandonjohnson19970202@gmail.com

Senior frontend developer (8+ years of experience) with a habit of turning chaotic product specs into smooth, intuitive UIs—and occasionally into memes. I specialize in AI-powered tools, pixel-perfect dashboards, and reducing user frustration (and dev burnout) one clean component at a time. Startup survivor, productivity nerd, and strong believer that “user-friendly” shouldn't require a manual or a prayer.

https://www.linkedin.com/in/brandon-johnson-ok
by riskable | 2025-06-02 15:38:55+00:00
From a copyright perspective the only question that matters is this: Do we treat AI models like (Xerox) copiers or do we treat them like artists?

If we treat it like a copier it's the end user that's responsible when they tell it to produce something that infringes on someone else's copyrighted work. No different than if someone walked up to a machine and copied an entire book.

Furthermore, if the end user never even distributes the result of a prompt the question is moot anyway: Copyright only matters when something gets distributed. No distribution == No violation of copyright.

If we treat AI like an artist it is the owner/creator of the AI model that's responsible when it produces something that violates another's copyright. Since it is literally impossible to maintain a database of all copyrighted works that exist (in order to check if something violates copyright or not) this option is untenable. It's not possible to implement unless we go back to requiring all copyrights be registered (and provide that database to anyone that asks—thus, distributing all those copyrighted works which would defeat the purpose).

I very strongly believe that the courts will ultimately settle on treating AI like a copier. It's a tool/machine and should be treated as such by copyright law.