I love watching football, but this season feels worse than ever. Game after game yesterday there were insanely bad calls. It’s honestly not even fun to watch anymore.
This is gonna kill the NFL.
Hey @grok, was the unnecessary roughness call against Cam Skattebo today, the worst penalty called in an NFL game ever?
Why big companies are struggling to move faster with AI.
1. Let’s have a meeting to get everyone aligned.
2. Simple solution but we need a PRD before anyone can do anything.
3. Someone uses AI to generate said PRD that is mostly nonsense. Most people never read it.
4. 2 weeks later someone says they are confused on what needs to be done. So another meeting takes place.
5. A new document is generated that inevitably no one will read.
6. I get escalated too, and try to figure out why this is complicated. Then I realize some people have opinions that make no sense.
7. I call this out, and end up still being told we need another meeting and a document.
8. If I was high enough up, I’d not allow any of this.
When in fact I could have just built the thing in 2 hours myself.
Some days I get so frustrated, that I wish I could just be okay with this so I’d live a much less stressful life.
I think this is healthy for the space, more consolidation. Augment team is top notch
Big news from Augment Code.
We've agreed to sell Cosmos, Auggie CLI, the Code Context Engine & related tech to @harnessio, the Autonomous SDLC Platform. Harness's integrated ecosystem provides the ideal home to deliver these capabilities at true enterprise scale.
We started Augment to help enterprises build software faster. As AI generates more code, orchestrating it reliably at scale has become the real bottleneck.
At Harness, our team will continue this work by bringing software factory capabilities to its Autonomous SDLC Platform.
Thank you to our customers, partners, investors, and team.
Read the announcement: augmentcode.com/blog/augment…
Man I wish I had time to join this debate. But on the point for models being nerfed.
What I can say factually is back in Sonnet 3.5 days I had tests I’d run to evaluate laziness. And there would be weeks where it would score just fine and then periods of hours where the model would consistently reduce its response. I had automated tests I’d run every 3 hours 7 days a week.
I had a structured output test with increasing items returned in an array. With explicit instructions to always return the fully number requested.
It would until it wouldn’t, and then it would add
… add more here.
I’d be surprised if there weren’t levers of response or reasoning being adjusted possibly dynamically.
Replying to @theo
@theo, it's very clear you're jealous of BridgeMind.
Some of your questions were fair. I'll be sharing more on the NerfBench methodology soon.
But asking me to take NerfBench down and post an apology written by you isn't about better benchmarks.
It's about your ego, and not wanting anyone else to exist in this space.
More benches are good for everyone. Build yours.
Tech drama is the best drama 🍿
You are a struggling second tier competitor that is more unethical and lying just because you have no decency or sense of proper behavior and shows your desperation. Straight out lying about if Chris being fired I thought would be below even you.
Readers added context they thought people might want to know
Khosla is an investor in both Cognition and Factory. khoslaventures.com/category/enter…
Finally had some time to really see what Jev can do, and holy smokes I have an infinite number of use cases to test now.
Opus 5.5 and Astra are both incredible, the downside is I now need to upgrade my Claude code plan too.
Seeing people build MCPs for agent harnesses they own instead of native tool calls hurts me.
MCPs are meant to allow your functionality to live in someone else harnesses.
I’ve been told this is called being a meat proxy.
I am done with this shit. It is over. The state of engineering right now is horrible. It has been half a month since I started a new role at a big company. Nobody knows anything here. The specs, code, tests, PRDs, tickets, resolution of those tickets, reports, etc., everything is made by Claude Code. Nobody on my team likes this. They are being forced to ship as much as they can. I have heard multiple times from higher management that pushing code is not a bottleneck, so why are we slow? People are working 12 to 13 hours a day just to press enter. Nobody is reading anything. Humans in corporate are doing nothing on their own. Everyone, literally everyone, from an L1 to an L7 engineer here is doing the same thing. Talk to Claude. There is no sense of victory. Nobody is resolving bugs. In reality, nobody is thinking anymore. Everything is done by LLMs. It is so soul-sucking. I would not mind it, to be honest, if we were at least given the time to check out the code and see what is going where. But no, the goal is to just ship. No matter what happens.
I had a 3 hour drive yesterday and kept thinking about all these AI doom claims.
The one thing I landed on is how in the world would anyone feel good about investing into OpenAI, SpaceX and Anthropic now?
It’s either we slow down and valuations need to come way down, or if for some reason there is real liability on these companies that they can hurt humanity the companies would be sued into oblivion. Anthropic would have to completely change its IPO plans now.
I also keep thinking about the severe lack of evidence provided other than Jacob’s 10% claim that isnt backed by anything factual.
Playing game theory here, if we end up with a big government AI agency responsible for regulation of AI, it could kill open weight models, and make it where government can control what it believes AI can and can’t say. Why would these companies want this?
Tinfoil hat on.
What if we are hitting limits and the best way to cover this up is to use safety and slowing down as the driver.
We Must Pace the Frontier: I’ve written a new essay on why the AI industry should slow down, with a three-part plan for doing so.
Anthropic is unilaterally committing to the first of these steps. We’ll provide third-party evaluators with permanent, employee-level access to our systems, so that they can verify adherence to our safety measures, report on incidents, and assess models’ alignment during training.
You can read the full post here: darioamodei.com/post/we-must…
Seeing so many non techy people prefer working in Claude Desktop over logging into a website.
I think I might of underestimated how quick that would happen.
Do SaSS companies just accept this and work on improving their product in ChatGPT and Claude or do they try to compete with their own offerings?
Nothing more frustrating then trying to stop someone from building in a way that you firmly know won't work. You try to redirect the team and help them understand what you've done that proves the approach won't work.
But the team charges on, 3 months later the team is just now realizing they should of gone the direction I pushed for. Folks get frustrated because now everything needs to be changed.
Its painful watching people running towards a wall and you try to redirect them. I guess some people need to bang their heads a few times.
An engineer called me over the weekend to help him with some problems. I ended up spending hours with him. What I found is he had gotten so reliant on AI that he wasn't even thinking about the customer experience, the product, the outcome.
The best engineers will focus on the customer.
He was so focused on using AI to automate everything, (he's in qa automation) that he wasn't even thinking about what should be tested or not tested. He was getting beat up on the number of defects that were making their way into customer hands.
Its a small startup with less than 10 people there.
He showed me his pipeline of work, which basically consisted of taking a PRD from a PM with AI generated AC (which was really bad) and then feeding that AC into Claude to generate a bunch of tests. When the tests pass, he would greenlight the new feature.
I gave him a ton of advice, and worked through some ways we could improve the workflow. But the bottom line imo is you do need to have some level of human involvement, even if its validating and just thinking for a few minutes on if the right things are being tested. For example one of the AC was "XYZ modal works"
Not to mention i'm super skeptical of QA automation, always have been, and with AI I kinda think we could probably have computer use do what it needs to validate major end to end workflows.
I’m surprised how many people disagree with this. As humans we have limited cognitive load, and as systems expand it’s why we organize around domains.
Eventually codebases outgrow what one human can keep in their head. There’s a book called Team Topologies that does a really great job of helping understand how we scale engineering organizations.
But you should understand the codebase very highly in your domain. You should understand upstream and downstream impacts. And if your codebase is small, you should definitely understand the entire thing.











