Raw LLM Responses

@marcotroster8247except when it starts forgetting the context and even after teling it multiple times not to ie.: • change names of functions • change the logic or a core function because it’s used in 47 other files than just the one I need to be working on • not try and revamp the ENTIRE business logic just to solve the issue at hand The list could go on. No matter how good of a context you give it; unless you put it in a dedicated markdown file and use multiple agents with multiple .md files (1 for your data structures specialist agent, 1 for your UI specialist agent, etc. etc.); when the “clipboard gets full” and the LLM starts to “forget” things you already specified, and starts deleting/ignoring rows from the beginning of your chat/workflow (where you usually put your specifications initially); things start fallong apart. Context rot sets in and the whole workflow becomes an “I’m arguing eith the shittiest 16 year old very polite and eloquent intern, hopped up on energy drinks, who keeps forgetting what I asked for 45 minutes ago”; instead of the “working towards the dopamine hit after I solve the problem”. Vibe coding gives you no dopamine hit (at least not for me) when I solve a problem. It’s glorified copy-pasting. And when it comes to debugging, it’s basically “fake progress” because you’ll end up spending more time debugging the AI’s code which you didn’t review at all because the “development process” was ‘copy-paste the AI’s output’ instead of building a mental model that sokves the issue and then starting to write the code along the line of that mental model. Don’t get me started on the code quality of the AI or the hallucinations either. 😅