MurphyA/hacker-news huggingface dataset:
by epolanski | 2026-02-14 10:49:29+00:00
I have the opinion it was well worth it for many reasons.

Not only the agents can complete trivial tasks on their own, leaving us just with reviewing (and often just focusing on the harnessing), but the new setup is very good for onboarding technical and non-technical staff: you can ask any question about both the product or its architecture or decisions.

Everything's documented/harnessed/E2Ed, etc.

Doing all of this work has much improved the codebase in general, proper tests, documentation and design documents do make a difference per se, and it further compounds with LLMs.

Which is my point in any case: if you start a new project just by prompting trivialities it will go off rail and create soups. But if you work on an established and well scaffolded project, the chances of going off rails and creating soups is very small.

And thus my conclusion: just fork existing projects that already do many of the things you need (plenty of them from compilers to native applications to anything really), focus on the scaffolding and understanding the project, then start iterating by adding features, examples and keeping the hygiene high.
Show HN: Klimly – multi-model weather with uncertainty and activity insights
by ailibrarian | 2026-02-14 10:52:24+00:00
We built Klimly to fix the “one-provider” weather problem. It pulls forecasts from 7–8 sources (OpenWeatherMap, WeatherAPI, Tomorrow.io, Pirate Weather, Open-Meteo, Meteostat, plus new MET Norway and Bright Sky/DWD for Europe), reconciles them, and shows where models disagree so you know how confident the forecast is.

What’s inside

Multi-model consensus with confidence scores and spread visualization
Hourly + 7-day forecasts, air quality, pollen, and API usage/health
“What to wear” and “Activity planner” cards generated from the forecast
“Best time outside” and smart alerts (rain, UV, extreme temps)
Mobile-first UI with tight layouts for small screens
City pages (e.g., /cities/kyiv-ua) and lat/lon query support (?lat=50.45&lon=30.52)
Why it’s different

Shows disagreement between models instead of hiding it
Adds high-quality European data: MET Norway (global ECMWF/HARMONIE) and Bright Sky (DWD MOSMIX) — no API keys needed
Lightweight, fast, and free to use
Links

Live: https://klimly.com
by whatsupdog | 2026-02-14 10:53:44+00:00
In 2020 nobody knew what's actually going on. And I don't fault the 43 administration falling for the lies spewing out of the hacks at CDC. But the lockdowns, shutdowns, mask and vaccine mandates followed well into the latter part of 2022 and early 2023. Most of the federal workers fired for not taking the (now proven unsafe) shots happened in 22 and 23.
by lordokami | 2026-02-14 10:54:20+00:00
You are absolutely right. A PWA would probably have given us a much lighter workflow. Instant feedback, hot reload, no deployment cycle, no TestFlight delay. From a purely practical perspective, it would have been more efficient.

But the truth is we wanted to build a native iOS app. It was less about optimizing the workflow and more about the excitement of trying something new. I had never built a native iOS app before, and part of the motivation was simply curiosity and the challenge.

We also wanted to test the limits of Claude Code. That part honestly surprised us. We never had to roll back once. Every issue we ran into we were able to solve remotely through vibecoding. The entire development cycle happened over SSH from a phone, and it held up better than I expected.

Another important reason was offline usage. We generated the audio files asynchronously using ElevenLabs TTS and bundled them into the app so everything worked fully offline. We did not want to depend on a server connection while traveling. Especially in Japan, where you are constantly moving through stations, underground areas, or rural zones, reliability matters.

So yes, a PWA would have been technically cleaner. But this project was driven more by exploration and constraints than by optimizing for the perfect setup. And in that sense, going native was part of the fun.

Now I am working on another app, a multiplayer party game to play with friends, and for that I am exploring a PWA approach using Firebase. And honestly, for this kind of project it works really well.

The development flow is much smoother. Instant updates, no App Store review cycle, easy real time features with Firebase, and the ability to test quickly with friends just by sharing a link. For a social, fast iteration type of product, it makes a lot of sense.

If it gains traction and people actually use it consistently, then I would consider migrating it to native iOS and Android later. Starting as a PWA feels like the right balance between speed, flexibility, and validating the idea before committing to the overhead of native apps.
by snemvalts | 2026-02-14 10:55:11+00:00
In simpler terms - they create an MCP server, essentially an API that the coding agent can call, that can fill in context about previous decisions done by the coding agent earlier in development. Agent equivalent of asking someone who's been working there longer "why is this this way".

This means that the agent will can have context of previous decisions, something that they currently struggle with as they are always starting from a blank slate.
by Marazan | 2026-02-14 10:57:21+00:00
I personally find LLM text exceptionally boring and tiresome to read. It is often incredibly voluminous and filed with trite phrasing that turns a one sentence idea into 3 paragraphs of pablum.

Yes, this has been inspired by a senior management figure in my company posting a clearly LLM assited 500 word slack message that could have been 2 lines.
by bravetraveler | 2026-02-14 10:58:42+00:00
Not to be dismissive, but I had to comment here:

> A $5000 budget would barely suffice to run something like gpt-oss 120b (OpenAI’s open model that is okay at code-writing tasks).

I toy with this model on a $1,200 PC-in-a-shoebox. If/when I ever do want to outsource my work, it does absolutely fine. Snappy, even. Keeps my data local, too.
by CuriousSkeptic | 2026-02-14 10:58:46+00:00
Could your observation be any other way though?

It recognise addiction (limited agency vs influence) and monetisation (economic rewards the primary means to influence behaviour) as problematic. It kind made “doing bad for pay” a premise of the system.

Large pay-checks incentivising bad behaviour is exactly another observable outcome of the same systemic issue.
by rurban | 2026-02-14 10:58:52+00:00
> Instead of debating for years (like other languages), zig just tries things out.

Good

> Worst case you can always rollback changes.

No, you cannot. People will leave in masses. In perl they announced experiments with a mandatory use experimental :feature. You couldnt publish modules with those, or else you are at risk.

This made perl exciting and fresh. Python on the other hand constantly broke API's, and had to invent package version locks and "safe" venv's. Which became unsafe of course.

Languages and stdlib are not playgrounds. We see what came out of it with C and C++ with horrible mistakes getting standardized.
by jimnotgym | 2026-02-14 10:59:01+00:00
I left the building trade in the UK about 20 years ago.

The UK is a damp place! We built one-off- houses. We built exclusively with 'brick and block'. Brick outside (to take the weather), cavity and block inside. Downstairs walls were block. Upstairs walls were studding, unless blocks were required to go up to support roof purlins.

The blocks inside were normally 'dry lined', sheets of 'plasterboard' (what we call drywall) 'dabbed' to the blocks with a plaster-like adhesive. Often these were 'Thermal boards', plasterboard laminated to urethane insulation foam. Plasterboard was always 'skimmed', plastered over with a plaster designed for this. The drying time is much lower than 'wet plastering' on the blocks.

On big spec built sites they were using prefab timber frames instead of blocks for the inner wall. Then they would plasterboard, and just fill the joints (no skimming). This is always considered a lower spec than skimmed walls.
by deanc | 2026-02-14 10:59:16+00:00
I wrote a little about this here [1]. To summarise, the reality of language learning here is that unless you give up your work it's almost impossible to learn - your only opportunities to learn are evening classes which come at a cost of no social life and are completely impossible if you have kids.

It's easy for people to judge, but move here and try it yourself. It's completely different to e.g. France or Spain.

I also don't agree with one of the other commenters. Finnish is objectively more difficult for most people to learn. The materials are poorly developers due to the population size, and the grammar is absolutely insane.

[1] https://deanclatworthy.com/2026/02/11/integration-isnt-an-ev...
by brachkow | 2026-02-14 11:03:40+00:00
I understand that US has a weird tipping culture which results in such UI.

But these UI's are occasionally slipping into a countries where tipping is not expected.

This leads to a strange situations like "transaction isn't approved by me because instead of ApplePay and walk away, I need to solve some quiz on a payment terminal or payment will not pass".

Every time this happens, it annoys me a lot which affects my wish to visit this place again.
by YinglingHeavy | 2026-02-14 11:04:34+00:00
* 02/22/1993 Jeffrey Epstein obtains Zorro Ranch from King

* 02/22/1993 Jeffrey SINclair: Babylon 5 debut

-------

"Something as big as Epstein’s operation starting up will usually have comms sent marking it.

This show explains a likely “intent” of why Epstein was allowed to meet and interact in suspect ways with so many important political and business people.

It clarifies the affiliation of Epstein. Note his (O'Hare) date of birth being as the world signed agreement to cooperate at CERN.

So let’s go through the show and we may just gleam a heck of a lot about intent. Note the pilot being about clearing Jeffrey Sinclairs name of suspicion of murder.

------

He was removed after the first season due to mental health issues. Meaning he went off the rails for at least some of the people who agreed to back him. Therefore we cannot assume anything Jeffrey Epstein did after 1994 with children was approved by all sides. On the contrary, this disagreement suggests at least some of the parties initially on board had strongly changed their mind about him once they saw what he was doing.

------

The way MK ops work is hidden, like a submarine that surfaces only when it’s time to attack. If one person dies there isn’t necessarily clearly understood of who pulled the string, and even when it is the way it works is specifically designed to be unpunishable. This seems to be the point of what Epstein was greenlit to do.

Finding who is tied to past murders.
Create Leverage to prevent more murders of those participating in truce."
by throwaway290 | 2026-02-14 11:04:35+00:00
I mean browser status bar (address bar, load progress etc.) and also you're wrong at least on new phones.

If you tap the island and if there's any activity there, it doesn't scroll up it switches to activity app. You need to hit the top edge of the screen not the island. And that is hit or miss, because 30% you hit the island and often there's activity there.

It was better before when it was not an island and activity was rare, only when you're navigating or on a call. Now every app and it's dog has a live activity in island.
by compsciphd | 2026-02-14 11:05:21+00:00
par2 is very limited.

It only support 32k parts in total (or in reality that means in practice 16k parts of source and 16k parts of parity).

Lets take 100GB of data (relatively large, but within realm of reason of what someone might want to protect), that means each part will be ~6MB in size. But you're thinking you also created 100GB of parity data (6MB*16384 parity parts) so you're well protected. You're wrong.

Now lets say one has 20000 random bit error over that 100GB. Not a lot of errors, but guess what, par will not be able to protect you (assuming those 20000 errors are spread over > 16384 blocks it precalculated in the source). so at the simplest level , 20KB of errors can be unrecoverable.

par2 was created for usenet when a) the size of binaries being posted wasn't so large b) the size of article parts being posted wasn't so large c) the error model they were trying to protect was whole articles not coming through or equivalently having errors. In the olden days of usenet binary posting you would see many "part repost requests", that basically disappeared with par (then quickly par2) introduction. It fails badly with many other error models.
by betteryet | 2026-02-14 11:06:17+00:00
This stuff is important and can only happen at this level through legislation.

If you don't do it this way to apply for everyone, then any good actor products will be crushed by profitmaxxing competitors. Or any good actor executives and workers will be pushed out by profitmaxxing shareholders.

Legislators need to be careful to keep requirements tight and manageable, but it's better to limit negative externalities than outright ban something. Banning infinite scroll or any particular pattern is nonsense, but restricting addictive design (e.g. TikTok) and algorithm weaponization (e.g. TikTok) is very sensible.
Show HN: Built Vokab: a vocabulary learning app built with SwiftUI
by meszmate | 2026-02-14 11:06:30+00:00
I just shipped my first iOS app. Vokab helps you build your English vocabulary with real examples, native audio, and smart review — synced across all your Apple devices including Watch. Built fully native with SwiftUI, no data collected. Would love feedback from fellow devs.

https://apps.apple.com/app/vokab-build-your-vocabulary/id675...
by selcuka | 2026-02-14 11:07:01+00:00
The source was available, but with cryptic variable names and (apparently) no or little comments:

> Ward mentioned that the biggest bottleneck was the cryptic variable names—short abbreviations that were common in old-school programming but made the code nearly impossible to follow.

> "He not only commented everything," Ward marveled, "he went through every single line of code and renamed every single variable for me in about three days.

I think it's still fair to use the term "reverse engineering".
by Xeago | 2026-02-14 11:07:29+00:00
What about an alternative business model, pay-per-date? There's an application in NL that charges €7.50 to arrange a dinner, disallowing chat until 2 hours before the arranged date for practicalities. They partner with restaurants and you each get a 'free' (you paid for it..) drink; but with the commitment that your date also paid for it and will therefore show up.

This removes a lot of the meat-grading and endless swiping; with the platform prompting you why you're not working to scheduling your existing matches. Whilst I have no experience with the absence of any scheduled matches, this gives the platform insight into whether you're a worthy date (remember, each date is profit!).

One date on tinder/hinge/bumble in a 5+ years to a finding my partner in a few months. Paying for the actual date experience was so much less and so much more fun than the footing the subscription on the other platforms - even accounting for the cost of food.
by alexrp | 2026-02-14 11:07:31+00:00
Just on this point:

> You mean like how Rust tried green threads pre-1.0? Rust gave up this one up because it made runtime too unwieldy for embedded devices.

The idea with making std.Io an interface is that we're not forcing you into using green threads - or OS threads for that matter. You can (and should) bring your own std.Io implementation for embedded targets if you need standard I/O.
by fatherwavelet | 2026-02-14 11:07:46+00:00
I just don't understand this view on Lex Fridman at all.

Fridman is quite good at letting the guest speak. The whole show is exceptionally good at keeping a conversation moving.

I think there are technical haters on Lex but that is stupid because Lex is in sales. He is selling a podcast. From a sales perspective, Lex is incredibly good.

It is like saying the chef is only a good cook because of the quality of the ingredients. Yes, exactly. The chef isn't a farmer growing their own organic vegetables for the dishes. The art is in the choice and ability to source quality ingredients and then bring it all together as a full dish.

A podcast is not a lecture or audio book.
by jimnotgym | 2026-02-14 11:10:42+00:00
I like the other employment 3 year problem.

In this the company fills jobs with keen but cheap young people to save money. These people work hard, get experience and take qualifications. Three years later you have a cohort of young people with excellent CVs and qualifications above their peers... that the company can't afford to pay the market rate for! Then it loses a whole cohort of great staff.
by lingxiao10 | 2026-02-14 11:12:00+00:00
This is the dumbest project I have ever seen. Why does it have so many upvotes and comments? Because there are a bunch of idiots here who need to add meaningless stuff to their empty and pointless papers. Only so-called pure academics would try to build such an index for code. File directories, search, and the built-in code parsing capability of compilers basically allow AI to locate any problem within 5 to 30 seconds. Even in the worst-case scenario, the problem is definitely not the lack of a so-called code index. To everyone participating in this discussion: how much have you actually used Claude Code? I have built several large projects with it without writing a single line of code myself, and I have never thought that code location or indexing was a problem at all.
by helloplanets | 2026-02-14 11:12:22+00:00
> blatantly naming

Not sure if you mean that I'm being hostile for no reason towards this 'someone else'. The second section in my original post is the big conditional.

> I guess the grifter didn't just copy paste what our guy did. it did have more impact and well time

This is more than likely correct.

Either way, I do think it's grifter behavior to not mention/include anyone else who was involved in the project if you pick it up halfway through. Unless the code (or whatever else) is actually bad, and you have to do extra work to redo it. And, if you are actually aware who even worked on the project to begin with.

But it very well might've been a case where some higher up passed the project off to another programmer (months/years later) with no malicious intent whatsoever, and the programmer just did the thing as requested. Or a myriad of other explanations.
by ofalkaed | 2026-02-14 11:12:42+00:00
I don't think Andrew believes Zig is going kill C or C++, he probably has hope but I think he is aware of the reality. He found a way to make a living on something he was passionate about.

Use-after-free is a fact of life until something kills C, but the realities of language adoption are against that. Zig seems interesting and worthwhile in offering a different perspective on the problem and does it in a way more agreeable than Rust or the like for all those who love C and are adverse to large complex languages. The realities of language adoption are as much for as against Zig, large numbers of people are still getting drawn to C and Zig seems to do a better job addressing why so many are drawn to it than the alternatives.
by arash_kay | 2026-02-14 11:13:28+00:00
Hotel chatbot SaaS costs $200-2,000/month with per-message fees and vendor-locked data. I built a free, self-hosted alternative.

Jack The Butler is an AI concierge that handles guest communication across WhatsApp, SMS, email, and web chat. Single Docker container, single SQLite database, deploy in 5 minutes.

Tech stack: Node.js, TypeScript, Hono, SQLite + sqlite-vec for embeddings, React dashboard. Supports Claude, GPT, Ollama, or fully local AI via Transformers.js (zero API costs).

Key design decisions:
- SQLite for everything including vector search (sqlite-vec) — no Postgres, no Redis, one file to backup
- Kernel/adapter architecture — core logic is channel-agnostic, channels and AI providers are swappable adapters
- Setup wizard — hotel managers (non-technical users) need to go from docker run to working chatbot in under 5 minutes
- Escalation engine — AI handles the easy 80%, smoothly hands off the hard 20% to staff with full context

One-click deploy on Railway/Render/Zeabur, or:

docker run -d -p 3000:3000 -v jack-data:/app/data ghcr.io/jackthebutler/jackthebutler:latest

Would appreciate feedback on the architecture and UX. Happy to answer questions.
by itopaloglu83 | 2026-02-14 11:15:49+00:00
At this point it’s more profitable for companies to just enforce tipping everywhere using the UI as an excuse. It’s a total ripoff especially at already expensive places.

Even if a law was passed in the US to correct the minimum wage at restaurants etc. nothing will be resolved.

Restaurants managed to outsource their wage problems to customers without raising their prices. Even with an adjusted minimum wage, people will say that it’s not enough.
by jauntywundrkind | 2026-02-14 11:16:03+00:00
That existed sort of largely outside the public sphere. There was a digital dual in those old times.

Now, there is no digital dual. https://www.roughtype.com/?p=2090

And worse here, the very worst have figured out how to keep making reality pay attention to the absolute garbage misery show. A newsgroup dust-up might have caught some small coverage, but the way the troll-forces of the world have mobilized and radicalized their shitizens at scale, and the stochastic terror they have focused on creating: it keeps the rest of reality all too glued to the sick farce programming the aggressor forces against the world anti-campaign on.
by tim333 | 2026-02-14 11:16:57+00:00
Keynes was a different thing - that we could cut working hours to 15 a week rather than never have to work again. I think that would be quite possible with a drop of living standards - you could do it today by moving somewhere cheap and doing some remote work. I think it didn't happen due to human nature. We both quite like doing something useful with our time and like increasing living standards.

I inherited some money and don't need to work, but do work on stuff because I like doing it. I imagine that's what things will be like post agi.
by ozgrakkurt | 2026-02-14 11:17:08+00:00
I recently ditched zig because of this.

I thought it was stable enough initially but they completely broke fuzz testing feature and didn’t fix it.

Also build system API and some other APIs change and it is super annoying.

Find it much better to use c23 with _BitInt integers and some macros and context passing for error handling.

Also some things like stack traces were broken in small ways in zig. It would report wrong lines in stack traces when compiling with optimizations. Also wasn’t able to cleanly collect stack traces into strings in production build.

It is understandable that breaking APIs is good for development but in most cases new API isn’t that good anyway.

And recently saw they even moved the time/Instant API to some other place too. This kind of thing is just super annoying with seemingly no benefit. Could have left the same API there and re-used it from somewhere else. But no, have to make it “perfect”
by grey-area | 2026-02-14 11:17:21+00:00
I and many others find it a useful warning. So I doubt people will stop noting it as part of a critique of things.

'You used a tool I don't like' is really missing the point.

'You generated text that is long and a bit boring and will probably include falsehoods.' is a more accurate description of why people pick up on this - the style is an indicator of using a tool that generates convincing garbage.