与「BAD」相关的搜索结果

I'm going to cancel Claude. It's just so bad, I can't believe it. It's just lazy. The most recent example: I have Claude check my inbox for important emails, summarize them, work with them, and send out replies if necessary. I caught Claude again simply not reading the email thread to the end and just ignoring the latest emails. When I asked him about it, Opus 5 just said: "Valid point. I didn't read it." I mean, seriously. What the heck? You have to babysit it every time.

C.J. Gardner-Johnson injured The Bills new safety went down, later clutched at his leg near his Achilles. Couldn’t put any pressure on his right leg as he was helped off the field slowly. Appeared non-contact Bad news for one of the Bills’ best defenders at training camp so far

Here is my AI investing guide. Sitting here August 2026, my current best thoughts are as follows: 1. LPS (Land Power Shell) is still the most obvious and fastest path to cash on cash returns. Lots of value can be assembled and traded quickly at this layer. And as data centers get more pushback, energized land can explode in value. Very bullish here. I’ve stepped into this layer very aggressively. My partner @anitavlallian and I have acquired almost 6GW coming online in a ramp from today thru 2029 of grid power and behind the meter. 2. Silicon - I helped get @GroqInc off the ground in 2015 and we licensed it to @nvidia for $20B Dec2025. I won’t invest or incubate anything in this layer now. The perf demands of the chips are too high, manufacturing precision is too complex and supply chain influence to get adjacent components like memory isn’t possible for a startup anymore. Lots of capital will be wasted here chasing Groq and Cerebras’ success. Note that both startups made sense a decade ago when these constraints were much more modest. 3. Clouds - Clouds are very very lucrative but very hard to build and very expensive and technically complicated to maintain. And as alignment becomes a more important issue, I expect the clouds will be asked to build robust KYC and attest to it. This makes the risk:reward ratio skewed. I don’t want to be responsible when the USG says a cloud allowed a bad actor to do something bad because of poor KYC. 4. Models are complicated. The big open question is how much of the revenue being generated by them today is because of tokenmaxxing and poor model behavior. If it’s a lot, then the annualized revenues will diminish meaningfully even as token consumption inflects upwards. This is the big economic question at this layer. 5. Harnesses are where the action is and why I started @8090solutions two years ago. In a nutshell, the harness helps enterprises owns their proprietary context (what Alex Karp calls their ‘alpha’). This is an enterprise’s data, workflows, evals, and business rules. A harness that gives this to an enterprise is what creates very low model-agnostic switching costs, which further reinforces my views of #4# above. 6. Applications will be another long term winner along with harnesses. This is where the differentiation between “off the shelf” and “custom time and materials” melts away. Every company, with the right harness, can now imbue their alpha into the software that runs their company. I expect this to mean that “off the shelf” is largely replaced with custom software creating a huge opportunity to write these solutions for companies. Build once and sell repeatedly is a laggard GTM motion for a SaaS world that isn’t needed here. Think custom by design, alpha embedded, proprietary by nature. Fin. Good luck to all the players!

Software quality now depends on the constraints you set around your agents. When humans manually wrote most of the code we could look at the code itself for signs of quality. Is it clean? Is it thoughtful? Is it fast? Can another engineer understand it? Does it have tests? Agents can now generate more code than people can read. When code generation scales beyond review, quality - checks for one or more of correctness, maintainability, security, performance etc - increasingly has to live somewhere else. It moves into the harness, environment and operating system around the agent. This can be the tests and deterministic checks that decide what the system is allowed to do (amongst others). Your constraints are what may eventually enable loops of agents to deliver production software reliably. They can include unit tests, property tests, acceptance tests, mutation testing and quality metrics. This back-pressure lets the system resist bad work before it becomes somebody elses problem. Set your constraints. They decide whether the code your agents generate is good enough to ship.