Knowing the cost of home ownership, it’s not unlikely to imagine the reported damages are well within what he’s asking. Given that repair work, filing paper with the courts, etc is a major PITA, if this guy was just looking for a payout you’d think he’d ask for a lot more.
Perhaps it's just regional, but I've been noticing more and more people saying "chat" to describe ANY ai chat interface including ChatGPT. They might have a Kleenex problem on their hands.
Doubtful these clowns even have commercial insurance for these rentals. What a deceitful and dangerous way to build a business - to save (what?) a few thousand per rental?
I had the opportunity to live with Drew back in 2006 when he, I, and another pair of YC founders Adam and Matt were living together and hacking away at our own startups in Cambridge. I remember Drew being a hard worker, humble, and a genuinely nice guy. It's probably self indulgent to claim that we all inspired him to eventually shift gears to Dropbox and apply to YC - but what a path it's been for him! I've always felt inspired by his meteoric innovation in cloud storage - Dropbox paved the way for all our modern cloud storage systems. We've fallen out of touch over the years, but I wish him well on whatever comes next.
Love the concept! Some feedback: I went to sign up to give it a go, but the set up process left me feeling a bit untrusting - so I backed out for now. I'd prefer more explanation about what to expect, what I will get, how it is safe, etc before asking me to run a prompt.
Right now, the prompt will enumerate all the services and install the OpenTelemetry SDK (https://opentelemetry.io/) in each service.
Then for every service, the skill will make sure that:
- Every time something breaks and an operator needs to take a look, there's an error log
- All important steps in a process emit info/debug logs (so that an issue can be investigated)
- Operations are covered with spans with relevant attributes.
- Cost (LLM tokens), API performance (latency/RED), tenant activity (cost/usage per tenant) are covered by metrics so that you can use Superlog MCP to build cool dashboards.
For most common stacks like NextJS, FastAPI, React Native/Expo etc. we have a custom skill that explains the best practices for this specific technology. For all the other stacks we ask the agent to use general best practices.
We have evals for all custom skills where we start from a starter project, run the agent with the skill and use LLM-as-a-judge to compare it to a human-written 'golden patch'.
In general, we try to:
- minimize diff, so that the instrumentation is easy to review
- make small chunks of additive diffs vs huge indents / moving logic around
- minimize new dependencies
- use well-supported and audited OTel SDKs vs custom libs
I agree with this sentiment. And it's hard to change. But there are plenty of examples of people exiting the normalized system and choosing a different life. Even small changes can make a big impact on mental health, like stopping reading the news.
But I'd encourage the author to consider what setting an example might look like for them. What does a less complicated life look like? Then live it, and eventually, more will follow.
[BestInterest](https://bestinterest.app) helps coparents find peace by automatically filtering out anything that isn't child-focused from their coparent's messages. Ensures court order compliance and reduces conflict.
It seems strange to me that our laws allow someone to declare personal bankruptcy to avoid paying on liabilities, while somehow maintaining interests in other companies…
resulting in that weird situation where another of his companies tries to buy the “bankrupt” company? (If you didn’t read the article, the only other bidder against the Onion was one of Alex’s own companies)
Jones is a grifter, but I almost admire his brazen attempts here. If he is successful in any way, he is doing a service to point out the flaws in the systems.
Yeah, it was fast. And yet, for it to work financially, they were still using plain old USPS. The trick (which required the levels of volume they had at the time) was to have a bunch of distribution centers positioned all throughout their service area. For a modern day service trying to do the same with significantly less volume, they won't be able to afford the extra distribution centers.
We also (I worked there at the time) had software that basically said, "Joe watches all of his disks every weekend and drops them in the mail on Tuesdays, let's just assume he's going to do that and ship his new disks Monday morning". And other such predictions.
If you had a very regular viewing behavior you could have your new disks the same day as you shipped your old ones. To the customer, it was magical.
reply