Skip to main content

Best Practice Workflow

tip

Always keep your code source controlled. That will enable you to selectively rollback the changes if you don't like what Priset did.

  1. Select Your Mode: Ensure the Model/Mode Dropdown is set to "Developer" for general tasks.
  2. Start a New Session: If you are starting a new task, click the New Session Button to clear the context. More info about using session is given in this article.
  3. Write Your Prompt: Clearly describe the task in the Prompt Input Box.
  4. Execute: Click the Run Button.
  5. Review: Analyze the code, diffs in the appropriate IDE windows to see if you like the changes made. Check the explanations in the Main Conversation Pane. Sometimes Priset will ask for the user input and would indicate so as part of the conversation.
  6. Rollback: Undo the changes if you don't like them. You can also undo the changes selectively and keep those that you like.
  7. Test: Test your application to see if the new functionality works as expected.
  8. Fix: If things don't work as expected use the same session to report the problem, exception etc. and request Priset to fix them. You can attach screenshots, word or PDF documents that provide more details.
  9. Check In: After the successful testing check in the changes to your source control repository.
  10. Iterate: Continue the conversation with follow-up prompts until all tasks are complete.
alert

AI is not infallible and it cannot / should not replace humans. If you see that Priset has started doing changes that you haven't anticipated you should hit the Stop button. You can then use the same session to clarify your prompt and provide more details or start all over. Check Using Sessions for more details.

pro tip

Priset will automatically build the solution in order to check for build problems. Nevertheless, even if the solution builds properly it may have runtime errors and bugs. If you see that the runtime errors and bugs are related to the changes just made, use the same session to report them (so Priset would understand the context of the reported issues). Otherwise, when errors and bugs are not deemed related to the changes just made, report them in a new session. Check Using Sessions for more details.