undefined
@sigmasternchen @leah I feel we are pretty on the same page then and I have misunderstood your initial post as well.
And yeah, vibe coding a small CLI for example as a useful tool to handle a certain kind of operational problem is really nice. I have a CLI where I do not care for the code at all, just the tests.
@sigmasternchen @leah I have had problems, where the AI was of no (substantial) help to me. I cannot say if this was due to my lack of context engineering skill at that time. But I really like the AI as a sparrings partner, given a predefined workflow and some "fixed" requirements.
But in no way do I see this as a replacement for my job, the AI is nothing with me doing the context engineering. As for the other problems, they sure await new solution strategies.
@sigmasternchen @leah I feel different. For me it is a tool to craft software. Being experienced helps me to shape the output. As every tool, it has a learning curve. But in many cases, it helps rather than it hinders. I would compare it to the usage of an IDE (as opposed to a text editor).
@nixCraft while you have a point, what you write dos not apply in full intent to all of them. ChatGPT for example gives citations and links to web findings so the user can jump to the original content when performing web research.