4,836 karma · joined October 2, 2016
QWNjZXNzIG1haW4gcHJvZ3JhbS4gQWNjZXNzIG1haW4gc2VjdXJpdHkuIEFjY2VzcyBtYWluIHByb2dyYW0gZ3JpZC4=
The icing on the cake was how popular this edition was.
I have no idea how assembly works - in my years of experience I’ve never had an issue that required I dig that deep into it. Does that mean I can’t be effective with higher-level tooling because I do not know the absolute basics?
And yet most people prefer talking to a waiter. There are other restaurants that have tried similar approaches and people would almost always deal with people rather than a robot.
I would love a robot to clean my home and do household chores, but in the service industry I would prefer real humans doing the work.
Agents and AI are getting expensive, it seems silly to waste tokens on static checks.
https://news.ycombinator.com/item?id=46871173
Anyways the most layman way I’ve seen it explained is this: skills help save token usage for the right context. Not every request needs all instructions all the time - running tests is different than reviewing a PR, so why should the context window have instructions for both on every request?
So now you split instructions into “skill” files, which are basically opinionated markdown files. And you invoke those with something like /grill-me in the prompt depending on what you’re doing.
There are some steps to have the agent automatically know what to invoke for you but in my experience this automation is hit or miss.
It is also challenging to keep track of a growing library of skills and keeping those up to date.
So YMMV regarding skills. I typically keep things in a single markdown file even if the context window gets a bit bloated.
Have there been improvements on this front?
It used to be fairly obvious (using em dashes, etc) but now AI writing, with the correct guidance, is very much the same as regular conversational writing.
https://www.frontiersin.org/journals/psychology/articles/10....
Will we eventually be so accustomed to LLM's that we will be similarly shocked when someone elects to not use them?
They really ought to do a follow up for 2026. From what I gather talking to faculty and professors, this problem became noticeably worse since COVID and the years following. A follow up book or study would be very interesting to read.
There is a reference to global warming that is similar to the poem. That the world will heat up, and humanity will die, and the earth will continue on as it has for a million years. The film mentioned the “the earth will shake us off, like a summer cold”.
This seems fairly comparable to the soft rains poem in this piece.
Maybe a similar setup can be done for banned AI weights?
https://github.com/apple-oss-distributions/xnu/blob/f6217f89...
https://lore.kernel.org/asahi/c13d95d0-911f-48f6-b4ca-8a5e9a...
For 100 USD I can get a Roomba or Roborock for one floor and because that is so cheap I don’t mind this limitation. But for 8-10k USD I would expect this very common household feature to be solved.
If you decided to boycott every company that replaced staff with automation, you would be forced to exit the economy. Every company does this to some degree and the customers who vote with their wallet do not seem to care about a reduction in force.
[1]: https://arstechnica.com/ai/2026/06/gm-installs-robots-at-fla...
It is nice to be able to have a consistent deployment pattern, with traceability, rollback support, and production approval checks. It’s nice to not have some archaic something stuck in someone’s head. It’s also nice to be able to see how something works by reading the code, which is usually up to date and deployable.
I prompted the AI to write a report as if it were a home inspector and it actually did a better job and identified some issues the paid 750 usd inspector missed.
HN Launch: https://news.ycombinator.com/item?id=30605010
Promo codes: https://www.optery.com/optery-promo-codes/