5,210 karma · joined July 9, 2010
https://hndistilled.com
[ my public key: https://keybase.io/juhap; my proof: https://keybase.io/juhap/sigs/WENl0olIwIRMUkvvYdpsHpszBLLHaissp7cTfP1QynU ]
Maybe they feel just using the AGENTS.md written for another model and possibly different era gives bad user experience.
[1] https://claude.com/blog/the-new-rules-of-context-engineering...
[1] https://techcentral.co.za/jony-ives-first-openai-device-an-a...
When pushed, I then start thinking and realise my mistake. System 1 vs 2?
In the future it will be increasingly difficult to prove in online context that you are not a bot. Being able to show that your social media (HN, GitHub, etc) presence goes way back would be an option.
Also if all the "state" is in one database, then you have better chance of getting consistent backups.
[1] https://newsroom.accenture.com/news/2026/accenture-to-acquir...
Or ask Codex to create image that explains xyz.
Then when you really start thinking about it, the list of requirements grows.
Of course it’s still totally doable for an average developer, but takes time and mistakes can be catastrophic. And maybe the time is better spent developing stuff that differentiates you from others.
Token maxxing? Might explain high costs if you are actively encouraging developers to spend as much tokens as possible.
Old fashioned person-to-person email would work as it does. This would only apply to the app-to-user stuff, which in my case makes up >99% of my emails.
Boom, you have an agent in the phone capable of doing all the stuff you can do with the apps. Which means pretty much everything in our life.
Obviously makes only sense for stuff like analytical queries that are not running constantly.
From Astral the (fast) linter and type checker are pretty useful companions for agentic development.