@tophz_ I know someone who was in Stanford ER for 24 hours while psych doctors and medical doctors argued about whether to admit a suicidal person.
Ultimately psych won out and he was discharged. Attempted suicide within hours.
Stanford got paid $30k from his insurance. No food given.
@MovieplugTV Mine was very similar to this in the early 2000s.
It ultimately led to me switching schools and messing up my education to avoid out of control kids.
I wish I would have killed myself back then instead of realizing how the real world is in adulthood.
@korngrower@wildwellings@jbuesking Of course, paying for experience and someone with good insurance is importany. You can charge a lot and not have a lot of experience. Sometimes older companies have newer guys. Mistakes also happen, which is why their insurance matters.
@wildwellings@jbuesking Concrete is something you should never try to save money on. I cannot recall a single example from over 20 years in the trades where someone was happy trying to save money on concrete. It’s a situation where I always prefer to pay more for experience.
@deedydas I know multiple people in tech who are living homeless right now because of this.
The common trend is vehicle dwelling, but I know some living in tents or outside.
One is a former Google engineer sleeping in the park with nothing more than a blanket.
@shazcodes Working at/on a startup to get rich is one of the dumbest reasons and why people hate startups.
Do it for the passion, purpose, or experience… otherwise you will almost always be disappointed.
@ncklmn@Brainmetry@Jason When I drove Uber, a lot of customers told me that was exactly what they did between Uber and Lyft.
I personally do it with Lyft, Waymo, and Robotaxi.
The cost/time difference makes it worth checking.
@Brainmetry@Jason A few days ago I opened Lyft, Waymo, & Robotaxi. (I don’t use Uber)
Robotaxi was cheapest($6.40), but a 29 minute wait.
Lyft was ($5.94+$3 tip) and a 3 minute wait.
Waymo was ($26.$$) and an 11 minute wait.
I took the Lyft. Checking 3 apps was super easy.
@Eric_P8@bscholl It’s a good theory, but the data center operators have done it to themselves after the auto manufacturers and other industrialists polluted a lot of land.
The operators have all required NDAs of local government officials & dismiss local concerns.
We need more open conversation
@bscholl Having been to many local meetings opposing data centers, it’s likely that 99% of people opposing data centers would also oppose your manufacturing facility.
There needs to be more positive conversation instead of all this rejection by both sides.
@ThePiccoloDog@zanehengsperger This is exactly the problem. A lot of people would build it, but the people with money won’t fund it… they will fund a million people making agents though.
We picked this name last year, long before claws were a thing…
But the idea was the same.
Local edge compute for AI.
It is hard to believe what has transpired this year.
Bought a new Mac mini to properly tinker with claws over the weekend. The apple store person told me they are selling like hotcakes and everyone is confused :)
I'm definitely a bit sus'd to run OpenClaw specifically - giving my private data/keys to 400K lines of vibe coded monster that is being actively attacked at scale is not very appealing at all. Already seeing reports of exposed instances, RCE vulnerabilities, supply chain poisoning, malicious or compromised skills in the registry, it feels like a complete wild west and a security nightmare. But I do love the concept and I think that just like LLM agents were a new layer on top of LLMs, Claws are now a new layer on top of LLM agents, taking the orchestration, scheduling, context, tool calls and a kind of persistence to a next level.
Looking around, and given that the high level idea is clear, there are a lot of smaller Claws starting to pop out. For example, on a quick skim NanoClaw looks really interesting in that the core engine is ~4000 lines of code (fits into both my head and that of AI agents, so it feels manageable, auditable, flexible, etc.) and runs everything in containers by default. I also love their approach to configurability - it's not done via config files it's done via skills! For example, /add-telegram instructs your AI agent how to modify the actual code to integrate Telegram. I haven't come across this yet and it slightly blew my mind earlier today as a new, AI-enabled approach to preventing config mess and if-then-else monsters. Basically - the implied new meta is to write the most maximally forkable repo and then have skills that fork it into any desired more exotic configuration. Very cool.
Anyway there are many others - e.g. nanobot, zeroclaw, ironclaw, picoclaw (lol @ prefixes). There are also cloud-hosted alternatives but tbh I don't love these because it feels much harder to tinker with. In particular, local setup allows easy connection to home automation gadgets on the local network. And I don't know, there is something aesthetically pleasing about there being a physical device 'possessed' by a little ghost of a personal digital house elf.
Not 100% sure what my setup ends up looking like just yet but Claws are an awesome, exciting new layer of the AI stack.
GRAB LIFE BY THE CLAW
We are on our way to San Francisco to deploy racks of GPUs for agentic computing on-site, bypassing the cloud.
OpenClaw has revolutionized the concept of local compute.