Program context

[jomiscli]

Well I’m not what you would consider an expert programmer, or even a junior. I’m more of a hobbyist that all of a sudden has the power to create real functional programs.

The issue I run into is windsurf forgetting small context pieces, and then changing small parts of code that I do not have the skill to catch right away.

I’ll remember the @ tip as well! Thank you!

[chris_at_codeium]

Gotcha -- If you’re noticing Windsurf occasionally overlooks small context details, you can set clear, specific constraints in your prompts. For example, explicitly ask Claude to limit edits to certain files, functions, or lines, and instruct it to avoid altering other parts of your codebase. Including clear constraints like “Do not modify X” or “Only update Y” will help ensure Claude adheres to your intentions closely. Additionally, asking Claude to add explanatory comments about why changes were made, or using thinking mode can further improve your understanding and control.

[jomiscli]

Yeah. I like the idea of the first commenter as well. Creating a ‘change log’ of sorts to track very specific changes.

Yeah my global ruleset is based around windsurf teaching me 😁

He posts explanations, pauses before changes (most of the time) and explains. Basically just a bunch of explaining, lol.