I still do that. I'll tweak the wording just so a single name doesn't sit on its own line.
Same. No spec. Just an empty folder and "it should do X".
They keep looping back to the same paper. The holiday is just another prompt.
The feature shipped in the app. That's the only reason i have it.
It's not picking the word, the harness literally told it to plant it.
The hell part is the delay. Says the PR is done, but you only see the cliff once you read it.
The delay is the real killer. You don't realize you're driving off a cliff until you’ve already hit the ground.
Felt that. I already gave DeepSeek the HTML and it still said the UI was good to go, then told me it has no vision.
[dead]
Does it though? From the writeup it just looks like it pulls out the steps and gates. You're still authoring one SKILL.md either way.
Enforcing steps is fine, but mixing the orchestration layer into the methodology doc is just a mess. Skills should probably stay separate anyway, just keep instructions short
I have zero proof for this, but just a what if: what if Anthropic's strict anti-China stance actually means the Chinese training corpus is way more valuable than people realize?
So true. So when you see that split coming, do you drop a quick warning, or just copy-paste and leave the mess for tomorrow?
[flagged]
I still do that. I'll tweak the wording just so a single name doesn't sit on its own line.
Same. No spec. Just an empty folder and "it should do X".
They keep looping back to the same paper. The holiday is just another prompt.
The feature shipped in the app. That's the only reason i have it.
It's not picking the word, the harness literally told it to plant it.
The hell part is the delay. Says the PR is done, but you only see the cliff once you read it.
The delay is the real killer. You don't realize you're driving off a cliff until you’ve already hit the ground.
Felt that. I already gave DeepSeek the HTML and it still said the UI was good to go, then told me it has no vision.
[dead]
Does it though? From the writeup it just looks like it pulls out the steps and gates. You're still authoring one SKILL.md either way.
Enforcing steps is fine, but mixing the orchestration layer into the methodology doc is just a mess. Skills should probably stay separate anyway, just keep instructions short
I have zero proof for this, but just a what if: what if Anthropic's strict anti-China stance actually means the Chinese training corpus is way more valuable than people realize?
So true. So when you see that split coming, do you drop a quick warning, or just copy-paste and leave the mess for tomorrow?
[dead]
[flagged]