Hey everyone! I'm looking to improve my team's development process in our startup where things are quite chaotic, mainly due to our inexperience with production code. We're working on core AI features and have realized we need to implement better practices like CI/CD pipelines and proper design patterns. Currently, our code is messy, with hard-coded prompts and no version control.
I'm considering whether to propose standardized design patterns for refactoring, such as establishing a way to manage instruction prompts more effectively. However, I'm concerned about how my teammates might react to these changes.
Is it worth pushing for these improvements, and do you think it's better to make these changes all at once or do it incrementally? I'd love to hear your insights!
2 Answers
It's great that you want to make things better! I’d recommend making incremental changes rather than trying to refactor everything at once. Pick a smaller service, implement a CI/CD pipeline for it, and demonstrate the benefits. This way, you can build a solid case for moving on to the next service without overwhelming your team. Smaller improvements are easier to review and less stressful for everyone involved.
Finally, a legit post that's not AI-generated! I feel you on the struggles. It might be beneficial to outline the potential risks of not refactoring. Show them how comprehensive testing and prompt management can lead to better outcomes in the long run. It could also help to highlight the issues with the current method to get everyone on board with change.
Related Questions
Biggest Problem With Suno AI Audio
How to Build a Custom GPT Journalist That Posts Directly to WordPress