|
|
|
|
|
by IX-103
27 days ago
|
|
In my experience, its the opposite. The AI is very good at writing code, but it is unreliable at any kind of design. I use it as a fancy form of autocomplete. I give the broad strokes: "add a method here and change all but this one caller to use the new method", "Apply this design pattern here for this change but don't do this other thing". It completes the task reasonably well and sometimes even remembers to run the code formatter and check that tests pass. If I ask it to me produce a design, I'll almost always end up with something unworkable or inefficient. Though if you push it hard enough then it can sometimes give you a good description of what existing code does and how it does it (which can be easily verified). |
|
Every thread is endless back-and-forth between the "AI works great and vibe coding is the future" and "no, AI works great as long as you don't vibe code" camps.