Earlier quoted context omitted.
> This ensures the LLM has a complete understanding of the overall goals Forget about overall goal. I have this simple instruction that i send on every request "stop after every failing unit test and discuss implementation with me before writing source code " but it only does that about 7 times out of 10. Other times it just proceeds with implementation anyways.
So it behaves just like a person.
Why agents are bad pair programmers
221–230 of 239 posts
Re: Why agents are bad pair programmers
#222I think this has put into words a reason why I bounced off using AI this way, when I need something done I often have a rough idea of how I want it done, and how AI does it often doesn't match what I want, but because it's gone off and written a 2,000 lines of code it's suddenly more work for me to go through and say "Ok, so first off, strip all these comments out, you're doubling the file with trivial explanations o…
Just like with human engineers, you need to start with a planning session. This involves a back and forth discussion to hammer out the details before writing any code. I start off as vague as possible to see if the LLM recommends anything I hadn't thought of, then get more detailed as I go. When I'm satisfied, I have it create 2 documents, initialprompt.txt and TODO.md. The initial prompt file includes a summary of t…
> I have it create 2 documents, initialprompt.txt and TODO.md.
That is an amazing approach. Which (AI) tools are you using?Re: Why agents are bad pair programmers
#223Earlier quoted context omitted.
Agreed. I find it interesting that LLMs seem pretty good at spitting out SQL that works well enough. But on the other hand LLMs seem pretty awful at working with CSS. I wonder if this is due to a difference in the amount of training data available for SQL vs CSS, or is this because CSS is a finicky pain in the ass when compared to SQL.
interesting. I've been having a great time telling the LLMs to generate CSS for me so I don't have to fight with tailwind
Re: Why agents are bad pair programmers
#224Earlier quoted context omitted.
> judgmental and condescending pushing back against judgement and condescension is not judgemental and condescending. > may not really exist I'm open to reading over any resources you would like to provide, maybe it's "real", maybe it isn't, but I have personally both experienced and witnessed the effect in myself, other individuals and groups. It's a good heuristic for certain scenarios, even if it isn't necesarily…
I would invite you to re-read some of the comments you perceived as judgement and condescension and keep an open mind. You might find that you took them as judgement and condescension unfairly. Meanwhile, you have absolutely been judgemental and condescending yourself. If you really keep the open mind that you profess, you'll take a moment to reflect on this and not dismiss it out of hand. It does not do you any favo…
I think if you read my own comments again you will realize I make no such assumptions at all, and have been open to criticism from those who made a genuine attempt to give feedback.
Re: Why agents are bad pair programmers
#225I think this has put into words a reason why I bounced off using AI this way, when I need something done I often have a rough idea of how I want it done, and how AI does it often doesn't match what I want, but because it's gone off and written a 2,000 lines of code it's suddenly more work for me to go through and say "Ok, so first off, strip all these comments out, you're doubling the file with trivial explanations o…
Just like with human engineers, you need to start with a planning session. This involves a back and forth discussion to hammer out the details before writing any code. I start off as vague as possible to see if the LLM recommends anything I hadn't thought of, then get more detailed as I go. When I'm satisfied, I have it create 2 documents, initialprompt.txt and TODO.md. The initial prompt file includes a summary of t…
Re: Why agents are bad pair programmers
#226Re: Why agents are bad pair programmers
#227I think this has put into words a reason why I bounced off using AI this way, when I need something done I often have a rough idea of how I want it done, and how AI does it often doesn't match what I want, but because it's gone off and written a 2,000 lines of code it's suddenly more work for me to go through and say "Ok, so first off, strip all these comments out, you're doubling the file with trivial explanations o…
Re: Why agents are bad pair programmers
#228Earlier quoted context omitted.
Second this. My solution is to have a 'non-AI' IDE and then a Cursor/VS Code to switch between. Deep work cannot be achieved by chatting with the coding bots, sorry.
I just cmd + shift + p -> disable Cursor tab -> enter Sure, you could just add a shortcut too. After a while, it turns into a habit.
Re: Why agents are bad pair programmers
#229Pair programming is also not suitable for all cases Maybe not for many cases I mentioned this elsewhere but I find it absolutely impossible to get into a good programming flow anymore while the LLM constantly interrupts me with suggested autocompletes that I have to stop, read, review, and accept/reject It's been miserable trying to incorporate this into my workflow
Code regularly, and use ai to get unblocked if you do so or review code for mistakes. Or have the ai write the entire first draft for some piece and then you give it a once over, correcting it either manually or with prompts.
The AI doesn't seem to be adding any extra value? It's not like it is more accurate that SO, or that it produces answers any faster, honestly
It just is much less trustworthy imo
Re: Why agents are bad pair programmers
#230Earlier quoted context omitted.
I usually add “discuss first. Don’t modify code yet”. Then we do some back and forth. And finally, “apply”.
Same. I use /ask in Aider so I can read what it's planning, ask follow-up questions, get it to change things, then after a few iterations I can type "Make it so" while sitting back to sip on my Earl Grey.