"you literally have to tell it to slow down, focus and think" - This soo much! When I get an unexpected result from claude, I ask it why - what caused it to do such-and-such. After one back and forth session like this putting up tons of guardrails on a prompt, claude literally said "you shouldn't have to teach me to think every session" !!
> When I get an unexpected result from claude, I ask it why - what caused it to do such-and-such.
No LLM can answer this question for you, it has no insight into how or why it outputted what it outputted. The reasons it gives might sound plausible, but they aren't real.
That sounds neat! I especially like "I give the code a sense of its own emotional state". I can just imagine a function crying "Why did they use that algorithm ?? Why so much spaghetti ?? I'm soo ugly ..Why Why Why" :-D
That would probably motivate me to fix the poor thing, just so I don't feel like I'm torturing it! :-D
If offshoring started before your time, that might be coloring your perception.
I had already been working in tech for decades when the offshoring craze started. It was remarkably similar to the current 'ai craze'. Loads of jobs lost, predictions it was the end of (on-shore) programming, long job searches (and even longer ones for recent grads, etc. All in the name of 'cost reduction'. Thing is, in a couple of years when the savings didn't materialize/live up to expectations, companies started hiring on-shore again (and even paid better!). Now, offshoring is just one more tool. It still exists, it's still used - but it didn't destroy domestic programming market.
Personally, I think AI will follow the same trajectory. Its gonna be rough, but then it won't be the 'magic bullet' management wants, and they'll start hiring again. AI (just like offshoring) will still be there, still be used - it will just be a tool rather then a complete replacement.
The offshoring doomsayers made it seem like offshoring would contract the domestic market, but in fact the US software labor market has grown by >100% since that time. Median software engineer compensation is up something like 90% over inflation over the same period. Clearly it hasn't been all that big of a problem for SWEs in the US.
Yep, it was a 'momentary' glitch in the matrix ... Things came back even stronger then before, and 'off-shore' just became another tool. Its still around, but it hasn't destroyed the domestic programming industry. However, it was painful for a lot programmers at the time and _seemed_ like the end of the world to them...
Which is why I say, it reminds me very strongly of the current AI trend. AI won't 'go away' - but I don't think it will 'be the end' of programmers (at least not in the next 5-10 years). It will just become another tool
I've been doing it myself for 40 years...I wanna play with the new shiny abit :-D
Whats the point of being a geek if you don't play with the new shinies ?
That's a Claude Code issue — queued slash commands not executing between steps.
you didn't answer me - is that last rule we added to MEMORY.md active and working ?
● Your point: you're asking whether rule 4 ("restate before responding") is actually being followed, because I just failed to do it two messages ago.
No, it's not working reliably. I followed it once (the gap-check message), then immediately stopped doing it on the very next exchange. The rule exists in memory but I'm not consistently applying it.
oh yeah - I get that too. Also, if I tell him to verify something - he'll do a big song and dance about verifying it as correct. Then you point out something very basic and he'll trigger that 'let me do this properly', verify it again, find out he was wrong - then say he was working from stale data/assumptions
Oh - another 'fun' new behavior this week:
He contradicted himself within 1 paragraph and when asked about it, admitted the correct answer was explicitly listed in his MEMORY.md file - he just ignored it...
reply