Yes, I've also hit it with Opus 5.5, but on way fewer projects. My long standing projects that I marked as failed/to-soon with 4.8 have entered the grey area of slow-progress-with-handholding like smaller projects did…
What's the end goal of actively harming what's fed to an AI if you already detected it and could have blocked it by then?
Works on my mobile
No, the tooling I make has better UX very quickly. It is built for their financial goals, not for the end user.
You also set up Hormuz and tariffs and spread discord between EU citiz ns through speeches of high officials and threaten Greenland, causing us to prepare to defend on multiple fronts while often publicly supporting…
I recognize the feeling of handholding and have the tingles telling me that given the step change of Opus 5.5 and what passed by in the news lately, agent swarms are about to become mainstream. That's exactly what a…
It's funny how you describe something very close to what I was attempting to design. It was meant to trickle down from tickets to deterministic code. Data wise, it should be like a pyramid of tickets diluting layer by…
Yes, I've also hit it with Opus 5.5, but on way fewer projects. My long standing projects that I marked as failed/to-soon with 4.8 have entered the grey area of slow-progress-with-handholding like smaller projects did…
What's the end goal of actively harming what's fed to an AI if you already detected it and could have blocked it by then?
Works on my mobile
No, the tooling I make has better UX very quickly. It is built for their financial goals, not for the end user.
You also set up Hormuz and tariffs and spread discord between EU citiz ns through speeches of high officials and threaten Greenland, causing us to prepare to defend on multiple fronts while often publicly supporting…
I recognize the feeling of handholding and have the tingles telling me that given the step change of Opus 5.5 and what passed by in the news lately, agent swarms are about to become mainstream. That's exactly what a…
It's funny how you describe something very close to what I was attempting to design. It was meant to trickle down from tickets to deterministic code. Data wise, it should be like a pyramid of tickets diluting layer by…