Recent submissions

Comment · 24 days ago
Comment · 1 month ago
The number of ads I have gotten lately about buying ads on Apple Maps has me glad I'm not using Apple Maps. It turns out they're just late to the ad game, not opposed to it.
Comment · 1 month ago
Hmm. The project uses BirdNET-Go, which does inference locally on a Raspberry Pi. Then it looks up the species against a set of already existing illustrations. So in this case it seems like the "ultra expensive, data-center-driven AI" is not really involved in the core loop of this project.
Comment · 1 month ago
Rate limiting
Comment · 1 month ago
You can /i-have-adhd when you get a wall of text and are exasperated. You don't always want the responses that it generates when you /i-have-adhd, and things in AGENTS.md tend to lose weight as context grows.
Comment · 2 months ago
It's Genetic Programming via LLM, cool!
Comment · 2 months ago
How do you differentiate between mastery of a topic and mastery of using an AI in an exam setting?

Open book tests and allowed cheat sheets already solve the memorization-is-not-required gap. It seems like allowing use of AI pushes that closer to thinking-is-not-required. And if no thinking is required, then how can you prove personal mastery?

Comment · 2 months ago
First, cloning a repo doesn't bring the hooks with it - so it's not just as simple as saying "use git hooks".

Second, if the repo had hooks and instructions for the LLM or user to blindly install/enable the hooks, we'd instead be complaining about security risks and what might happen if the repo is compromised at some point in the future.

Third, sometimes you don't want to mechanically enforce things via git hooks because it impacts your use when what you're really trying to codify and enforce are the LLM's actions. In that case you can enforce mechanically via hooks at the harness level.

And finally, git hooks are a great solution for upstream repositories to enforce quality and protect branches. But it means that the upstream is the one running the checks. It makes the upstream a potential bottleneck - better to have the leaf nodes run the checks locally and fix any issues before pushing it upstream rather than push upstream, wait for results, make changes, push upstream, wait for results, make changes.

Comment · 2 months ago
Comment · 2 months ago
My read on this, beyond data and MBA's, is that all of the slack has been pulled out of the economy.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton