MurphyA/hacker-news huggingface dataset:
by awwaiid | 2026-02-17 01:14:00+00:00
I've been building a skill to help run manual tests on an app. So I go through and interactively steer toward a useful validation of a particular PR, navigating specifics of the app and what I care about and what I don't. Then in the end I have it build a skill that would have skipped backtracking and retries and the steering I did.

Then I do it again from scratch; this time it takes less steering. I have it update the skill further.

I've been doing this on a few different tests and building a skill which is taking less and steering to do app-specific and team-specific manual testing faster and faster. The first times through it took longer than manually testing the feature. While I've only started doing this recently, it is now taking less time than I would take, and posting screenshots of the results and testing steps in the PR for dev review. Ongoing exploration!
by sjs382 | 2026-02-17 01:16:30+00:00
ChatGPT 5.2 Thinking for me:

---

Walk.

At 50 meters, driving is usually slower overall (start car, back out, pull in), adds unnecessary engine wear (cold start/short trip), increases minor risk in a parking lot/driveway, and you’ll have to park again anyway.

Drive only if there’s a practical constraint like:

you need to bring heavy items (bucket/cleaning kit) and can’t carry them,

bad weather/unsafe walking conditions,

mobility limitations.
by gwern | 2026-02-17 01:16:50+00:00
Allowing more metadata might be useful. You can add anything to the manifest at build time as assets are not required to be loaded or ever used (because this is impossible to statically check). I suppose we'd have to define an official prefix like 'gwtar-metadata-*' with like a 'gwtar-metadata-screenshot' and 'gwtar-metadata-desciption'... Not obvious what the best way forward is there, you don't want to add a whole bunch of ad hoc metadata fields, everyone will have a different one they want. Exif...?

Multiple versions or multiple pages (maybe they can be the same thing?) would be nice but also unclear how to make that. An iframe wrapper?

I considered and rejected deduplication and compression. Those can be done by the filesystem/server transparent to the format. (If there's an image file duplicated across multiple pages, then it should be trivial for any filesystem or server to detect or compress those away.)
by Terr_ | 2026-02-17 01:17:20+00:00
> An honest signal doesn't always take effort.

I would guess that the non-effort signals instead involve risk tolerance.

It's a statement that they could easily withstand the consequences of an adverse judgement in ways regular people can't.

If I get turned away from Le Foie Heureux for failing to meet the restaurant dress-code, there's not much I can do. If the sommelier thinks that a billionaire looks like a vagrant, well, the billionaire will make a phone call...
by zmgsabst | 2026-02-17 01:17:21+00:00
I think it’s a difference in kind, ie, if we return to above[0] and the discussion about “outsourcing our thinking” — then it deeply depends on what we hope to accomplish. That’s what I was originally intending to convey: that people are actually inhabiting the space you used as an extreme because they’re operating in a different mode.

That is, we seem to be conflating different cases - ie, being an expert versus hiring an expert. A manager and an SDE get different utility from the LLM.

I think I expressed it poorly, but I think that we need to consider that outsourcing thinking entirely is the right answer in the way that subcontracting or outsourcing or hiring itself can be; and that we seem to get caught in a “spectrum” or false dichotomy (ie, “is outsourcing good or bad?”) discussion, when the actual utilization of LLMs, their content, etc interacts in a complex way due to the diversity of roles, needs, etc that humans themselves have. And the impact on acquired expertise is only one aspect, for which “less work, less learning” is both true but too simple.

[0] - https://news.ycombinator.com/item?id=47040091
by nradov | 2026-02-17 01:17:28+00:00
There has been a standard X12 EDI format for invoices for decades. It's kind of a hassle to work with but it can at least be reliably parsed. A lot of huge businesses like Walmart use it successfully, and even require their suppliers to submit all invoices that way.

I don't object to using LLMs to parse PDFs but over the long run it's going to be less efficient and reliable than other options.
by simianwords | 2026-02-17 01:17:40+00:00
I'm not sure what your comment is trying to say.

>They would only decrease much later, after a long period of social conflict, economic growth, and technological progress.

The technological process mentioned here as Industrial Revolution, was the necessary step. It was not primarily social conflicts.

The above poster is making exactly the same point.

You are right that there was an aberration in the middle where people worked way more hours but this was when things were consolidating.

But your post implies that the preference of people was to work less hours as opposed to work more hours and earn more money, which is not the case.
by rhodey | 2026-02-17 01:17:55+00:00
At my time of reading it is not at all clear to me how the "sandbox network proxy" knows what value to inject in place of the string "proxy-managed"

> Prerequisites
> An Anthropic API key in an env variable

I am willing to accept that the steps in the tutorial may work... but if it does work it seems like there has to be some implicit knowledge about common Anthropic API key env var names or something like this

I wanna say for something which is 100% a security product I prefer explicit versus implicit / magically
by jlpk | 2026-02-17 01:17:56+00:00
Nice work! For others with journals in the U.S., but not feeling up to all the scanning and transcription work, I volunteer with the American Diary Project (https://americandiaryproject.com/) based in Cleveland Ohio. You can donate journals to be archived and shared. It's only been established in the past few years, and all scanning/transcription is done by volunteers, but are currently evaluating more automated pipelines like OPs. So great to see it in practice!
by truncate | 2026-02-17 01:18:11+00:00
Three patterns I've noticed on the open-source projects I've worked on:

1. AI slop PRs (sometimes giant). Author responds to feedback with LLM generated responses. Show little evidence they actually gave any thought of their own towards design decisions or implementation.

2. (1) often leads me to believe they probably haven't tested it properly or thought of edge cases. As reviewer you now have to be extra careful about it (or just reject it).

3. Rise in students looking for job/internship. The expectation is that LLM generated code which is untested will give them positive points as they have dug into the codebase now. (I've had cases where they said they haven't tested the code, but it should "just work").

4. People are now even more lazy to cleanup code.

Unfortunately, all of these issues come from humans. LLMs are fantastic tools and as almost everyone would agree they are incredibly useful when used appropriately.
by freetime2 | 2026-02-17 01:18:47+00:00
Sure I think there's some truth the that. You've gotta learn the rules first to know when it's ok break the rules. Somebody with a lot of experience should be able to judge how their message will be received, and what amount of effort is "good enough". Whereas someone with less workspace experience may lack such judgement, and is probably better off erring on the side of "too good" rather than "not good enough".

But it's definitely also very much tied to status, power, and privilege. The same people who have no qualms about firing off a sloppy email to their subordinates often spend a lot more effort on emails to their bosses. But even this discrepancy is justified, I think, given that a manager represents their subordinates to the higher ups. And the potential consequences of a bad impression or misunderstanding are more severe when communicating up the chain of command.
by nihalwashere | 2026-02-17 01:18:49+00:00
Thanks! Honestly that was just pure luck with the domain :)

There's a Docker deployment guide here: https://docs.reader.dev/documentation/guides/deployment

For k8s, you can run multiple Reader instances behind a load balancer, each manages its own browser pool. Main things to watch:

- Memory limits (~500MB-1GB per concurrent browser)
- Headless Chrome needs --no-sandbox or a seccomp profile
- Sticky sessions for crawl jobs (or run full crawl on single pod)

A dedicated k8s guide is on the roadmap...
by commandersaki | 2026-02-17 01:19:29+00:00
1Password - the only real drawback is they use an electron app for desktop, and they don't really have a good story for legacy recovery.

Otherwise they have an incredibly strong security model (though it means its a bit complicated to the end user) and they support almost every form of credential TOTP, Passkey, passwords, etc.

They're also working on simplifying unlock methods such as being able to use a passkey to unlock (such as your iCloud passkey), or using your passcode/biometrics unlock double as the unlock for 1P.

It seems to have good integration into iOS as well for autofilling in apps and such.

Also, it supports custom fields where some forms on websites require some additional codes or secrets that normally don't autofill because they're not a password. 1P handles this pretty gracefully by just having a labelled text field stored as part of the login credential and it'll automatically fill that in.

They have a family pricing and it comes out cheaper once you have 2 members using it. Also sharing credentials, notes, etc. with other members is pretty straightforward.

If you just want something to start out with and you're in Apple ecosystem, consider the Apple Passwords app which is free. Having something is better than nothing.
by mindslight | 2026-02-17 01:20:17+00:00
I understand. In fact, I've been there - I was working on ecash and cryptography before bitcoin and the bastardization of the term crypto. "Code is law" and all that.

I'm sure some of it is due to getting older, but with open cult-of-personality autocratic authoritarianism (aka fascism) upon us I have become quite conservative. I had been taking a lot for granted about the freedoms we do have, and the position of the Western world. Don't let a desire to make things better goad you into wanting to destroy what we do have.

But regardless, if you recoil from the groupthink of the leftists you should be similarly allergic to the groupthink of the rightists. They have taken up the mantles of so many of our longstanding societal problems, only to be led by outright con men and liars who are doing nothing to actually address those problems. And I don't just mean hate-but-hold-your-nose-for-some-greater-good, but rather hold them in the same exact regard as the leftists. Especially as that red tribe groupthink is now in power, and its results are not pretty.
by Mr_Minderbinder | 2026-02-17 01:20:52+00:00
> In terms of strength he's the weakest player to win in half a century even in absolute terms.

Gukesh is arguably stronger than either of Khalifman, Kasimdzhanov and Ponomariov, who won the FIDE title before it was re-unified. Also his current rating is higher than either Karpov’s or Kasparov’s were when they first won the title. His rating when he first won was about the same as Fischer’s when Fischer first won. Neither Kramnik or Anand were clearly the best player throughout the entirety of their reigns and both of their ranks fluctuated amongst the top ten positions.
by daxfohl | 2026-02-17 01:22:40+00:00
I'm kinda surprised by this. Yeah it's just regurgitating something it already "knows", but I'd still expect that having the skill materialized there in the context would give it something concrete to reference, less likelihood of getting lost or hallucinating, and probably need less incremental context to do the job.

I mean, basically it's doing the same thing as reasoning IIUC, except up-front rather than inline and ad-hoc, so I'd almost expect it to work even better than reasoning alone.
by yongjik | 2026-02-17 01:22:45+00:00
Savings are literally being passed onto the consumers. The #1 reason people buy imported goods is that they are cheaper: if they're the same price as domestic goods then there will be little incentive to buy imported goods and domestic jobs won't be going away.

In other words, the only reason foreign industry threatens domestic jobs is because it's cheaper to produce the same thing in these countries and the cost savings are being passed on to domestic consumers.

Sometimes I wonder if we're simply living in different realities. You may claim it's not worth it, but you can't claim it's not happening. Just go to grocery and see the prices of Mexican avocados and everything.
by dogline | 2026-02-17 01:23:15+00:00
I did a quick search, mules are mentioned 75 different times. Like this one at random from Sept 1942: https://forestrydiary.com/page/019bd90a-f176-713f-9999-b14b6...

"Fix up my packs. Load the 2 mules with 225# each. Take the 2 loads to trail camp at Lake Everett, Unload. Have lunch with the Trail cook. Haze mules & ride to 7 1/2 PM."

Horses are mentioned 2586 times. That'd be a whole study on how they're used in the back country. (Edit: horse number is inflated since part of the diary form at one point asks for "Horse Mileage". Will have to refine search).
by Terr_ | 2026-02-17 01:23:21+00:00
Half-agree: "Blockchain" systems contain new and useful technology, but the useful technology is not new, and the new technology is not-so-useful. If we keep the useful stuff, we're basically back at regular old distributed databases.

The key blockchain requirement is allowing unrestricted node membership. From that flows a dramatic explosion of security issues, performance issues, and N-level deep workarounds.

In the case of a bunch of banks trying to keep each other honest, it's drastically simpler/faster/cheaper to allocate a certain number of fixed nodes to be run by different participants and trusted outside institutions.

One doesn't need to trust every node, just the a majority is unlikely to be suborned, and you'll know in advance which majorities are possible. The bank in Australia probably doesn't want or need to shift some of that responsibility outside the group, onto literally anybody who shows up with some computing power.
by lauriewired | 2026-02-17 01:24:32+00:00
This is correct. The majority of cases I have to rely on my own expertise.

It's useful for the automation of small repetitive tasks here and there. I was never expecting it to gain the traction that it did; anyone saying they expect it to replace reverse engineers (it won't) is wildly misunderstanding the original intent.

Quite trivial to create binaries that massively confuse LLMs!
by puttycat | 2026-02-17 01:25:29+00:00
> They contacted Facebook, which at the time dominated the social media landscape, asking for help scouring uploaded family photos - to see if Lucy was in any of them. But Facebook, despite having facial recognition technology, said it "did not have the tools" to help.

Willing to bet my life savings that they are able to do exactly this when the goal is to create shadow profiles or maximize some metric.
by ssl-3 | 2026-02-17 01:26:20+00:00
It is.

My read through this document suggests that the maximum usable range may be as far as 5 meters, or as little as 1 meter: https://rfid.michelin.com/wp-content/uploads/2024/07/dataShe...

That's not as far as BLE or TPMS can work at, but it's not exactly like the NFC arrangement in a credit card, either. 5 meters is enough for a motivated attacker to do some undetected bulk data collection.
by scoofy | 2026-02-17 01:26:35+00:00
So, yes, OP here and you're effectively right on the money. Mark Broadie's strokes gain approach is literally dynamic programming applied to golf. He even discusses a bit of the history of dynamic programming in Every Shot Counts.

The point of what I'm doing here is pointing that strokes gained approach at the golf course instead at the player. Ideally, I'd like to continue working on it to build something that can help clubs make minimal, inexpensive changes while maximally improving the strategic interest if the way the course plays.
by sloaken | 2026-02-17 01:27:15+00:00
It could be.

From HR perspective it might be the best place to work.

I would look at glassdoor.

Realize it could be great and awful depending on where you work. HR could be great while IT could suck. I interviewed at a place that on glassdoor was listed very well. But when I examined the reviews in detail. Everywhere BUT IT had nothing but praise. IT was a dumpster fire, probably why they were hiring.
by dtnewman | 2026-02-17 01:27:26+00:00
Open Source isn't going anywhere. Open Contribution might be on the way out. I built an open source command line tool (https://github.com/dtnewman/zev) that went very minorly viral for a few days last year.

What I found in the following week is a pattern of:

1) People reaching out with feature requests (useful)
2) People submitting minor patches that take up a few lines of code (useful)
3) People submitting larger PRs, that were mostly garbage

#1 above isn't going anywhere. #2 is helpful, especially since these are easy to check over. For #3, MOST of what people submitted wasn't AI slop per se, but just wasn't well thought out, or of poor quality. Or a feature that I just didn't want in the product. In most cases, I'd rather have a #1 and just implement it myself in the way that I want to code organized, rather than someone submitting a PR with poorly written code. What I found is that when I engaged with people in this group, I'd see them post on LinkedIn or X the next day bragging about how they contributed to a cool new open-source project. For me, the maintainer, it was just annoying, and I wasn't putting this project out there to gain the opportunity to mentor junior devs.

In general, I like the SQLite philosophy of we are open source, not open contribution. They are very explicit about this, but it's important for anyone putting out an open source project that you have ZERO obligation to accept any code or feature requests. None.
by umairnadeem123 | 2026-02-17 01:27:32+00:00
tests taking minutes is usually a symptom of integration creep, not just slow code. once you have a few slow e2e flows, they dominate wall clock unless you shard + run in parallel.

what helped us: split unit vs contract vs e2e, keep e2e <10%, and treat long tests like a queue (retry, quarantine flaky). ai can write test scaffolding fast but it also encourages over-testing the wrong layer.
by sokoloff | 2026-02-17 01:27:45+00:00
Agree that SMD hand assembly is easier than it looks, at least down to 0603 imperial. If I can wait the week for boards to arrive, I’ll often skip the breadboard step and go straight to a proto PCB, especially since most parts aren’t available in throughhole without waiting on dev boards anyway.

When you hand someone a board with 0603s on it that you hand-assembled, it seems like magic to people who stop to think about it.
by umairnadeem123 | 2026-02-17 01:27:50+00:00
governance for agents feels like it needs 3 primitives: allowlist tool access, budgeted retries/backoff, and an audit log you can diff.

how are you thinking about idempotency? most failures ive seen are agents retrying side effects (double charges, double posts). curious if bulwark enforces a request id / dedupe layer or just observes.
by umairnadeem123 | 2026-02-17 01:28:11+00:00
these kinds of marketplace edge cases are brutal bc they sit at the billing boundary. one mitigation ive used is treating every entitlement change as an event with a monotonic version and making the consumer idempotent (ignore stale versions).

also worth adding a reconciliation job: periodically recompute entitlements from source of truth and repair drift. its annoying but it turns races into eventual consistency instead of permanent weird states.
by nabbed | 2026-02-17 01:28:11+00:00
>At this point, I don’t think we will hire another human for at least a year or two at our firm, but our efficiency will increase by at least 10% a month – the equivalent of two new full-timers.

and

>This isn’t dystopian. It’s nirvana!

Although the nirvana part is probably mostly in reference to having more free time to spend with podcast guests and other founders and less about being able to avoid hiring humans.

Such overheated, almost delirious writing. Lots of one sentence paragraphs with exclamation marks. I am not sure how to take it. Still, I am glad I exited the software business (and the workforce altogether) a few years ago, and it seems my timing was impeccable!
by umairnadeem123 | 2026-02-17 01:28:32+00:00
the thing i like about a more structured cve process is it forces a paper trail, but the failure mode is turning it into a throughput bottleneck.

imo the pragmatic approach is: let maintainers publish advisory + fix quickly, then let cve ids catch up asynchronously. the priority should be fixing and communicating impact, not the id itself. otherwise you incentivize people to sit on fixes while paperwork happens.
by umairnadeem123 | 2026-02-17 01:28:51+00:00
this feels like the missing primitive between classic full page reloads and heavy client hydration. if patching can preserve scroll position + focus + selection reliably, it unlocks a lot of low-js apps.

but the hard part is semantics: what happens to event handlers and component state when nodes are replaced. do you envision a standard way to mark stable ids (like keyed diffs) so patchers can do minimal DOM surgery?
by userbinator | 2026-02-17 01:29:27+00:00
One reason soldering with an iron can be difficult is because your hand is so far away from the tip, like trying to write with a pen held by the end.

Newer irons, especially for SMD work, have gotten smaller and the grip-to-tip distance also shrunk; here's a good visual comparison:

https://www.eevblog.com/forum/reviews/grip-to-tip-distance-o...

It's worth noting that the longest one there is already much shorter than the classic mid-century unregulated irons, and all of those can be held like a pencil.
by loeber | 2026-02-17 01:30:41+00:00
This is a deeply pessimistic take, and I think it's totally incorrect. While I believe that the traditional open source model is going to change, it's probably going to get better than ever.

AI agents mean that dollars can be directly translated into open-source code contributions, and dollars are much less scarce than capable OSS programmer hours. I think we're going to see the world move toward a model by which open source projects gain large numbers of dollar contributions, that the maintainers then responsibly turn into AI-generated code contributions. I think this model is going to work really, really well.

For more detail, I have written my thoughts on my blog just the other day: https://essays.johnloeber.com/p/31-open-source-software-in-t...
by the-anarchist | 2026-02-17 01:31:03+00:00
> corrupt criminals and mafia types who have a need to covertly hide cash

You're describing the people that use actual cash to launder and hide, well, cash, and that have done so for centuries, long before crypto had even been invented.

A few web searches on <big bank name> + "money laundering scandal" (e.g. "HSBC money laundering scandal") can offer valuable insights.
by suprjami | 2026-02-17 01:31:50+00:00
Not Claude, but there are open-weight LLMs trained specifically on Ghidra decomp and tested on their ability to help reverse engineers make sense of it:

https://huggingface.co/LLM4Binary/llm4decompile-22b-v2

There's also a dataset floating around HF which is... I think a popular N64 decomp to pseudo-C? Maybe the Mario one?