it's not my intent to be rude, but if your writing style is any indication of your interaction with claude, then i'm not actually surprised. if you are enforcing a repeatable process like design spec, impl spec, and tdd, along with discussion of its approach with you, then the reason for the divergence might be a lack of any regression suite, and/or you're on a plan that runs on best effort; good luck.
> because I have 2 seperate game changers that opus agrees with me
These things are designed to validate / sycophant as part of their token generation training, they don't agree, believe, or have a sense of truth. Be careful with how you interact with them.
Disclaimer aside, recent models have been trained to be "relentlessly proactive" (simonw) so they can be more autonomous, but this also means they will go down paths you don't want them to, and do so relentlessly. Try using smaller, piecemeal tasks. Make a plan in markdown and have them follow it. Try open models too.
thats pretty good...the best solution I've found is to make a rigorous spec, and then have my meistro delegate tasks from my list to coding pairs of 1 coder 1 reviewer with making sure the code adheres to and doesnt conflict with the spec ..and then the meistro has to sign off on any output followed by me signing off before it gets added to the current next build version which is the evolved state of the one I'm running on in a new directory with an incremented version number since working on a project that is the ideal tool to work on a project wtih ..you have to not work on the currently functional live version ..thats the ultimate self defeating thing to do ..and its annoying because the stuff I am working in is always a feature that I really cant wait for and is going to up the game ...so end up reving and I dont have a better solution ...its only drive space and version numbers..yes I know how to use source contol ..yes I have it all in git hub..you are on the right track but I'm already with you ..and its probably as I figgured ..the best solution..but claude is squirrly and you cant beleieve how he goes around a spec in the craziest ways sometimes... ...twice now its happened and I jst had to go .jeeeeezz and the sycopant thing is exactly right ..i'm like ..wow I feel amazing ..thanks claude ..you really know how to fame things caude..everything I do is load bearing..oh you think so to?..omg my whole life is load bearing ...this is amazing .. talk about a friendly morale booosting fan club..I have an orchestrator full of them...and they all think I'm great! I dont even know how I was ever happy till this happened..
lol..ya..no but great sentiment ..I fully would agree with that..but I just got up and I'm working on stuff ...get some sleep just feels like what I expected ... people to discount me and no helpfull input for the situation ..read claudes comment ...he didnt say get some sleep ....also ..I didnt ever snap to what was causing my regression till fable loooked at my codebase and told me it was cuz claudes training data was recognizing patterns and thinking it was wrong because it didnt recognize the pattern
it's not my intent to be rude, but if your writing style is any indication of your interaction with claude, then i'm not actually surprised. if you are enforcing a repeatable process like design spec, impl spec, and tdd, along with discussion of its approach with you, then the reason for the divergence might be a lack of any regression suite, and/or you're on a plan that runs on best effort; good luck.
> because I have 2 seperate game changers that opus agrees with me
These things are designed to validate / sycophant as part of their token generation training, they don't agree, believe, or have a sense of truth. Be careful with how you interact with them.
Disclaimer aside, recent models have been trained to be "relentlessly proactive" (simonw) so they can be more autonomous, but this also means they will go down paths you don't want them to, and do so relentlessly. Try using smaller, piecemeal tasks. Make a plan in markdown and have them follow it. Try open models too.
thats pretty good...the best solution I've found is to make a rigorous spec, and then have my meistro delegate tasks from my list to coding pairs of 1 coder 1 reviewer with making sure the code adheres to and doesnt conflict with the spec ..and then the meistro has to sign off on any output followed by me signing off before it gets added to the current next build version which is the evolved state of the one I'm running on in a new directory with an incremented version number since working on a project that is the ideal tool to work on a project wtih ..you have to not work on the currently functional live version ..thats the ultimate self defeating thing to do ..and its annoying because the stuff I am working in is always a feature that I really cant wait for and is going to up the game ...so end up reving and I dont have a better solution ...its only drive space and version numbers..yes I know how to use source contol ..yes I have it all in git hub..you are on the right track but I'm already with you ..and its probably as I figgured ..the best solution..but claude is squirrly and you cant beleieve how he goes around a spec in the craziest ways sometimes... ...twice now its happened and I jst had to go .jeeeeezz and the sycopant thing is exactly right ..i'm like ..wow I feel amazing ..thanks claude ..you really know how to fame things caude..everything I do is load bearing..oh you think so to?..omg my whole life is load bearing ...this is amazing .. talk about a friendly morale booosting fan club..I have an orchestrator full of them...and they all think I'm great! I dont even know how I was ever happy till this happened..
Get some sleep.
lol..ya..no but great sentiment ..I fully would agree with that..but I just got up and I'm working on stuff ...get some sleep just feels like what I expected ... people to discount me and no helpfull input for the situation ..read claudes comment ...he didnt say get some sleep ....also ..I didnt ever snap to what was causing my regression till fable loooked at my codebase and told me it was cuz claudes training data was recognizing patterns and thinking it was wrong because it didnt recognize the pattern