4 ms·
I had horrible experience with a number of ai tools for infra-as-code. My theory is, that in that case it’s hard to predict what to do from context and librari
by niemandhier 2y ago
I had horrible experience with a number of ai tools for infra-as-code.
My theory is, that in that case it’s hard to predict what to do from context and libraries are at the same time hyper specialized and similar.
Example:
Creating a node and attaching a volume using ansible looks similar for different cloud providers but there a subtle differences in how to speciy the location etc.
- lars_francke 2y agoThis mirrors my experience. I've tried various tools (including Cursor) and my problem is that they often (more than 50%) generates non-working code. Why does it do so? Because the ecosystems change so fast and they have been trained on old versions of various libraries (by definition) but when I use the latest version it's a constant uphill battle. And there are so many different combinations of how to use libraries together.... I can't be the only one facing this issue but I didn't see a lot of discussion around this. So, as someone said: It's generating at most average code and most of it is outdated and sometimes vulnerable because... Well that's what's out there. I still use these tools but mostly to know how a solution could look roughly and then start to do my own research and to avoid the black page problem. Sometimes just to learn what to even Google for especially in ecosystems I'm unfamiliar with.