MurphyA/hacker-news huggingface dataset:
by throw1235435 | 2026-01-13 10:04:47+00:00
> They are laughing at them.

Yes but not for the reason you think - more that those are the future customers. If you look closely most are pivoting slowly away from software and shifting more to AI + hardware. The slow layoffs and pivoting that capital to infra shows this. All that "vibed" software needs to run somewhere. Also the models that generate and also power all that software need compute which comes from somewhere.

If I can:

- Have large margin compute since GPU's, power, data centre, etc setup is expensive AND

- Models that outperform models you can have at home.

- Vibed software that derives a lot of functionality from the AI compute and wants to be hosted on compute.

The big companies are pivoting away from software to being more infrastructure like for the democratized software that is projected to be made. They will be fine but in 10 years they will be more cloud hyperscalers, AI compute agents, etc than software businesses. Any software they write will be more to package up their compute as higher margin products.

None of this IMV gives any hope to current SWE's.
by bob1029 | 2026-01-13 10:06:00+00:00
The fastest way to eliminate fear is to practice. I had the team go through it one day. They didn't get a choice. I locked us on a screen share until everyone was comfortable with how rebasing works. The call lasted maybe 90 minutes. You just have to decide one day that you (or the team) will master this shit, spend a few hours doing it, and move on.

Rebase is a super power but there are a few ground rules to follow that can make it go a lot better. Doing things across many smaller commits can make rebase less painful downstream. One of the most important things is to learn that sometimes a rebase is not really feasible. This isn't a sign that your tools are lacking. This is a sign that you've perhaps deviated so far that you need to reevaluate your organization of labor.
by tomaytotomato | 2026-01-13 10:06:51+00:00
Github is not Git but I find the Squash and Merge functionality on Github's Pull Request system means I no longer need to worry about rebasing or squashing my commits locally before rebasing.

At work though it is still encouraged to rebase, and I have sometimes forgotten to squash and then had to abort, or just suck it up and resolve conflicts from my many local commits.
by aebtebeten | 2026-01-13 10:06:52+00:00
Wow; I think the O.C. has jumped the shark.

(again, this sounds like a good argument to have multiple parties, but good luck getting anything like that off the ground. I wonder how many primaries are open? With a closed primary, I'd think a "center party" might actually appeal to those who are getting whipped to the edges — if there are any of them left, that is)
by kennykartman | 2026-01-13 10:07:05+00:00
I wonder what you consider a successful language.

Rust appeared in 2012. Zig in 2016. I consider them both two successful programming languages, but given they are only 4 years apart, it's easy to compare Zig today with 4-years-back Rust and see they are very far apart, in term of maturity, progress, community size and adoption.

Rust is a very successful language so far, but expecting that in 10y it can overthrow C++ is silly. Codebases add up more than they are replaced.
by silvestrov | 2026-01-13 10:07:40+00:00
I can baffle you even more: if you register your company in Delaware, you don't even need to specify who owns the company.

You only need to specify the name and address of the registered agent, which is sort of a "contact person", not somebody who works for the company.

https://www.delawarebusinessincorporators.com/blogs/news/can... and https://velawood.com/anonymity-in-delaware/
by isaaksmart | 2026-01-13 10:07:50+00:00
Hi HN,

I built Jangoro because I noticed a recurring pattern in the startups I worked for: we would spend months building features based on a single loud customer or a "gut feeling," only to forget a year later why we made that choice or if it actually moved the needle.

Jangoro is a "Decision Accountability System." It essentially acts as a git log for your product strategy.

The Tech Stack:

ReactJS/Remix
NodeJS/Express
DynamoDB
SQLite

I’m using Gemini-2.5 to handle the sentiment analysis of the survey data, but I’ve focused heavily on the "Revenue Weighting" logic to ensure the data is grounded in financial reality, not just word clouds.

What I’d love feedback on:

The Logic: Does the "Customer Truth Graph" make sense to you from a data perspective?

Privacy: Right now, I handle data by manual CSV uploads to an SQLite DB. Is this a dealbreaker for your team?

Use Case: Does your team actually record why you don't build things?

It’s early days and there are definitely some rough edges. I’ll be here to answer any technical questions about the implementation or the data model.
by TrackerFF | 2026-01-13 10:07:59+00:00
I used to import a lot of stuff from the US to Norway. I lived all the way up in northern Norway, so parcels would take roughly 5 working days from Oslo to where I lived.

Domestic overnight mail / express mail was prohibitively expensive, something equivalent to $150 for small items.

However, if I ordered something via USPS International Express, those items would automatically be shipped as overnight / express mail once inside Norway, and handed to the Norwegian postal system. A parcel from New York to where I lived would take 2-3 working days, and as a bonus, USPS Int'l Express only cost around $50 for the same size parcel!

So while not the same type of arbitrage as OP posted about (where items become cheaper due to free shipping), I could save a lot of time and money.

Maybe a more extreme example would be the ultra cheap shipping prices from China. You paid like $1 in shipping, which would have cost $10 if you bought the same service domestically.

IIRC, the root of these practices go back many, many decades. And has a been a thorn on the side of modern shipping ever since Chinese e-commerce exploded.
by spwa4 | 2026-01-13 10:08:32+00:00
I highly doubt that in Iran half the population supports the government. If you hear Iranians it's more like 5%. Even if it's really double that, that's still only 10%.

Plus after wars the mullahs wanted that ended in total disaster and enormous numbers of casualties (given that the central promise of islam, of allah if you will, is military success), whilst the mullahs never had real support of the Iranian army, there are now reports of a lot of individual soldiers and even one or two of entire units attacking mullahs and religious schools, killing teachers and students. Oh, and after the recent "success" against Israel, the mullahs once again cut military pensions, with now reports they just stopped paying entirely. Given that it's the military doing the planes, one wonders that if the "supreme leader" runs to a plane if he'd make it on board the plane without a bullet. The government only has the basiji, the "religious army" (technically their name means mobilization of the oppressed, a reference to Marxism, and to who brought the mullahs to power. Of course in practice the basiji is anything but what their name implies, they are the oppressors).
by tvali | 2026-01-13 10:08:46+00:00
Compare this to modern system: we could fully simulate this kind of slow computer in real time, I would guess, with all the wheels, clockwork and mechanics as well as logic circuits with full electricity. Deciding the simulation level would be a bit challenging - is this an atomic, an electron or more common sense simulation -; still I think the simulation would work as well as this kind of document.
by nake89 | 2026-01-13 10:08:48+00:00
I have not had the same experience. I pay 10 dollars a month for GitHub Copilot, where I get to use Claude Sonnet 4.5.

I tried the same with OpenRouter and I used up 2.5 dollars in a day using Sonnet 4.5. Similar use on copilot has could maybe make me use 10% of my quota (and that's being generous for OpenRouter).

I think GitHub Copilot is way more affordable than OpenRouter.
by PxldLtd | 2026-01-13 10:09:38+00:00
I'm sorry but this is factually incorrect and I'm not sure what experts you are referring to here about there being concensus on this topic. I would love know. Geoffrey Hinton, Demis Hassabis, and Yann LeCun all heavily disagree with what you claim.

I think you might be confusing creation ex nihilo with combinatorial synthesis which LLMs excel at. The proposed scenario is a fantastic testcase for exactly this. This doesn't cover verification of course but that's not the question here. The question is wether an already known valid postulate can be synthesized.
by 72deluxe | 2026-01-13 10:10:07+00:00
But when Apple released macOS Snow Leopard (widely held to be great), it announced 0 new features over Leopard, to much applause. It focused exclusively on fixing issues, and was better for it.

Journalists will report whatever they get fed anyway (notice how they all talk gleefully over the wobbly new iPhone with a jutting-out camera bump when only a few years ago they talked gleefully about how flat the iPhone was, and then gleefully wrote about how their screen estate was invaded by a notch etc), so if Apple focused on fixing issues instead of short-attention-span apps (when was the last time you used "Image Playground"?) the media could report how committed to reliability and quality Apple is, gleefully.
by eru | 2026-01-13 10:10:25+00:00
If you want to subsidise these unfortunate people, please just do so openly. Don't be all sneaky, sneaky about it by banning accurate risk assessments.

In any case, what you are saying is only true, if you buy your health insurance second to second on the spot market.

Insurance companies are more than happy to enter long running contracts, where you both agree today on (the algorithm for) the premiums for the next twenty years or even until the rest of your life. That's pretty common with life insurance and disability insurance already.

The above already exists, but if you allow some speculation: you could even envision people buying insurance for their kids before conceiving them. That way you don't have to worry about pre-existing conditions.

(Well, if the parents already have heritable conditions that would make the kids more likely to have expensive medical problems, those would push up their premiums. But then: perhaps these people should think twice about burdening a potential kid with these issues.

Compare how in Cyprus where sickle cell anemia is prevalent, even the Catholic church demand you get screened, before they'll marry you.)

If you really want specialised in-kind welfare, you can get people a voucher for the catastrophic version of 'unconceived baby insurance'.

Basically, you can buy insurance against insurance premiums being expensive.
by netsharc | 2026-01-13 10:10:28+00:00
It's probably Microservices(TM)... The black box responsible for rendering the HTML is some other black box to the UI or whatever. The UI offers you locale options, but the renderer that fetches video titles hasn't been configured to respect this, probably uses locale from geolocation and some overpaid genius said "always use machine translation if locale doesn't match video title language"...

The homepage of google.com is also localized. I remember noticing that even when requesting and getting the English locale, the tooltip for the doodle was still in my region's language... wahey!
by river_otter | 2026-01-13 10:11:02+00:00
Once you are attached to an agent session, correct it's just tmux! aoe does:
- gives you one screen that shows you all of your agents and shows you which one s are waiting for you to attach to them and give them a new task or answer a question

- Easy git worktree integration to help you manage branches when running multiple agents in parallel on the same repo.

I also plan on adding a lightweight docker sandbox integration to help give you the option to sandbox a session when you run it (but that part isn't ready yet)
by flanked-evergl | 2026-01-13 10:12:39+00:00
It's so strange. There is a real place on Earth which is much more brutal and oppressive than the wildest fantasy that Margaret Atwood could come up with. A place that rapes virgins before executing them to prevent them from entering heaven, a place that uses sexual violence and mutilation to control women, but if anyone mentions this place or the atrocities occurring there, then a certain element in the west gets incredibly upset and tries to divert attention away from it back to some US domestic local news interest stories. Almost like they are jealous or something.

Someone told me with a straight face once that we will one day come to see The Handmaid's Tale as a documentary and not just a novel. A statement that one can only make with a straight face if one is incredibly ignorant of the world.

I'm sure these US domestic pet peeves will exist even if some attention is given to the mass atrocities occurring in Iran. Not every local interest story in the US has to become international news. We really don't care.
by ewavonhowie | 2026-01-13 10:12:40+00:00
Howie | Senior Engineer (AI Search / RAG) | Vienna / Remote (EU)
Early-stage AI startup in AEC (building architecture), live product, EU/UK customers, backed by Pi Labs & DAR.

Looking for a hands-on senior engineer to own AI search & retrieval in production (Python, RAG, vector DBs, cloud). Strong bias to shipping.

Salary + meaningful ownership.
Apply: ewa@howie.systems (ewa- i am a founder&CEO, team 6 FTE atm, raising seed now and growing)
https://howie.systems
Full JD: https://bit.ly/4prjMTJ
by orwin | 2026-01-13 10:12:50+00:00
Ideally you only rebase your own commit on your own feature branch, just before merging. Having a clean commit history before merging make the main branch/trunk more readable.

Also (and especially) it make it way easier to revert a single feature if all the relevant commits to that feature are already grouped.

For your issue about not knowing which branch the commits are from: that why I love merge commits and tree representation (I personally use 'tig', but git log also have a tree representation and GUI tools always have it too).
by eru | 2026-01-13 10:13:30+00:00
> We know that from observing evidence such as how much the government pays out in welfare to Wal-Mart employees.

That's a weird metric. If tomorrow Wal-Mart laid off all employees and replaced them with robots, they would surely be worse off, but by your metric Wal-Mart would look less evil?

> Customers continue shopping there because human beings are typically incapable of accepting a short-term loss (higher price) for a long-term gain (product lasts more than three uses).

Groceries typically only last one use.
by vee-kay | 2026-01-13 10:14:34+00:00
I use an Amazon FireTV Stick on my old non-smart LG TV. And the advantage is that the FireTV has a simple cute little remote control device. There is a nifty Setting in the Amazon FireTV UI to allow its remote to turn on/off the TV too.

So it's been a long time since I had to wrestle with the TV's built-in OS.

I just use the pleasant UI of the FireTV Stick to watch Netflix, Prime, Disney+, etc. on that decade+ old TV. That FireTV becomes sluggish if I keep multiple apps open, so I have learnt to exit out of an app before switching to the new one.

I may get a new FireTV stick this year, rather than splurging for a new TV, since the old TV is still doing well.

As the Americans say:
If it ain't broken, don't fix it.
by psychoslave | 2026-01-13 10:14:55+00:00
That’s also because there are multiple concerned that are tried to be presented as the same exposed output through a common feature. Having one branch that provides a linear logical overview of the project feature progression is not incompatible with having many other branches with all kind of messes going back and forth, merging and forking each other and so on.

In my experience, when there is a bug, it’s often quicker to fix it without having a look at the past commits, even when a regression occurs. If it’s not obvious just looking at the current state of the code, asking whoever touch that part last will generally give a better shortcut because there is so much more in the person mind than the whole git history.

Yes logs and commit history can brings the "haha" insight, and in some rare occasion it’s nice to have git bisect at hand.

Maybe that’s just me, and the pinnacle of best engineers will always trust the source tree as most important source of information and starting point to move forward. :)
Show HN: Watchfolio – TV show ratings as stock market charts
by abishekvenkat | 2026-01-13 10:15:09+00:00
A tool that visualizes TV episode ratings as candlestick charts. Each episode is a candle - green if the rating went up from the previous episode, red if it dropped.

Search any show and instantly see its "quality trajectory" over time. Built with Next.js and TradingView's charting library, data from SeriesGraph.com/TMDB.
Ask HN: What's the best solution to query a code repository as of today?
by epolanski | 2026-01-13 10:15:12+00:00
Like many, I'm finding a great deal of utility in Claude Code.

Even ignoring its capabilities in authoring code, which I don't particularly care for, one of the most useful aspects of the tool is researching information in a codebase, connecting the dots and extracting information about the whats, wheres and whys.

This capability is helping me a lot into refining tasks I get assigned to find edge cases, assess their impact or simply learn about the product.

I want to scale this and put this power in the hands of my PMs and POs with a predefined "functional analyst" prompt to help them refine tasks and do this work instead of me (as they are the domain experts or close to them).

Right now the closest I could get into a working product is essentially a Claude Code wrapper, but it's not a solution that scales and I'm particularly fond of.

Access to MCP on the local machine would be also an added bonus.

Anybody has a solution in this space? Possibly open source, but I could consider something like that "as a service".
by fc417fc802 | 2026-01-13 10:15:37+00:00
I agree but I think git got the distributed (ie all nodes the same) part right. I also think what you say doesn't take it far enough.

I think it should be possible to assign different instances of the repository different "roles" and have the tooling assist with that. For example. A "clean" instance that will only ever contain fully working commits and can be used in conjunction with production and debugging. And various "local" instances - per feature, per developer, or per something else - that might be duplicated across any number of devices.

You can DIY this using raw git with tags, a bit of overhead, and discipline. Or the github "pull" model facilitates it well. But either you're doing extra work or you're using an external service. It would be nice if instead it was natively supported.

This might seem silly and unnecessary but consider how you handle security sensitive branches or company internal (proprietary) versus FOSS releases. In the latter case consider the difficulty of collaborating with the community across the divide.
by menaerus | 2026-01-13 10:15:55+00:00
> That does not apply here. Because more often than not, we don't prescribe products/services that our clients must go out and buy, without exception.

You know that treating patients is not only about picking the right medicament and writing prescriptions? It's about diagnosing, testing the hypotheses, optimizing for the particular patient case, learning about all the specific factors of their environment including the genetics, then we have surgeons, etc.

And yet I don't quite see doctors being on a time spending spree to become exquisite in all of those things. Nor do I see hospitals or clinics doing such knowledge and ability harness tests over their potential employees. Stakes are much higher in medicine than they are in software so it makes no sense at all to make an argument that doctors cannot "afford" it. They can, they have books and practice the same way we do. I don't get to modify the production system every day but yet I am learning constantly of how not to make those same production system go down when I do.

> It is not a normal thing to expect because in other fields there are few people who can afford to do that.

It's not a normal thing in software too, you know? Let's please stop normalizing things which are not normal. If there is one thing that makes me happy in this new era of AI-assisted development is that all this bs is coming to its end.
by OlaProis | 2026-01-13 10:16:14+00:00
Great point about sharing the 'how' not just the 'what'. I'll consider adding prompt history or a development log showing the AI interactions, just have to figure out how to present all the data i guess. The commit messages could definitely include more context about what was requested vs generated. Thanks for the thoughtful framing,'open weights vs open source' is a useful distinction
by eru | 2026-01-13 10:16:48+00:00
Other search engines exist. Bing is right there, and Microsoft is more than willing to eat the high cost of entry and infrastructure cost.

> It should be a regulated utility like electricity or railroads, we should have a public alternative like the post office is to UPS, or it should be nationalized.

I agree that electricity and railroads should be regulated like Google Search.

It's really weird that snail mail in the US is a government monopoly. When even social democratic Germany managed to privatise them.

> The situation gets more dire when you consider their browser monopoly.

Don't a lot of people in the US use iPhones? They don't ship with Chrome as the default browser, do they?

(And yes, Safari is built on top of the same open source engine as Chrome. But you can hardly call using the same open source project a 'monopoly'. Literally anyone can fork it.)

There's also plenty of other browsers available.
by OlaProis | 2026-01-13 10:17:58+00:00
the line is blurry for shure. Code generated by a closed-source compiler (or LSP) is still 'your' code. Maybe the difference is whether humans can reproduce and learn from the process? With traditional code, you can read commit history and understand the author's thinking. With AI-generated code, that context is lost unless explicitly shared. Food for thought.
by river_otter | 2026-01-13 10:18:06+00:00
THIS!!! I'm right there with you. Imo, using aoe (or whatever tool you can find for session management) is the key unlock to help give us all the patience to try out the ollama/lmstudio/mlx providers to see how they really perform. We're lacking information about what work is really being done with local coding models, at least somewhat because imo most github open source repos don't ask you to share what LLM you used to help you, and they should.

We need to start sharing our specific success and failure stories from using local llms for coding
by lightningspirit | 2026-01-13 10:18:12+00:00
If you do `new Date('2025-11-31T00:00:00Z')` you get `2025-12-01T00:00:00.000Z`, which is weird and potential cause for bugs when parsing date string from input. Right because of these inconsistency I created a small package backed as Regex to validate Date string input before throwing it on `new Date(stringDate)`.

https://www.npmjs.com/package/iso-8601-regex
by piker | 2026-01-13 10:18:44+00:00
> You can make a vast majority of the population "pending charge" at some point if you take into consideration they were - at one point - marked "pending bench warrant" during the time between getting a traffic ticket and (A) paying it; or (B) fighting it.

This statement is incorrect. A "charge" means charged with a crime. You cannot make anyone "pending charge" if you issue them a bench warrant. Nor an arrest warrant.

Charging someone is a different procedure.