MurphyA/hacker-news huggingface dataset:
by MrJohz | 2025-09-01 08:18:58+00:00
I think the word "later" is unhelpful in this situation because it implies all sorts of different timescales. You don't want to be resolving merge conflicts three weeks after you've created them, you're right!

Typically for me, "later" means "immediately after the rebase command has finished", which is very similar to git's "while the rebase command is running", but has some subtle and important differences.

For example, because the rebase completes first, I get to see roughly what the end-state of the rebase is before I start doing the hard work of fixing conflicts. This is useful as a sanity check - sometimes the reason I'm getting a bunch of merge conflicts is because I was rebasing the wrong things in the first place and included an extra commit somewhere. Seeing the result first gives me the chance to sanity check what I'm doing.

Another thing is that my repository is never in a broken state where I can't continue doing other things. There's no way in git to stash a rebase, say because I've realised a different approach might work better or just because I urgently need to work on something different. I either need to cancel the rebase and start it again later, or keep on going until it's over. In jj, because the conflicts are automatically checked in as part of the commits, I can easily jump backwards and forwards between the work I'm doing resolving my conflicts, and anything else.

Another way of thinking about it is that git is very modal. You check out a branch and are in the "branch" mode, and then you start a rebase and are in the "rebase" mode, and then you do a bisection and are in the "bisect" mode - it's difficult to move freely between these modes, and there's certain things you can only do in some modes and can't do in others. In contrast, jj has exactly one mode: "there is a commit checked out". The different operations like rebasing all happen atomically, so you never see the halfway state. But because things like conflicts can be encoded in the commit itself, you still have all the same power that the modal approach had, just with a simpler conceptual model.
by latexr | 2025-09-01 08:19:26+00:00
> My coding has transitioned from coder to code reviewer/fixer vey quickly. Overall I feel like it's a good thing

Until you lose access to the LLM and find your ability has atrophied to the point you have to look up the simplest of keywords.

> the last few years of my life has been a repetition of frontend components and api endpoints, which to me has become too monotonous

It’s a surprise that so many people have this problem/complaint. Why don’t you use a snippet manager?! It’s lightweight, simple, fast, predictable, offline, and includes the best version of what you learned. We’ve had the technology for many many years.
by pampa | 2025-09-01 08:19:32+00:00
I didn't think that there was something wrong with my git workflow, or that git was complicated. I switched from darcs as my primary VCS to git around 2007. I was skeptical about jj at first but gave it a try. Did not look back ever since.

My impression is, that git is ok for managing shared history. And thats what i was using it for mostly. But jj added another whole dimension for managing my work in progress, different paths of code that i am working on in the moment. jj made it almost frictionless. I did not know I was missing it, but i'm not going back.
by sfn42 | 2025-09-01 08:20:32+00:00
That's not a problem in a well designed ASP.NET project. Just create a new web API project, move a controller into it and copy/paste the necessary boilerplate into Program.cs, set up config etc for it and configure cicd to deploy it separately, there you go. Less than a days work.

You can also publish libraries as nuget packages (privately if necessary) to share code across repos if you want the new app in it's own repo.

I've worked on projects with multiple frontends, multiple backbends, lots of separately deployed Azure functions etc, it's no problem at all to make significant structural changes as long as the code isn't a big ball of mud.

I always start with a monolith, we can easily make these changes when necessary. No point complicating things until you actually have a reason to.
by kathir05 | 2025-09-01 08:20:53+00:00
I was referring to our "Show HN" post, which we did it last week. It just had link to our site huntyourtribe.com.

In this ASK HN post, we thought we have to add little context about huntyourtribe.com, because we really have no clue why our last week Show HN post didn't showup in public page. If we see "new and novel approach" as marketing heavy then, happy to remove that as well.
by theshrike79 | 2025-09-01 08:22:09+00:00
This, to me, feels like you're complaining to the 45 year old builder that they should be using a hammer instead of a nail gun.

I know how to nail a nail, I've nailed so many nails that I can't remember them all.

My job is to build a house efficiently, not nail nails. Anything that can make me more efficient at it is a net positive.

Now I've saved 2 hours in the framing process by using a nail gun, I have 2 extra hours to do things that need my experience. Maybe spot the contractor using a nail plate in the wrong way or help the apprentice on their hammering technique.
by hiAndrewQuinn | 2025-09-01 08:22:51+00:00
I like the resume pool approach as well, yes.

Perhaps the future will be people of various talents and ability levels first applying to various resume pools, which job offerers then use as a first pass filter for high quality candidates. Then down the line these same candidates, if they do apply for a new job directly, might list "I belong to So-and-so Pool" as a line item to separate themselves from the pack even among job offerers who don't actually dip into that pool. Not entirely unlike working at FAANG today, to open up interesting new positions tomorrow.
by franga2000 | 2025-09-01 08:22:52+00:00
In practice the opposite happens - when new technical workarounds are popularized, more technical solutions are found to prevent them and legislation is proposed to mandate them.

Look at Chat Control in the EU: they started with mandating server-side scanning. Nobody liked that so everyone implemented E2EE. Now there's a new law that adds mandatory client-side scanning.

Most of my tech-brained friends are saying "whatever, we'll just compile from source or use alternative means of distribution. But is that becomes popular, what's the next step? I'm fully expecting the EU's to then try to mandate the service providers need to ensure their apps aren't tampered with, which can only be done by locking devices down to official means of distribution and implementing end-to-end cryptographic attestation. Then we truly are out of options.
by safety1st | 2025-09-01 08:23:11+00:00
Only competition can provide a solution. We have lost sight of this principle even though all Western democracies are built on the idea of separation of powers, and making it hard for any one faction of elites to gain full control and ruin things for everyone else. Make them fight with each other, let them get a piece of the pie, but never all of it. That's why we have multiple branches of government, multiple parties etc. That's why we have markets with many firms instead of monopolies.

There has never been a utopian past and there will never be a utopian future. The past was riddled with despotism and many things that the average man or woman today would consider horrific. The basic principle of democratic society is to prevent those things from recurring by pitting elite factions against each other. Similarly business elites who wield high technology to gain their wealth must also compete and if there is any sign of them cooperating too closely for too long, we need to break them up or shut them down.

When Apple and Google agree, cooperate, and adopt the same policies - we are all doomed. It must never happen and we must furthermore break them up if they try, which they are now doing.
by account42 | 2025-09-01 08:23:12+00:00
In some cases it is hidden though. USB has a lot of "generic" device classes where (at least in theory) the OS only needs to deal with a standardized interface and whatever actual hardware is behind it is driven by an embedded controller.

It's just that most internal hardware initially only cares only about Windows (or only Linux) so it makes more financial sense to develop a more complex driver than a complex firmware. The equation might change later on but by then you are stuck with the hardware design.
by mtlmtlmtlmtl | 2025-09-01 08:23:25+00:00
As a player I like to think of sharpness as a measure of the potential consequences of a miscalculation. In a main line dragon, the consequence is often getting checkmated in the near future, so maximally sharp. In a quiet positional struggle, the consequence might be something as minor as the opponent getting a strong knight, or ending up with a weak pawn.

Whereas complexity is a measure of how far ahead I can reasonably expect to calculate. This is something non-players often misunderstand, which is why they like to ask me how many moves ahead I can see. It depends on the position.

And I agree, these concepts are orthogonal. Positions can be sharp, complex, both or neither. A pawn endgame is typically very sharp; the slightest mistake can lead to the opponent queening and checkmating. But it's relativity low in complexity because you can calculate far ahead using ideas like counting, geometric patterns(square of the pawn, zone of the pawn, distant opposition etc) to abstract over long lines of play. On the opposite side, something like a main line closed Ruy Lopez is very complex(every piece still on the board), but not especially sharp(closed position, both kings are safe, it's more of a struggle for slight positional edges).

Something like a king's indian or benoni will be both sharp and complex. Whereas an equal rook endgame is neither(it's quite hard to lose a rook endgame, there always seems to be a way to save a draw).
by raxxorraxor | 2025-09-01 08:24:43+00:00
It is of high financial interest of Netflix. I killed my subscription because they couldn't support my sensibly configured browser.

I often recommend people to kill their subscription as well because of this fact. Netflix just isn't oriented to improve their service for their users and it shows.

It won't hit any of their KPI or metrics, but their shitty behavior has a real effect. That said, most other alternatives suck as well. Killed Paramount almost immediately, can't remember why I left Disney. I think there were similar issues.
by griffzhowl | 2025-09-01 08:24:49+00:00
> It goes what step further, there are statements that are true but can not be proved.

No, this is the misconception. I know it's often stated this way, but it's wrong. Godel showed that given any formal system, you can construct a statement that the system can neither prove nor disprove. But Godel actually proves this statement in his proof, so it's certainly not unprovable in general.
by encody | 2025-09-01 08:25:11+00:00
I think I'm using it wrong.

I'm using Zed as my editor, and maybe 18 months ago I upgraded my system. I didn't miss the AI autocomplete at the time, so I didn't bother to set it up again. However, around two weeks ago I figured I'd give it another go.

I set up GitHub Copilot in Zed and... it's horrible. It seems like most of its suggestions are completely misguided and incorrect, usually just duplicating the code immediately above or below the cursor location while updating the name of a single identifier to match some perceived pattern. Not remotely close to what I'd consider useful; I'm definitely a faster & better programmer without it.

I also tried setting up some local models on ollama: I kept getting random tokens inserted that seemed to be markup from the model output that Zed didn't know how to parse. (On mobile rn, will post sample output when I am back at work if I remember to.)

Is paying Anthropic an arm and a leg for the privilege of granting them first-party access to train on my user data really the competitive move as a modern developer?

P.S. I know Zed has their own AI (and it seems like it should be really good!), but when they first introduced it, I tried it out and it immediately consumed the entire free tier's worth of credits in just a few minutes of normal coding: suggestions are proactively generated and count against your account credit even if not accepted, so I didn't really feel like I'd gotten a good sense of the tool by the time the trial ran out. Even if it's really good, it burns through credits extremely fast.
by franga2000 | 2025-09-01 08:27:08+00:00
That's not a good reason not to allow it, it's a good reason not to support it. If I do that and complain to Nintendo support about overheating, they can tell me to fuck off. Worst case it should give a scary popup saying "your dock isn't actively cooled so your device is likely to overheat". Absolutely no excuse for not allowing third-party docks though.
by SideburnsOfDoom | 2025-09-01 08:27:15+00:00
> It's going to be released approximately in November

That's literally what I said, yes. The track record is very punctual so far, so "in the first half of November" is highly likely.

> the first RC is probably going to be released within the next few weeks

I made a statement about the way that things factually are at present. No less, no more. You characterised .NET 10 as a supported version, and this is not currently true.

> Now is the time to upgrade to 10, do some testing and then deploy once 10 is released.

Really "Now" ? or "probably within the next few weeks" when there's a version that is somewhat supported?

My employer is not in the habit of deploying 2 months after the work is done. Nor are they in the habit of prioritising this pre-release over other more important work. They love .NET LTS releases when they are releases, but absolutely will not put a pre-release on production, no matter if it's "supported" in some sense.

LTSs are for people or companies with low appetite for this kind of risk, or who have contractual obligations to not be running unsupported or pre-release software. Preview 7 is by definition not release quality yet, as it's not the release.

I expect .NET 10 to get picked up by my employer in the new year. This is based on my experience with the update to .NET 8

Your way does seem to better in that you have capacity to trial pre-releases, but the long release cycle sounds sucky.
by masfoobar | 2025-09-01 08:28:07+00:00
With the behaviour Nintendo has been 'in the last few years' - I no longer will purchase Nintendo consoles.

We purchased a Switch and the kids have enjoyed many games on it. After reading other comments on here, I am surprised my Switch has not been bricked - and I am not doing anything dodgy at all.

As for the Switch 2. I was showing the announcement videos with the kids - they did not look excited for it. As for me, I was smirking when they were not revealing the price of the console and games. I knew something was up. Within hours there were angry youtube channels blasting their prices.

I am not even getting into Nintendo's legal behaviours over ROMs, youtube channels, or games like Palworld.

"Oh.. that thing you do in this game... Yeah... we have a patent for that!"

Of course, every game Nintendo creates are completely new ideas. Sure, I give Nintendo credit with their involvement in video game history - but I am sure "new features" in Mario Kart World are inspired from other games..... but if you do something Nintendo consider is their idea (especially patented) - they will throw money at you *towards their legal department*

Nintendo are not a family-based games company. They lost that title some time, now. Unless they really change their ways, I wont buy Nintendo again. I do not support their practices. Sure we might not have Mario Kart World or Zelda or other Nintendo specific titles - but a decent PC have many, many great games of the last 30 years - and they will run faster, smoother, etc.

This Dock <--> USB-C drama is just laughable.
by gus_leonel | 2025-09-01 08:29:05+00:00
> I'll never see an earth-rise

You wouldn't see one even if you were on the Moon, which doesn't rotate with respect to the Earth. (In the spirit of your comment, you can satisfy yourself about this intuitively by reflecting that we always see the same face of the Moon, so somebody on that face wouldn't see the Earth changing position in the sky, either.)
by flohofwoe | 2025-09-01 08:29:28+00:00
Rust isn't exactly famous for its fast build times. It's probably the only language that actually builds slower than C++, which is an impressive achievement on its own ;)

And give Rust one or two more decades and it will be the same messy kitchen sink language as C++. If anything, Rust is speedrunning C++ history (with the notable exception of fixing static memory safety of course).
by theothertimcook | 2025-09-01 08:29:58+00:00
You’re probably not wrong.

Even the later blackberry phones like the priv and keyOne kinda sucked.

The unihertz phones seemed like a genuine attempt but lacked proper support and flagship polish.

The minimal phone looks cool but reviews aren’t great.

At this point I think your best bet is a clicks keyboard, at least when the novelty wears off you’re not stranded with useless, insecure e-waste. Well, less than a dedicated second device.
Ask HN: Another AI agent, this runs CRM follow‑ups (200msg in prod). Worth it?
by ebenes | 2025-09-01 08:29:59+00:00
I’m a software developer hacking on a proof‑of‑concept for a friend’s sales agency. The idea is a lightweight agent that plugs into their existing CRM (AgencyZoom) and handles repetitive lead follow‑ups.

It’s already running in production in a semi‑automatic way (every action still goes through human approval). So far the system has sent about 200 texts. Too early to measure impact, but it’s been enough to see interesting behavior.

=== How it’s built:

Almost stateless: core data lives in the CRM, with SQLite for caching / minimal state. Written in Typescript, using a lot of functional programming. Trying to follow Domain Driven Design patterns, which keep the logic and bounded contexts manageable. Rate limits and random API errors were a pain: solved with higher‑order functions wrapping API calls. Challenges so far:

Prompt tuning: lots of “close but not quite” AI decisions, especially edge cases where I’d act differently as a human. Infrastructure: significantly more code around state, retries, and API integration than around the actual LLM.

=== My question to you:

Does this sound like something worth pursuing further? Is there a genuine gap here, or am I just reinventing existing automation tools?

I’d love to hear perspectives from people who’ve built or used similar systems.
by rickdeckard | 2025-09-01 08:30:04+00:00
> "The Nintendo Switch 2 only ever charges at a maximum of 15 W(as far as I can tell)."

This is already higher than stated in legal EU-compliance documents [0], where the PD-charger is required to not provide more than 12W "in order to achieve the maximum charging speed"

Also interesting[0]: "TV mode requires output power of 54 watts. This is higher than the power requirements for charging given above. This product supports USB PD fast charging and is capable of being recharged by means of wired charging at voltages up to 15 volts"

According to this, the device will obviously only use the 20V/3A mode (=60 watts) for TV mode, and will not utilize it for charging. Whereas the provided charger (NGN-01) also supports a 15V USB-PD mode which MAY be used for charging.

I assume the device will request max. 15V/1A for charging then, adding up to 15W (not sure why they state the charger should not support "more than 12W"). However, I guess at 15V the majority of power in this state is going to the device and not the battery (they only have a single battery-cell which should be charged with 5V. If they want to charge the battery, they could also request 5V/3A from the charger)...

[0] https://www.nintendo.com/eu/media/downloads/support_1/ninten...
by Izmaki | 2025-09-01 08:31:29+00:00
Will the book cover how Ford nearly lost it all in his efforts of improving the manufacturing process and lowering the costs of the Model T? In the end people had enough of the car and wanted something new, but all Ford could produce - arguably really well - was the Model T. The competitors focused their manufacturing process such that they could efficiently reuse components for a handful of years, then they made small changes to make their new models "feel new and exciting", as we see today, which gave them the upper hand when people got fed up of the Model T.

I'm waiting for history to repeat itself with Tesla, but it's not a popular (hi)story to tell. Not as popular as how great an American pioneer Henry Ford was, for sure.
by Someone | 2025-09-01 08:31:34+00:00
> As a result, the last five minutes were played out with neither team's players attempting to score

That’s nothing compared to West Germany–Austria in the 1982 World Cup (linked from that page), where “The game progressively deteriorated to a virtual standstill in the second half” (https://en.wikipedia.org/wiki/Disgrace_of_Gijón)

For weirdness, there is Barbados–Grenada in 1994, where “In the last minutes of regular time, both teams attempted to score own goals” (https://en.wikipedia.org/wiki/Barbados_4–2_Grenada)
by stevekemp | 2025-09-01 08:32:20+00:00
And currently we have the second highest unemployment rate in the EU:

https://yle.fi/a/74-20175260

That said Finland is a lovely country to move to. Raising a child here in particular has meant I really appreciate the support, and services/facilities available. From the daycares, onwards.

Sure the taxes are high, but when you have good public transport, good services, and so on it's hard to resent them too much.
by beagle3 | 2025-09-01 08:33:36+00:00
Thanks. I agree.

My question was referring specifically to the “not paying taxes”. TTBOMK, in all western jurisdiction, sales/vat/etc/income taxes on sales are equal to or higher than those owed on rental income - and op kept repeating (in multiple responses) that misclassifying a rental as a sale is a tax fraud for the seller/original-owner. That makes no sense to me.
by NostraDavid | 2025-09-01 08:33:40+00:00
I use RSS Guard as local RSS feed manager, and I've slapped all my channels in there. No more reliance on "The Algorithm", and I can now see how freaking many channels I actually follow. I can now start cutting into the spammers, those that don't put out content at all, etc.

Also using Firefox with "Youtube-shorts block", which turns a short into a normal video, so I can't start doom-scrolling.

It cut procrastination-times down enough where I now feel I can program again.
by alexvitkov | 2025-09-01 08:34:04+00:00
No, not everything is a trade-off. Some things are just good and some are just bad.

A working permission system would be objectively good. By that I mean one where a program called "image-editor" can only access "~/.config/image-editor", and files that you "File > Open". And if you want to bypass that and give it full permissions, it can be as simple as `$ yolo image-editor` or `# echo /usr/bin/image-editor >> /etc/yololist`.

A permission system that protects /usr/bin and /root, while /home/alex, where all my stuff is is a free-for-all, is bad. I know about chroot and Linux namespaces, and SELinux, and QEMU. None of these are an acceptable way to to day-to-day computing, if you actually want to get work done.
by mrweasel | 2025-09-01 08:34:57+00:00
It's also interesting that the cloud engineer can apparently be both a DBA, network-, storage- and backup engineer, but if you move the same services on-prem, you apparently need specialists for each task.

Sometimes even the certified cloud engineers can't tell you why an RDS behaves the way it does, nor can they really fix it. Sometimes you really do need a DBA, but that applies equally to on-prem and cloud.

I'm a sysadmin, but have been labelled and sold as: Consultant (sounds expensive), DevOps engineer, Cloud Engineer, Operations Expert and right now a Site Reliability Engineer.... I'm a systems administrator.