MurphyA/hacker-news huggingface dataset:
by zbentley | 2025-05-28 12:55:22+00:00
I think that discussions in this area get muddied by people using different definitions of “rapidly”. There are (at least) two kinds of speed WRT tests being run for a large code base.

First, there is “rapidly” as pertains to the speed of running tests during development of a change. This is “did I screw up in an obvious way” error checking, and also often “are the tests that I wrote as part of this change passing” error checking. “Rapid” in this area should target low single digits of minutes as the maximum allowed time, preferably much less. This type of validation doesn’t need to run all tests—or even run a full determinator pass to determine what tests to run; a cache, approximation, or sampling can be used instead. In some environments, tests can be run in the development environment rather than in CI for added speed.

Then there is “rapidly” as pertains to the speed of running tests before deployment. This is after the developer of a change thinks their code is pretty much done, unless they missed something—this pass checks for “something”. Full determinator runs or full builds are necessary here. Speed should usually be achieved through parallelism and, depending on the urgency of release needs, by spending money scaling out CI jobs across many cores.

Now the hot take: in nearly every professional software development context it is fine if “rapidly” for the pre-deployment category of tests is denominated in multiple hours.

Yes, really.

Obviously, make it faster than that if you can, but if you have to trade away “did I miss something” coverage, don’t. Hours are fine, I promise. You can work on something else or pick up the next story while you wait—and skip the “but context switching!” line; stop feverishly checking whether your build is green and work on the next thing for 90min regardless.

“But what if the slow build fails and I have to keep coming back and fixing stuff with an 2+ hours wait time each fix cycle? My precious sprint velocity predictability!”—you never had predictability; you paid that cost in fixing broken releases that made it out because you didn’t run all the tests. Really, just go work on something else while the big build runs, and tell your PM to chill out (a common organizational failure uncovered here is that PMs are held accountable for late releases but not for severe breakage caused by them pushing devs to release too early and spend less time on testing).

“But flakes!”—fix the flakes. If your organization draws a hard “all tests run on every build and spurious failures are p0 bugs for the responsible team” line, then this problem goes away very quickly—weeks, and not many of them. Shame and PagerDuty are powerful motivators.

“But what if production is down?” Have an artifact-based revert system to turn back the clock on everything, so you don’t need to wait hours to validate a forward fix or cherry-picked partial revert. Yes, even data migrations.

Hours is fine, really. I promise.
by injidup | 2025-05-28 12:55:45+00:00
Often. It's often as simple as adding to the prompt to prefer to use standard libraries than recoding algorithms from scratch. Or do a second pass on something that you feel might be copy pasting ideas. And adding to the prompt doesn't mean always having to type it. I have a set of canned things that get added to every request which includes, coding standards and requests to use standard api. You often get what you ask for not what you want.
by sensanaty | 2025-05-28 12:55:47+00:00
> I think you could make similar arguments about mapping technology like Google and Apple Maps

The problem is that mapping software is reliable and doesn't spit out a result of what is essentially a random number generator. You can rely on its output, the same way you can rely on a calculator. Not always, mind you, because mapping the entire globe is a massively complex task with countless caveats and edge cases, but compared to LLM output? Even with a temperature setting of 0 with the same prompt regenerated multiple times, you'll be getting vastly different output.

Also, since LLMs cover a much more broad swathe of concepts, people are going to be using these instead of their brains in a lot of situations where they really shouldn't. Even with maps, there are people out there that will drive into a lake because Google Maps told them that's where the street was, I can't even fathom the type of shit that's going to happen from people blindly trusting LLM output and supplanting all their thinking with LLM usage.
by bluGill | 2025-05-28 12:55:55+00:00
that isn't a mono repo, it is a polyrepo setup with the wrost features of a polyrepo. I use a polyrepo setup and it works well, but we need careful attention to the repo split - and repo where too many different teams work together gets the worst features of a monorepo combined with the worst features of a poly-repo. We have a lot of tooling around making the different repos stay in sync.
by ty6853 | 2025-05-28 12:56:01+00:00
Yes you have to put two and two together.

If the attrition of newcomers is high enough, and oldtimers fill newcomer positions (or just their wages) in rough times, then if the high attrition of newcomers is high enough to overcome the phase-in rate of automation then the old timers will more or less stay employed just likely at the shit wages that newcomers get.
by mark_l_watson | 2025-05-28 12:56:09+00:00
Interesting article! Also good to see what we have done, and anything done with international cooperation is almost always a good thing.

Off topic, but it is good to see The Atlantic back to doing non-political quality journalism! As a company they had gone down a dark partisan rabbit hole of just propagandizing for one political party.

I had blocked The Atlantic in Apple News, now I am going to start reading them again.
by christina97 | 2025-05-28 12:56:33+00:00
The post doesn’t account for the case where a suburb of Amsterdam breaks off from the rest of Netherlands and changes timezones… Then how do you know if the event was in the neighborhood or not?

My point is that this is an extremely niche case and works around one particular type of timezone insanity. You either have a team dedicated to dealing with timezone insanity, or you store stuff in UTC.
by guffins | 2025-05-28 12:56:42+00:00
That’s a great question. ISO 8601 doesn’t allow timezone offsets on date-only strings.

If you were born in the US, can you buy cigarettes at 12:00 am on your 18th birthday in London?

I’ve never heard of age verification laws caring what timezone you were born in. In fact, you couldn’t even pinpoint this from many people’s ID cards. Plenty of US states span multiple time zones, and I wouldn’t be that surprised if there were a maternity ward out there sitting on a TZ line.
by rochav | 2025-05-28 12:57:17+00:00
I keep seeing comments like this and can't help but feel like that would be like suggesting someone who makes pottery as a hobby could make it way faster by just ordering the vase they want from someone else; I imagine the fun part in this, as in many other hobbies, is making it, because if just want to play something someone else made, you can already do that, can't you? Maybe it won't be exactly what you wanted, but the LLM generated one won't also.
by The_SamminAter | 2025-05-28 12:58:30+00:00
There’s several going for roughly 30,000-40,000 yen (before shipping) on [buyee.jp](https://buyee.jp/item/search/query/Sharp%20X68000) currently. I’m considering picking one up myself, though I’m quite sure I’d have no use for it (please outbid me).
by xyst | 2025-05-28 12:59:04+00:00
> Back in 2015, I was working on a project to build PoE-powered embedded x86 computers and digital signage systems.

> Our device required about 23W when fully operational, which pushed us into 802.3at (PoE+) territory

The problem the author solved is quite interesting. But I can’t help but think how wasteful it is to load up a full copy of windows just to serve up dumb advertisements.

The attack surface of a fully copy of windows 10 is an attackers wet dream.

Hope most of these installations are put out to pasture and replaced with very low power solutions.
by mickael-kerjean | 2025-05-28 12:59:36+00:00
For my use case of building Filestash, WASM is a game changer in those 2 areas:

1. use libraries from ecosystem outside JS. In the past few months, I've added support for file types like psd, dbf, arrow, parquet and about 50 more. To give a concrete example: https://www.filestash.app/tools/parquet-viewer.html WASM open up a very exciting door. In the same idea, I stumbled upon a couple JAVA only libraries which I would love to ship on a browser and not have to create web service to interact with those.

2. enable third party to make plugin that can run in my app in a safe way. In my case, plugins are zip files containing a bunch of assets and the WIP piece is to be able to put wasm in there that will run server side without giving those plugins a blank check for acting crazy.
by gabev | 2025-05-28 12:59:57+00:00
Quite a lot of em dashes for the New Yorker...

[EDIT] Several commenters rightly noted that heavy em-dash usage is normal for the New Yorker (and common thanks to OS auto-replacement), so my “LLM giveaway” quip was off-base. Leaving this up for context—thanks for the corrections.
by graybanana | 2025-05-28 13:00:22+00:00
I think the author's point is that while you might a priori think there are lots of groups out there that might be good candidates for DH, it turns out that elliptic curves are a strictly better choice than every alternative, and the reasons for this were definitely no fully known at the time Miller and Koblitz proposed ECC.

There was a period during which there was lots of interest in using abelian varieties of higher dimension (arising as Jacobians of curves of higher genus), with dimensions g=3 and g=4 being particularly attractive because then you could work over a very computationally friendly base field like Fp with p = 2^61-1. But it turns out the discrete logarithm problem (and therefore DH) is strictly easier in these settings (one can exploit Weil restrictions to get an algorithm that is still exponential-time but strictly better than O(p^(g/2)). But this wasn't known until the 2000's.

That leaves g=1 and g=2 as the best choices, and the group law is faster and simpler for g=1, and as far as I know nobody is really working on the g=2 case anymore (but there was a lot of activity in this area 10-20 years ago).
by throwanem | 2025-05-28 13:00:41+00:00
> I am not the author of the Dynomight article.

Who chose to bring it up? Who chose to insist on its baseless conclusions? Who then demonstrated the inability to defend those conclusions for their total lack of substance?

No, you don't get to represent the source you chose as accurate only until that fails to go your way, and then turn around and try to disclaim it. The embarrassment you now feel is amply earned.

This is what it feels like to have failed to evaluate your sources, argued strenuously in support of total nonsense, and thus made a complete and negligent fool of yourself. You should draw a lesson from that for next time you consider starting a conversation like this one.

You won't; you are too deeply in love with the idea of yourself as a clever person, and you won't dismiss the offense I gave to consider the substance of my remarks. This is a level of predictability I would not be comfortable with in myself. But that, too, is no problem of mine.

You've tried moving the goalposts again, had you noticed? If I let you get away with it, we wouldn't be talking about the factual inaccuracies, facial implausibilities, and ignorant misrepresentations of research, in the source you so uncritically chose, at all...
by vouaobrasil | 2025-05-28 13:00:58+00:00
We kinda did this to ourselves, as we insisted on eating vast quantities of meat for billions, which likely caused a huge range expansion [1]. And global warming is likely to make it worse [2]. I can't help but think it's a bit of karma – if everyone just ate meat once a month we could have much less livestock and a much more manageable screwworm problem.

[1] https://academic.oup.com/jme/article-abstract/48/2/280/89277... [2] https://resjournals.onlinelibrary.wiley.com/doi/abs/10.1111/...
by AnimalMuppet | 2025-05-28 13:01:31+00:00
All right, let me put it this way: As a developer, my most important tool is my brain. The time I spend figuring out what to build and how to build it is more important than just banging out some code.

For at least some people, stepping away from the keyboard may be the best way to do that thinking.

To put it in your own style: This isn't typing class, it's software engineering.
I built workflowhub AI for helping creators to monetize their automations
by workflowhubai | 2025-05-28 13:01:49+00:00
Hi HN, Woody Wang here. For the past 3 months, I've been building workflowhub.ai, a platform I wanted to share with you all today. I've noticed many talented people creating incredibly useful automation workflows with tools like n8n, Dify, and comfyUI, but they often sit on hard drives or are only shared informally. Existing marketplaces feel too general.

So, I built workflowhub.ai – a dedicated space for buying and selling these specific workflow files. Our core promise to creators is a 90% profit share. We want to help these underserved creators turn their expertise into a revenue stream

We're looking for people who build these automations – consultants, internal experts, hobbyists – who aren't currently selling them or find other platforms unsuitable.

I'd love to get your feedback on the platform once launched, our model, and especially hear from anyone who creates these kinds of workflows. What would make this valuable to you as a seller? Any concerns
by leo_dard | 2025-05-28 13:02:28+00:00
Actually, I did see one really cool use case. A guy was using a chatbot to help him revise for his uni courses. Not just chatting for the sake of it, but actually learning. It was super fluid and the whole thing was way sharper than the usual “how was your day?” stuff.

Wish I could remember the name of the app, if anyone knows it, let me know !
by intended | 2025-05-28 13:03:15+00:00
The very next sentence reads::

> Still, the screwworm advanced relatively slowly through Panama and Costa Rica for the first couple of years. Then it hit Nicaragua, and over just 10 weeks in 2024, it shot from the country’s northern border through Honduras and Guatemala to reach Mexico. This rapid advance was because of the illegal cattle trade,

Furthermore - given the attitudes we see in America, it seems clear there is no appetite for projects that other countries don’t pay for. From how I understand the rhetoric is made,

“this was a subsidy for cattle farmers, and for other nations, which should have picked up the slack on their own. “
by bluGill | 2025-05-28 13:03:20+00:00
Is a mono repo the answer, or is the real problem you just have a bad repo split.

I can't answer that question, and there are reasons to go monorepo anyway. However if your problem is a bad polyrepo split going to monorepo is the obvious answer, but it isn't the only answer. Monorepo and polyrepo each have very significant problems (see the article for monorepo problems) that are unique to that setup. You have to choose what set of problems to live with and mitigate them as best you can.
by techdmn | 2025-05-28 13:03:31+00:00
My own list:

* Leave your phone at home.

* Shop locally, not online.

* At locally owned stores, not big box chains that benefit from a lot of customer behavior data.

* Paying cash, to avoid the payment processor reselling your purchase history.

Now if only I could figure out a solution to those traffic cameras with license plate tracking, not to mention facial recognition.
Show HN: Puck – Open-source visual editor for React
by chrisvxd | 2025-05-28 13:04:29+00:00
I first shared Puck here back in Sept 2023, and wanted to give a quick update!

Here's the original post: https://news.ycombinator.com/item?id=37391848

Puck let’s you embed a page building experience within your own React application. It integrates with any backend or CMS, and since it’s MIT licensed, you can safely use it in internal tools or customer-facing products.

A lot’s changed since then; here are my highlights:

* Multi-column drag-and-drop with full CSS layout support (Grid, Flexbox, etc)

* Viewport previewing

* Headless mode for completely custom interfaces

* Permissions API to lock down authoring behaviour

* Dynamic fields that adapt based on data

The first Hacker News post was instrumental to Puck’s growth—when I first shared it, Puck had 6 stars and grew to 1,700 in 24 hours. It’s now approaching 7,000 stars. Thank you!

Always curious to hear feedback and answer questions.
by jrockway | 2025-05-28 13:04:48+00:00
Honestly, both are pretty good for prototyping. I haven't found AI helpful with big picture stuff (design) or nuts and bolts stuff (large refactorings), but it's good at some tedium that I definitely know how to do but guess that AI can type it in faster than I can. Similarly, given enough time I could probably manufacture my designs on a mill/lathe but there is something to be said for just letting the printer do it when plastic is good enough (100% of my projects; but obviously I select projects where 3D printing is going to work). Very similar technologies and there are productivity gains to be had. Did the world change because of either? Not really.
by close04 | 2025-05-28 13:05:03+00:00
At the risk of repeating myself, this is the idealistic take and even that only until you give it the slightest bit of though. Standing by this take after the realistic questions were asked also makes it an ignorant take.

3 million truckers in the US alone. Retire early? To live on what, the wealth accumulated in not even a full lifetime of trucking? Go to school? Who pays for it, who supports the person/family while they go to school, and what are the odds that the skill set increases so drastically that AI/automation won't just catch up with them in a couple of years? "Just" switch professions? If there was a better one they would have done it already, so they can only switch for the worse.
by salawat | 2025-05-28 13:06:10+00:00
Malicious compliance is not the answer here. The system should not be made. Period. It's a primitive kept out of current existence due to it's critical role in providing a foundation for a tyranny. Think about this. The question being asked is to deliver a technical implementation with high reliability to elicit and enforce a signal cross population. It's the wannabe tyrant's wet dream; even cloaked in the sheep's wool of "Think of the Children". We don't either ethically or morally have the right of it to craft these chains. Once done for this test case, it'll be propagated everywhere else.

We don't need it. We shouldn't want it.
by sensanaty | 2025-05-28 13:06:32+00:00
> From my experience so far it is helpful for me to get another opinion on how to solve a problem—and I do the work in the end.

I agree fully, I use it as a bouncing off point these days to verify ideas mostly.

The problem is, and I'm sure I'm not alone in this, management is breathing down my neck to use AI for fucking everything. Write the PR with AI, write the commit message with AI, write the code, the tests, use YOUR AI to parse MY AI's email that I didn't bother proofreading and has 4 logical inconsistencies in 1 sentence. Oh this simple feature that can easily be done for cheaper, quicker and easier without AI? Throw an AI at it! We need to sell AI! "You'll be left in the dust if you don't adopt AI now!"

It comes back to my point about there being 2 camps. The one camp actually uses AI and can see their strengths & weaknesses clear as day and realizes it's not a panacea to be used for literally everything, the other is jumping headfirst into every piece of marketing slop they come across and buying into the false realities the AI companies are selling them on.
Show HN: Ts-migrating – Progressively Upgrade tsconfig.json
by ycmjason | 2025-05-28 13:07:20+00:00
I built @ts-migrating to help you "progressively" migrate tsconfig settings (more specifically compilerOptions) without doing it all at once.

It's a TypeScript Language Service plugin. Once installed, your IDE will start showing errors based on your new tsconfig settings.

You can suppress these errors using a special comment, @ts-migrating.

It also comes with a CLI. For example, `ts-migrating annotate`, which finds and annotates all current violations. This lets you enable the new tsconfig immediately while preventing new violations from being introduced.

From there, you can fix the suppressed errors over time at your own pace.
by clutter55561 | 2025-05-28 13:07:21+00:00
A lot of the discourse around AI, and LLMs specifically, suffer terribly from FOMO and cognitive biases such as confirmation bias and anthropomorphism. The fact that AI/LLMs are commercial concerns makes it even more difficult to distinguish reality from bullshit.

I’m not a LLM user myself, but I’m slowly incorporating (forcing myself, really) AI into my workflow. I can see how AI as a tool might add value; not very different from, say, learning to touch-type or becoming proficient in Vim.

What is clear to me is that powerful tools lower entry barriers. Think Python vs C++. How many more people can be productive in the former vs the latter? It is also true that powerful tools lend themselves to potentially shitty products. C++ that is really shitty tends to break early, if it compiles at all, whereas Python is very forgiving. Intellisense is another such technology that lowers barriers.

Python itself is a good example of what LLMs can become. Python went from a super powerful tool in a jack-of-trades-master-of-none sort of way, to a rich data DSL driven by Numpy, Scipy, Pandas, Scikit, Jupyter, Torch, Matplotlib and many others; then it experienced another growth spurt with the advent of Rust tooling, and it is still improving with type checkers, free threading and even more stuff written in Rust - but towards correctness, not more power.

I really do hope that we can move past the current fomo/marketing/bullshit stage at some point, and focus on real and reproducible productivity gains.
by pvg | 2025-05-28 13:08:12+00:00
If I had a coworker who made a random insult machine

Nothing of the sort happened, though? Why even make this gigantically escalatory analogy? You don't have to like the work presented and you still have the option of non-yelly critique or saying nothing. You're acting like you've done the work of persuasion for your position and everyone is or should be as incensed as you are. And that's clearly not the case.
by bluGill | 2025-05-28 13:09:04+00:00
I have hundreds of tests that take 15-30 mintues each. These tests tend to be whole system tests so there is no way useful way to say it won't touch your change (75% will). Despite an extensive unit test suite (that runs first) these tests catch a large number of real production bugs, and most of them are things that a quicker running test couldn't catch.

Which is to say that trying to avoid running tests isn't the right answer. Make them as fast as you can, but be prepared to pay the price - either a lot of parrell build systems, or lower quality.
by rimunroe | 2025-05-28 13:09:30+00:00
> I have always wondered why Windows never had a unified installation, update, and uninstall framework like MacOS had from the start. It seems like an obvious omission that was never solved.

I was shocked when I switched to macOS. I couldn’t believe how much better the typical install experience was compared to Windows. Just drag the downloaded file into a folder. No need to run some bespoke install wizard. Even when applications did need to run something to install, it was almost always just the same (presumably system-provided) install flow.