MurphyA/hacker-news huggingface dataset:
by jascha_eng | 2026-02-15 05:17:14+00:00
I think people got fatigued by reviewing already. Most code is correct that AI produces so you end up checking out eventually.

A lot of the time the issue isn't actually the code itself but larger architectural patterns. But realizing this takes a lot of mental work. Checking out and just accepting what exists, is a lot easier but misses subtleties that are important.
by troad | 2026-02-15 05:17:53+00:00
> The application that assumes that key "foo" is in the map, and crashes if it's not, is just as brittle

And the program that assumes that foo is a string when it's an integer yadda yadda yadda. Boring type debates are boring. What's better, that code containing erroneous baseline assumptions about the data it's handling stays live, or that it safely aborts before it corrupts any of that data?

Did you know that Erlang's unofficial motto is "let it crash"? The language has extremely robust recovery mechanisms, having been designed for flaky telecommunications infrastructure. All code runs in green threads, under in-built supervisor trees.

A web request, for example, would have at least two associated green threads - one for business logic, one to respond.[0] If the logic thread was dead sure it was going to get a foo, and it instead gets bar, what is it intelligently supposed to do with that bar? The only thing it safely can do - log and crash. The supervisor tree brings it back live. Immutability ensures no data is corrupted. The second thread then gracefully returns a 500, exactly as it should.

Read up on the BEAM sometime, you might find it interesting.

[0] More in reality for other things: databases, worker pools, etc.
by adamrt | 2026-02-15 05:17:59+00:00
In the "for ... else" example, am I wrong to think this is a typo? Should it be "if (sample.key == key)". The second example doesn't help clarify since the resulting variable is shadowed by the loop variable (cpu).

const item = for (let sample .. items) {
if (item.key == key) {
break item;
};
} else { ... };

I don't have a project to use hare for currently, but I do appreciate most of it's goals. I think it's an admirable project and hope it succeeds in its ambitions.
by noufalibrahim | 2026-02-15 05:18:21+00:00
I've never used Arch but I can really get the vibe here. Wikis (especially toopical ones) are social media of sorts. There was a strong community around the #emacs IRC channel and emacswiki.org back in the day. About a 100 people who knew each other quite well. And an Emacs bot that could read from the wiki (pre-modern RAG I suppose) and answer questions.
by AnthonyMouse | 2026-02-15 05:20:17+00:00
The one thing AI is consistently better at than humans is shipping quickly. It will give you as much slop as you want right away, and if you push on it for a short period of time it will compile and if you run it a program will appear that has a button for each of the requested features.

Then you start asking questions like, does the button for each of the features actually do the thing? Are there any race conditions? Are there inputs that cause it to segfault or deadlock? Are the libraries it uses being maintained by anyone or are they full of security vulnerabilities? Is the code itself full of security vulnerabilities? What happens if you have more than 100 users at once? If the user sets some preferences, does it actually save them somewhere, and then load them back properly on the next run? If the preferences are sensitive, where is it saving them and who has access to it?

It's way easier to get code that runs than code that works.

Or to put it another way, AI is pretty good at writing the first 90% of the code:

"The first 90 percent of the code accounts for the first 90 percent of the development time. The remaining 10 percent of the code accounts for the other 90 percent of the development time." — Tom Cargill, Bell Labs
by yellow_lead | 2026-02-15 05:22:39+00:00
There's already Zulip, Mattermost, and many others. Building a chat application should be considered a tar pit problem IMO. A lot of success relies on network effects and familiarity, and the product looks deceptively simple.

It's unlikely you can build one that is better than Slack without years of investment. Even if you do, it's still an uphill battle.
by nextaccountic | 2026-02-15 05:23:11+00:00
For Rust programs there's https://docs.rs/clap_mangen/0.2.31/clap_mangen/ that will generate a man page out of the help. (I am sure most programming languages have something like this). However, that's only useful if you are compiling the program (maybe distros could patch Rust programs to generate the man page during the build process)

A more general tool would be pretty good. Either for distros to call during build, after building the program proper; or for users to call.

If users are calling directly, it would be useful to, by default, show the regular man page if it exists, and only if it doesn't exist generate and display one out of --help. Also give it the same flags as man etc. In this case, we could do alias man=better_man and pretend this problem is already solved (but it's still better if distros generate it, so that they can display the man page on the web, etc)
by AlotOfReading | 2026-02-15 05:23:38+00:00
If the other option is suicide, a qualified therapist and other mental health resources are the right answer, not a chatbot.

Frankly I'm not sure an LLM is even better than nothing. Note the user in that thread whose "partner" told them to get a therapist because they were delusional and instead retreated to Grok.
by jauntywundrkind | 2026-02-15 05:24:00+00:00
> That said I'd have preferred something other than Lua if I had the choice.

Denops is super easy to use, works great. Connects over RPC. https://github.com/vim-denops/denops.vim

Nvim-oxi is wild. Uses neovim's FFI to let you write Rust that talks directly to neovim. https://github.com/noib3/nvim-oxi

Denops has always been a niche but it was a really popular niche for a couple years. Activity is fading somewhat. I'm still doing my plugin dev in lua, and it's... survivable. But I do think of switching more into one of these options.
by ineedasername | 2026-02-15 05:24:48+00:00
Same? Not quite as good as that. But google’s Gemma 3 27B is highly similar to their last Flash model. The latest Qwen3 variants are very good, to my need at least they are the best open coders, but really— here’s the thing:

There’s so many varieties, specialized to different tasks or simply different in performance.

Maybe we’ll get to a one-size fits all at some point, but for now trying out a few can pay off. It also starts to build a better sense of the ecosystem as a whole.

For running them: if you have an Nvidia GPU w/ 8GB of vram you’re probably able to run a bunch— quantized. It gets a bit esoteric when you start getting into quantization varieties but generally speaking you should find out the sort of integer & float math your gpu has optimized support for and then choose the largest quantized model that corresponds to support and still fits in vram. Most often that’s what will perform the best in both speed and quality, unless you need to run more than 1 model at a time.

To give you a reference point on model choice, performance, gpu, etc: one of my systems runs with an nvidia 4080 w/ 16GB VRAM. Using Qwen 3 Coder 30B, heavily quantized, I can get about 60 tokens per second.
by yawnxyz | 2026-02-15 05:24:56+00:00
useful for adding semantic search to tiny bits of data, e.g. collections of research papers in a folder on my computer, etc.

for web stuff, e.g. community/forums/docs/small sites which usually don't even have 1M rows of data, precomputing embeddings and storing them and running on a small vector search like this somewhere is much simpler/cheaper than running external services

it's the operational hassle of not having to deal with a dozen+ external services, logins, apis, even if they're free

(I do like mixed bread for that, but I'd prefer it to be on my own lightweight server or serverless deployment)
by monkpit | 2026-02-15 05:26:28+00:00
Slightly off topic, but: is it just me or does it become uninteresting to read things like this when the whole process is basically “so then I asked Claude this, and then I asked it this, and then this…”

I guess it takes away the intrigue of the project because anyone could do this (ask ai), and the only thing human left about it is the creativity of the idea itself. There’s not much merit to the effort.

Edit: nothing against the author or anything, it’s fun to do projects like this.

But I always kinda likened AI output to your kids’ artwork - to you it’s the best. To someone else, it doesn’t have as much impact.
by vladdoster | 2026-02-15 05:26:30+00:00
Location: Nashville, TN
Remote: true
Willing to relocate: boston || nashville
Technologies: Python, Django, IaC, Terraform, Golang, CI/CD, Azure/AWS, {ba,z}sh, Lua, Springboot,
Redis, Docker, Open Service Broker, {,non}relational & vector dbs, shared services, SOA
Email: mvdoster@gmail.com

resume: https://linkedin.vdoster.com && http://github.com/vladdoster

sr. cloud software engineer @ Mastercard (5 years)

Designed and built Platform-as-a-Service for microservice workloads running on Azure and AWS
to migrate on-prem workloads to the cloud. The platform operates globally, allowing teams to
deploy to several Azure-backed regions worldwide. Helped plan and create regional landing zones
in Azure for application teams wanting to perform globally. Designed platform components using
Terraform, Go, and Node; developed support tooling using Bash, Python, and Azure CLI. De-risk the
platform by addressing security vulnerabilities and ensuring the platform is PCI compliant.

api/devops software engineer @ Harvard Medical School (2 years)

Worked as part of the DevOps team to manage a 15k core CentOS HPC cluster. Designed and implemented
Python-based security scanning pipeline to securely deploy & run Apptainer images via SLURM.
Coordinated cross-team emergency patching eﬀorts. Collaborated with researchers and engineers across
3-letter institutions to deliver secure research infrastructure. Built CI/CD Pipelines with GitHub, Jenkins,
to automate code builds, testing, and deployments. Wrote Puppet modules to manage configuration of HPC fleet.
Wrote custom Puppet module & Python scripts to automatically remediate Tenable findings.

full-stack software engineer @ Global Prior Art (3 years)

Used Django, Celery, Selenium grid, and AWS API Gateway for IP rotation to scrape USPTO patent PDFs,
apply CV for data extraction, and generate reports with relevant claims, saving employees 4-5 hours daily.
Wrote E2E black-box/fuzzing unit tests. Automated on-premise deployment via Github Actions and Ansible.
by fragmede | 2026-02-15 05:26:54+00:00
Hot keys. Used to be, you could drive a program from the keyboard with hotkeys and macros. No mouse. The function keys did functions. You could drive the interface blindfolded, once you learned it. Speed is another one. Why does VSCode take so long to open? and use so much memory and CPU? it's got a lot of features for a text editor, but it's worse than vim/emacs in a lot of ways.

Boot time.

Understandability. A Z80 processor was a lot more understandable than today's modern CPUs. That's worse.

Complexity. It's great that I can run python on a microcontroller and all, but boring old c was a lot easier to reason about.

Wtf is a typescript. CSS is the fucking worst. Native GUI libraries are so much better but we decided those aren't cool anymore.

Touchscreens. I want physical buttons that my muscle memory can take over and get ingrained in and on. Like an old stick shift car that you have mechanical empathy with. Smartphones are convenient as all hell, but I can't drive mine after a decade like you can a car you know and feel, that has physical levers and knobs and buttons.

Jabber/Pidgin/XMPP. There was a brief moment around 2010? when you didn't have to care what platform someone else was using, you could just text with them on one app. Now I've got a dozen different apps I need to use to talk to all of my friends. Beeper gets it, but they're hamstrung. This is a thing that got worse with computers!

Ever hear of wirths law?
https://en.wikipedia.org/wiki/Wirth%27s_law

Computers are stupid fast these days! why does it take so long to do everything on my laptop? my mac's spotlight index is broken, so it takes it roughly 4 seconds to query the SQLite database or whatever just so I can open preview.app. I can open a terminal and open it myself in that time!

And yes, these are personal problems, but I have these problems. How did the software get into such a state that it's possible for me to have this problem?
by ffsm8 | 2026-02-15 05:27:42+00:00
Okay, honestly asking: do you really think your outlined simulation meet the same bar as automated regression tests like

> E.g you technically don't need to look at the code if it's frontend code and part of the product is a e2e test which produces a video of the correct/full behavior via playwright or similar.

> Same with backend implementations which have instrumentation which expose enough tracing information to determine if the expected modules were encountered etc

If not, your quoted sentence was "tests like that". If yes... I guess we would have to disagree.
by brigandish | 2026-02-15 05:28:37+00:00
Something I occasionally do is ask it to extensively comment a section of code for me, and to tell me what it thinks the intent of the code was, which takes a lot of cognitive load off of me. It means I'm in the loop without shutting off my brain, as I do have to read the code and understand it, so I find it a sweet spot of LLM use.
by jauntywundrkind | 2026-02-15 05:30:11+00:00
I used mcp-neovim-server to let my LLM control my vim session. that way it can debug and test and poke around. It's crazy good at debugging plugins. It's absurd how little these things need to look-up docs; half these models are just out the box wildly good at vim. "Open these files on these lines" and now there are four splits with me at the relevant line numbers. Awesome. And it'll explain how to do things & test it out & validate! https://github.com/bigcodegen/mcp-neovim-server

That was a little tricky to set-up. I ended up writing nvim-auto-listen, which uses some heuristics to find your project root, and starts a .nvim.socket in that directory. That makes it easy for mcp-neovim-server instances to find. https://github.com/rektide/nvim-auto-listen/

I'm only somewhat getting started, but the workmanship, fit and finish is just outstanding on Codecompanion, for a fantastically well put together in vim agentic experience. Works really well driving a headless opencode mcp. Being able to stay in vim but still get a great opencode powered experience has been mind blowingly sick.
https://github.com/olimorris/codecompanion.nvim
by gotwaz | 2026-02-15 05:31:11+00:00
Why? Switzerland has survived hundreds of years longer than the EU dealing with larger powers and bullys quite smoothly. "Expanding horizons" to survive is already a failed concept from colonial experience, and extremely unpredicable in modern times as Putin has already proved to everyone. If "smashing" takes 4 years just to struggle to take 4 poor provinces and inflicts massive damage to self, who wants to follow that path? Only morons who will get bogged down just as Putin has.
by mgraczyk | 2026-02-15 05:31:23+00:00
You're imagining that the doctor is required to act irrationally or against the patient's interest. I understand that they do act this way, but I'm pointing out that they don't have to!

You walk into a doctor's office and meet for the first time.

Case 1. You have 3 full body MRIs taken 6 months apart in hand and give them to your doctor. Nobody has opened or looked at the scans yet.

Case 2. You do not have a scan yet

You are claiming case 1 will lead to worse outcomes in expectation. I claim that's impossible because the doctor can simply do the following:
Without opening the scans, email them to the world's best radiologist. Tell that radiologist "only reply if it is nearly certain the patient has an operable cancer with the information available"

Now there are 4 possibilities.

Case 1 without cancer: nothing happens

Case 2 without cancer: nothing happens

Case 1 with cancer: you maybe survive

Case 2 with cancer: you die

The only reasonable objection to this is "that's expensive"
by dietr1ch | 2026-02-15 05:32:56+00:00
I find plenty of interesting videos, but I needed to slowly craft my following list.

I started with some CS lectures, and conference talks and it was alright, but something I reached for out of necessity.

Once I started watching videos out of curiosity I slowly ended up finding channels around my hobbies that filled my feed with pretty interesting stuff. There's good content out there beyond dense lectures, but also a lot of crap. I built my curated list of channels making videos worth watching and rarely watch something outside of those.

Similarly to music discovery, once you find what you like keep an eye on neighboring artists. I stay curious, but I'm quick to reject.
by nich2533 | 2026-02-15 05:33:07+00:00
I made a set of agentic coding commands that force different cognitive styles based on human drugs.

/LSD sees patterns between things. /Shrooms sees depth. /PCP is omnipotent. /Cocaine is aggressive and a little rude.

/adderall is actually pretty useful. /nitrous.. not so much.

Commands work in both Codex and Claud Code.

Don't do drugs kids. Just say no.
by noodletheworld | 2026-02-15 05:35:28+00:00
Nice idea, but isnt this kind of daft?

There are basically no useful models that run on phone hardware.

> Results vary by model size and quantization.

I bet they do.

Look, if you cant run models on your desktop, theres no way in hell they run on your phone.

The problem with all of these self hosting solutions is that the actual models you can run on them aren't any good.

Not like, “chat gpt a year ago” not good.

Like, “its a potato pop pop” no good.

Unsloth has a good guide on running qwen3 (1), and the tldr is basically, its not really good unless you run a big version.

The iphone 17 pro has 12GB of ram.

That is, to be fair, enough to run some small stable diffusion models, but it isnt enough to run run a decent quant of qwen3.

You need about 64 GB for that.

So… i dunno. This feels like a bunch of empty promises; yes, technically it can run some models, but how useful is it actually?

Self hosting needs next gen hardware.

This gen of desktop hardware isnt good enough, even remotely, to compare to server api options.

Running on mobile devices is probably still a way away.

(1) - https://unsloth.ai/docs/models/qwen3-how-to-run-and-fine-tun...
by RulerOf | 2026-02-15 05:38:01+00:00
The device is paid through a loan. That makes radio locks more preposterous, not less.

Breaking a contract is far less serious than defaulting on a loan. And if the cell providers' argument is "we need radio locks because fraud," remember they're full of crap.

It's not every consumer's fault that Verizon made hundreds of thousands of bad decisions about to whom they decided to extend credit last year. It's theirs.

This change in policy came less than a week after Verizon suffered a high-visibility outage[1] that left scores of people unable to use their phones. Before this policy change, customers could at least pick up an eSIM on another network for emergencies. Not anymore. Thanks, FCC.

[1]: https://www.the-sun.com/tech/15782764/verizon-down-sos-mode-...
by troad | 2026-02-15 05:38:03+00:00
> if you understood King's point, I don't understand how you can be arguing that Haskell idiomatically leads you into rigidity at version boundaries

Why would understanding his argument necessarily mean finding it persuasive or exhaustive?

> you parse the cases you care about and ignore the rest

What language would not allow this?

> The "path of desire" you're describing isn't a property of the language.

If a tool tends, more often than not, to lead to certain use, is that not a property of that tool? It is theoretically possible to use a hammer for interpretive dance, sure, but it doesn't seem to happen nearly as often as banging the hammer on things.

Equally, I think it's pretty easy to see how a language designed for robust typing is going to lead to, more often than not, robust typing.

I rather think you're engaging with a point that no one ever made - that typed languages are inherently incapable of dealing with uncertain, incomplete, or variable data - in lieu of the argument that was actually made - that languages with rich DX around rigid typing encourage an architecture that's rigidly typed, and that rigidly typed codebases tend to come up against predictable issues.

The original article identities a series of such issues and misattributes them to FP, when they don't have much to do with FP at all. That's all I was saying.
by amluto | 2026-02-15 05:39:35+00:00
> 3. Values follow a strict rule: primitives pass by value, containers pass by read-only reference. This prevents accidental aliasing/mutation across scopes and keeps ownership implicit but predictable.

There are plenty of languages where functions cannot mutate their parameters or anything their parameters reference — Haskell is one example. But these languages tend to have the ability to (reasonably) efficiently make copies of most of a data structure so that you can, for example, take a list as a parameter and return that list with one element changed. These are called persistent data structures.

Are you planning to add this as a first-class feature? This might be complex to implement efficiently on top of C++’s object model — there’s usually a very specialized GC involved.
by remocode | 2026-02-15 05:42:42+00:00
Hey HN, I built this because I kept wanting to kick off coding tasks while away from my desk.

The problem: AI coding agents like OpenCode, Claude Code, and Codex are powerful, but they're trapped in your terminal. If you step away from your workstation, you can't interact with them.

The solution: remote-opencode is a Discord bot that runs alongside OpenCode on your dev machine. You send prompts from any device (phone, tablet, laptop), and the output streams back in real-time.

Key features:
- Real-time streaming — see AI output as it's generated
- Task queuing — send multiple tasks, they execute sequentially
- Git worktree isolation — each task gets its own branch automatically
- Passthrough mode — just type naturally in a thread, no slash commands needed
- One-click PR creation from completed work
- Access control via allowlist

Typical workflow: I'm on the couch, I type /opencode prompt:refactor the auth module to use JWT on my phone, and watch my home workstation do the work. When it's done, I queue the next task.

npm install -g remote-opencode && remote-opencode setup — takes about 2 minutes.

1000+ weekly downloads on npm. MIT licensed. Would love feedback and contributions.
by charleslmunger | 2026-02-15 05:43:09+00:00
Not OP, but used Arch for a while in 2011, and at some point doing an update moved /bin to /usr/bin or something like that and gave me an unbootable system. This was massive inconvenience and it took me many hours to un-hose that system, and I switched to Ubuntu. The Ubuntu became terrible with snaps and other user hostile software, so I switched to PopOS, then I got frustrated with out of date software and Cosmic being incomplete, and am now on Arch with KDE.

Back then I used Arch because I thought it would be cool and it's what Linux wizards use. Now Arch has gotten older, I've gotten older, and now I'm using Arch again because I've become (more of a) Linux wizard.