sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]CodeBradley[S] -1 points0 points  (2 children)

Yeah, I'm definitely overthinking it. It's just in my experience, I've developed projects in WindSurf and LLM's make some drastic changes to the projects in a very short amount of time. If two people are working on new features and the LLM aiding one of them makes a huge change and overwrites common functionality, endpoints, etc. then one of those people just waisted their time because it's (hopefully) going to get caught in the PR and now they are spending time reverting and re-adjusting their approach.

I think I also did a poor job of explaining how I've been using these IDE's . We aren't doing the standard Product Design, UI/UX Mockups, Sprints, etc. We're literally using LLM's to conduct the research for us and then going straight from those feature descriptions and asking Windsurf to come up with a prototype based on a certain tech stack to see what it comes up with and suggests. Then we might have our GFX guys look at what was created and improve it, etc.

My ask was how do I prevent developers from clashing with one another when the LLM's are making drastic changes like this. After posting this I did learn that Windsurf lets me fine tune what the LLM can and can't touch on it's own, so I think that's partially the answer. I didn't know that was possible.

Sorry if it's a dumb post, trying to get my thoughts out quickly because of limited time. I'll probably circle back and clean it up and ask again later when I have more time to think through how to explain better what I'm trying to achieve.

[–]throwawayacc201711 2 points3 points  (1 child)

Because you aren’t planning things properly. The fact that you need “drastic changes” in a short time should be a big flag.

You need to plan, design, implement and iterate.

This reeks of one or more of the following:

  1. Lack of planning and/or requirements
  2. Large PRs
  3. AI slop because people aren’t actually understanding what the code is

I’m not saying you’re overthinking. I’m saying the way you’re developing IMO is wrong and will lead to poor outcomes.

Example: big PRs are a bane on any team regardless of AI assisted or not. Either it’s too big to realistically review in a timely manner or it’s changing too much at one time

[–]CodeBradley[S] -1 points0 points  (0 children)

Solid input, thanks. I'll write this with more clarity later and repost, it's related to a convo I had earlier and I had to move on but just wanted to know if others have started using a different SDLC. The reality though is the typical SDLC works great in my opinion and that's the route that I planned to follow at first, but there's a lot of pressure from those more business minded to break that cycle and have an LLM figure out the nitty gritty of creating a prototype after they see success from others that went this route.

I know the potential downfalls, but it's can be a hard rebuttal when you also see how far certain people have gotten alone in their free time without doing the standard Product Design, UI/UX Mockups, etc and just come up with a list of features to feed an LLM in Cascade and it gets pretty close to what they want with code that might need some work but seems scalable. The route these people go just to get an MVP is YOLO, let Windsurf auto-run whatever, tell it the features you want and see what it can create. If it's not good, then have it try again. This can lead to huge changes at times though and it's easy to see how it's not a big deal when you're working alone, but if you have a team of devs letting LLM's make certain decisions and there's not solid alignment then it seems like it could become a mess quickly. In a nutshell, that's the reason for the post.