I look up to people who are well-read and try to follow their example. Maybe one day I can inspire somebody else.
755 karma · joined January 5, 2026
I look up to people who are well-read and try to follow their example. Maybe one day I can inspire somebody else.
That said, I probably wouldn't ship spinlocks in consumer libraries or code I expect to be reused across deployments.
Likely, they will run an OCR scan to blur any text seen through the cameras. Also likely, they would run a vision model classifying identifiable information: people walking past, hanged photos or even paintings, TV screens, maybe even the view outside the window? For safety purposes, I imagine it's also worth identifying handheld tools such as knives, bats, etc., all done so the operator risks are minimized.
Fair enough, and I'm not arguing against that, there's just something distasteful about the operator having to walk around in a largely obscured, muted camera feed, looking for traces of underwear scattered around the house.
I'd love to read an article about the topic, but can't recommend this one if you expect high informational quality.
A much more valuable discussion would be centered around the company's own website, which contains the same information, and doesn't require an LLM mediator: https://www.weaverobotics.com/isaac-1
Obviously, we'd have processes built that build machines for each of the individual tasks, or changing tracks to support new car models.
From my perspective, this framework of a factory could map to many other endeavours where we either produce the end product or a machine used for something else.
So, the difference would be whether the machines utilize chemical/biological processes for working, or are made out of steel, at which point it would boil down to economics.
I guess I don't see what's so special about adding 'bio' to these perpetual factories.
What can you use it for? To run a breadth search on Erdos problems?
What exactly about checking out makes it 'more living'? I sense a false dichotomy here
IMO, they were quite good with checklists even a year ago, and tried to tick off each one.
I'd say it's generally true that the majority of jobs of an era deal with a similar level of abstraction, and that's why most people stay on it. However, I frame this as being born with technical debt, and it's my obligation as an engineer to understand what the previous generations have built, and where it makes sense for me to work, directionally.
For a while now there has been very little incentive for providing these alongside the paper, and I don't see why exactly 'AI' would change this. I could even see how making it vague to be harder to test with LLMs could be profitable for citation hackers.
I want to see who did the hard work properly, and who focused on publishing with concealed details.
I can't help but feel this is intentional towards the 'Agentic' workflow.