Using springdoc worked a lot better but uncovered some ugliness in generated code that I thought I had fixed - not all REST APIs using DTOs to define payloads. Ugh.
Strangely the thing that Windsurf is having the most problems with is generating accurate OpenAPI for REST APIs. Seems like this should be simple and I need it for generating the client. But each iteration just keeps introducing new garbage.
managed to vibe code my backend but that's because i know my way around java conceptually. now it's time to do the front-end, and i don't know JS. so asking ChatGPT to teach it to me.
Having cursor generate my prompts based on my existing code so that new code gets inserted correctly has put this shit on rails. I know, welcome to the party John...
I'm not technical enough to read through the code and figure out what my app is doing, so I asked Windsurf to document the architecture. The doc can't even get the API responses of the REST APIs right.
Building out the test suite is where shit got crazy. Went into a long loop of "test fails, let me try to fix that, oops more tests failed, let me try to fix that".
First thing I learned vibe programming with Windsurf - don’t try to let it install the software stack. Install everything yourself, get services running, etc before starting. (Bit worrying that it got install cmd for mongodb wrong.)
I'm a tech-savvy product guy. 20+ yrs in developer tools and runtimes, mostly Java and JavaScript. I understand what all the moving parts do at a high level, but I can't code for shit.
Time try out vibe programming. I'm starting with Windsurf. Any tips?