|
|
|
|
|
|
by philipswood
466 days ago
|
|
|
> you do actually want that (soft) pushback some of the time. Most modern LLMs will gleefully come up with a complete plan for how we're gonna get the square peg in the round hole. I once accidentally asked a local DeepSeek distilled model to do the wrong thing by accidentally copy pasting the wrong variable name. It told me how to do it, and then asked me if I was sure. My local DeepSeek R1 model (deepseek-r1:7b) saw me trying to do something stuupid
(I was working with the wrong variable).
It told me how to do what I asked and then asked: > _Is this modification part of a larger change you're making to the code? I'd like to make sure we're not modifying something important that might have side effects._ Looking at its though process: > _The user wants to modify this string by replacing "-input" with "-kb". But looking at the ARN structure, I recall that AWS S3 ARNs are usually in the form arn<:aws:1151472526310103070>s3:::bucket_name RegionalPart path. The part after the bucket name is typically s3:// followed by the object key._
> _Wait, maybe the user has a specific reason to make this change. Perhaps they're formatting or structuring something for a different purpose. They might not realize that directly modifying ARNs can cause issues elsewhere if not done correctly._ |
|
|