For presenters
Run of show
A good format is to demo a few labs live and then let attendees work through the rest on their own. The presenter notes describe what Devin should find in each lab, so keep them to yourself.
Suggested flow
- Start the architecture review live, since it needs no setup and finishes in a few minutes.
- Walk through a finished Devin Review and the pull request from the security lab.
- Start the six-repo audit and come back to its results at the end.
- Post the bug report in Slack and show Devin replying in the thread.
- Send attendees to Setup and then to the first lab.
The migration, performance, six-repo audit and iOS Safari labs take a while, so start them before you begin talking or show a finished reference session instead.
Reference sessions
These are finished runs of every lab, visible to members of the Devin org they ran in.
- Architecture review of an unfamiliar codebaseOpen the finished session
- Review a pull request with Devin ReviewOpen the finished session
- Find and fix security vulnerabilitiesOpen the finished session
- Fix a slow API endpointOpen the finished session
- Migrate a Java 8 app to Java 17Open the finished session
- Implement a feature from a specOpen the finished session
- Reproduce an iOS Safari bug on macOSOpen the finished session
- Write a repo skill from a failed runOpen the finished session
- Set up a repo's environment and KnowledgeOpen the finished session
- Analyze a churn spikeOpen the finished session
- Audit six repos with a Dynamic WorkflowOpen the finished session
- Fix a production errorOpen the finished session
- Triage a bug report from SlackOpen the finished session
- Schedule a weekday health checkOpen the finished session
- Start a task by voice, continue in Desktop or the CLIOpen the finished session