Welcome to the Devin hands-on workshop. This repo contains everything you need to get started: lab instructions, prompts to paste into Devin, and links to the repositories you will work with.
- Find your workshop — check
workshops/for your session's lab guide, or ask your facilitator for the direct link - Pick a lab — each lab has a prompt you copy-paste into a new Devin session
- Kick off and move on — Devin works autonomously. Start the next lab while it runs
- Review the PR — when Devin finishes, review its pull request and leave comments to iterate
Devin works autonomously on its own machine. Once you paste a prompt and kick off a session, Devin runs independently — you don't need to watch it. Move on to the next lab, explore Ask Devin, or grab coffee while it works. You'll get notified when it opens a PR.
workshop-instructions/
├── modules/ ← individual lab instructions organized by discipline
│ └── README.md ← full index of all labs
├── workshops/ ← structured lab sequences (your facilitator will point you here)
│ ├── foundations/ ← theory, product features, platform mental model
│ ├── general/ ← broad multi-repo hands-on tour (start here)
│ ├── otterworks/ ← advanced monorepo deep-dive (300-level)
│ └── specialties/ ← deep dives by technical domain or job family
├── demos/ ← facilitator-led showcases (follow along, single linear thread)
├── events/ ← event-specific agendas and customizations
├── catalog/ ← reference inventory of all available repositories
└── shared/
├── general-themes/ ← how Devin works: architecture, patterns, collaboration
├── product-features/ ← feature tours for Cloud, Desktop, and CLI
└── runtime-resources.md ← how to run apps locally if needed
| Category | What You'll Try | Labs |
|---|---|---|
| Application Development | Build features, fix bugs, evolve schemas | 7 |
| Testing & QA | Linting, unit tests, E2E tests, performance, accessibility | 13 |
| Security | Dependency upgrades, vulnerability remediation, SAST | 7 |
| Compliance & Governance | License audits, PII detection, regulatory reporting | 3 |
| DevOps & CI/CD | Pipelines, PR automation, CI failure resolution | 5 |
| Cloud & Infrastructure | IaC translation, Kubernetes, Terraform, GitOps | 6 |
| Observability & SRE | Monitoring, incident response, anomaly detection | 4 |
| Data Engineering | DW migration, ETL modernization, data quality | 10 |
| Architecture & Design | ADRs, API review, dependency analysis, refactoring | 5 |
| AI & ML Engineering | ML pipelines, model evaluation, LLM patterns | 3 |
| Technical Documentation | Inline docs, API docs, runbooks, changelogs | 6 |
| Migration & Modernization | COBOL-to-Java, framework upgrades, containerization | 15 |
Browse all labs: modules/README.md
Your facilitator may have directed you to a specific workshop. Each workshop bundles labs into a structured sequence.
| Workshop | Focus | Duration |
|---|---|---|
| Foundations | Cloud agent theory, product features, platform mental model | 2-3 hours |
| General | Security, modernization, feature dev — broad multi-repo tour | 4-6 hours |
| OtterWorks | Polyglot microservices — 300-level monorepo deep-dive | 4-6 hours |
Collections of modules targeting specific tech stacks and engineering challenges.
| Workshop | Focus | Duration |
|---|---|---|
| COBOL Modernization | End-to-end mainframe modernization | ~4 hours |
| Legacy Modernization | COBOL/legacy → modern tech stack | 2-4 hours |
| .NET Cloud-Native Modernization | .NET monolith → Kubernetes-hosted cloud-native APIs | 2.5-3 hours |
| Framework Upgrades | Angular + Spring Boot version upgrades | 1-2 hours |
| Data Source Migration | Legacy DW → modern schema | 1-2 hours |
| Platform Microservice Decomposition | Monolith → platform-conformant microservices | 1.5-2 hours |
| Security & Compliance | CVE remediation, SAST, shift-left | 1-2 hours |
| Enterprise Security Automation | Event-driven SAST, mass remediation | ~4 hours |
| Agentic AI | Multi-agent systems, document processing | 2-4 hours |
One workshop per job family — broad coverage of the role's engineering concerns.
| Workshop | Focus | Duration |
|---|---|---|
| Application Development & Maintenance | Feature dev, bug fixing, code maintenance | 4-6 hours |
| Feature Development | New features on existing apps | 1-2 hours |
| Digital Engineering | CI/CD, cloud infrastructure, observability | 4-6 hours |
| Quality Engineering & Assurance | Test automation, E2E, continuous quality | 4-6 hours |
| Quality Engineering & Security | QE + security remediation combined | ~3 hours |
- Start sessions early, review later. Each lab has a "Paste into Devin" step and a separate "Review & Give Feedback" step. Kick off the session first, then use the wait time for Ask Devin research — Devin keeps working in the background.
- Run parallel sessions. Kick off the next lab while reviewing the previous one. This mirrors real enterprise usage where Devin handles work across many services simultaneously.
- Use Ask Devin to refine requirements. The better-defined a task is, the better Devin's output. Ask Devin helps you think through the problem before creating a session.
- Build up Devin's knowledge as you go. When Devin suggests a Knowledge item during a session, accept it — this builds a shared context layer that makes Devin more effective over time.
- Leave PR comments to steer Devin. After Devin opens a PR, leave comments directly on the diff and Devin will wake up and address them — this is the core workflow for iterating with Devin.
Some labs require a running application. See shared/runtime-resources.md for local run instructions. Your facilitator will let you know if hosted instances are available.
Looking for a specific repo? The catalog lists all repositories in the workshop org with descriptions, tech stacks, and links to the labs that use them.
Track your progress on the Devin Features Appendix — try to discover as many Devin capabilities as you can during the session.