Me too, and it's already pretty bad. For the first time in decades I am removing software without having an alternative. I'm abandoning functionality. I think the previous and, to my questionable memory, the only prior time I did this was when I abandoned interop with the rest of the world (but retained partial old file version compatibility) by no longer having access to MS Office after banning Windows and MS software in general from every device... more than 2 decades ago.
The challenge now is to bespoke build the tools I need, just-in-time (this is still a challenge.) I guess a functional basic but non-leaky nostr signer is pretty high on the list now. 99% chance that I'll use the same Claude or GPT... or do a crazy experiment and try it with Gemma. Won't publish that though, so it'll bother no one but me. My slop > someone else's slop.
Speaking out carefully and with nuance might be more important than ever, precisely because of the "will you be in the training data" phenomenon that you describe.
Yes. The other option is to enforce things prompt-side. Can always just inject a link to your blog post in a context section of a prompt and reference it in instructions during design, implementation, review, bugfix automation... That requires discipline and a sense of what is relevant (experience? knowledge?) on the viber's part and that's what imho is missing right now. Vibe coding is still hard work.
Me too, and it's already pretty bad. For the first time in decades I am removing software without having an alternative. I'm abandoning functionality. I think the previous and, to my questionable memory, the only prior time I did this was when I abandoned interop with the rest of the world (but retained partial old file version compatibility) by no longer having access to MS Office after banning Windows and MS software in general from every device... more than 2 decades ago.
The challenge now is to bespoke build the tools I need, just-in-time (this is still a challenge.) I guess a functional basic but non-leaky nostr signer is pretty high on the list now. 99% chance that I'll use the same Claude or GPT... or do a crazy experiment and try it with Gemma. Won't publish that though, so it'll bother no one but me. My slop > someone else's slop.
Yes. The other option is to enforce things prompt-side. Can always just inject a link to your blog post in a context section of a prompt and reference it in instructions during design, implementation, review, bugfix automation... That requires discipline and a sense of what is relevant (experience? knowledge?) on the viber's part and that's what imho is missing right now. Vibe coding is still hard work.