[ my public key: https://keybase.io/jimmcslim; my proof: https://keybase.io/jimmcslim/sigs/rPRehkgKNYg779OfURwz4ZTEUjjaTvSbikilZm4-xro ]
jimmcslim.at.hn
- jimmcslimWhere is "Cloudflare Cock-Ups" in this chart? https://radar.cloudflare.com/year-in-review/2025#internet-ou...
- 28 points
- Ask yourself "what is intelligence?". Can intelligence at the level of human experience exist without that which we all also (allegedly) have... "consciousness". What is the source of "consciousness"? Can consciousness be computed?
Without answers to these questions, I don't think we are ever achieving AGI. At the end of the day, frontier models are just arithmetic, conditionals, and loops.
- 4 points
- 2 points
- 30 points
- Maybe, but I did come to the article hoping to learn that he had just published another collection of short stories, but alas not.
- Apple have no interest in fixing the “one more minute” loophole in Screen Time so I don’t see them wanting to support this.
- I would very much like this to operate in read-only mode!
- Kim Stanley Robinson's Aurora [1] is a great novel about the hubris of generation starships.
- 1 point
- > The initial init makes some CHARM.md
Oh god please no... can we please just agree on a standard for a well-known single agent instructions file, like AGENT.md [1] perhaps (and yes, this is the standard being shilled by Amp for their CLI tool, I appreciate the irony there). Otherwise we rely on hacks like this [2]
- 4 points
- And a real risk of a shattered CRT screen! I remember carting my bougie 17” Viewsonic around in the back of my Hyundai Excel and wondering if it would pick up a crack along the voyage…
- Kiro, the latest agentic IDE hotness, indicates that it you should "Define user stories and acceptance criteria in structured EARS notation". But didn't link to what EARS actually is [1]. Any mention of EARS also appeared to be missing from the HN post discussing Kiro [2]. If you have previous experience with EARS, it looks like you might be soon "hearing" all about it...
From the link...
The Easy Approach to Requirements Syntax (EARS) is a mechanism to gently constrain textual requirements. The EARS patterns provide structured guidance that enable authors to write high quality textual requirements.
Structured English that should be simpler for an LLM to parse and reason about.
- 1 point
- 2 points
- Some of the other comments have identified the priority of proper form when lifting… are there any accurate and effective computer vision solutions for checking correct lifting form and posture throughout different types of moves? Preferably open source and deployable with off the shelf consumer hardware.
- 6 points
- I understand the GraphQL has fallen out of favour somewhat, but wasn’t it intended to solve for this?