Skip to content

Devin course · Included in Osum membership

Hand Devin a ticket, merge its work.

You handed over a ticket. The run went off the rails, you corrected it, and the summary still said done. That is the babysitting loop, and it survives every plan tier. Learn the Defined Done: the scoped ticket that comes back proven, and the review that decides what merges.

  • Lesson 1: your first fix, back and checked in 15 minutes
  • By lesson 12: a weekly pipeline, three tickets deep, proven and merged
  • No new stack to learn. Your repo, your tests, your merge click
Get my Devin plan About 2 minutes. Lesson 1 is a real fix you can use the same day.
Would you merge this pull request? Try it first ↓
Lesson 1: Get your first Devin fix back in 15 minutes
12 hands-on lessons36 exercises1 certificate for LinkedIn30 courses in one membership

Sound familiar?

You wanted an engineer. You got a run to watch.

“The promise was full autonomy, but the reality still involves a lot of babysitting. You give it a task, it goes off the rails, you correct it, it sort of gets back on track.”

Devin user

“when people got to use it it was slow and code didn't work”

Devin user

“you need an organization that's very AI-friendly in how the whole tech stack is set up plus a lot of tweaking and setting up to get it to that level.”

Devin user

More tweaking rarely fixes it. A scoped ticket with a definition of done usually does. That’s the Defined Done, and this course teaches it.

What you’ll be able to do

Hand work to Devin. Merge what it returns.

A scoped ticket card is handed to Devin before the session starts.01

Hand off the first ticket

Your first real fix comes back in lesson 1, checked against its tests the same day. From there, every ticket leaves with a definition of done, so Devin stops guessing where done is.

A tray of proof: test output, screenshots and a recording beside the pull request.02

Get proof, not promises

The proof lives in the ticket: test output, screenshots, a recording. A claim without its artifact goes back as one comment, so review starts from evidence.

The machine tower boots ready from a snapshot with secrets in their drawer.03

Set the machine once

The snapshot, the repo rules and the secrets mean every session boots ready. Setup is paid once, not per ticket, and credentials never enter the chat.

A playbook booklet attaches to a new ticket by its short macro.04

Turn the run into a playbook

Your scoped run becomes a playbook with a macro. Every next ticket starts from the same proven procedure, corrections included.

The weekly watch runs on a schedule under a spending leash.05

Run the weekly watch

Recurring tickets start themselves on a schedule, bounded by a session cap and an invocation cap, with email only on failure. You review; the watch queues.

The four-check review card decides a merge.06

Merge only what you checked

Proof, diff, status, boundaries: four checks, every pull request. Agent or teammate, the checklist decides, and a failing check goes back as one comment.

The 60-second check

Would you merge this pull request?

Devin says the bug is fixed. You have the ticket, the diff and the summary. Make the call the way you will on every run.

The ticket

FieldThe ticket says
BugThe booking form accepts past dates
ReproPick yesterday, submit, the booking goes through
Definition of doneSubmit rejects past dates, the form's test passes, no other file changes
Proof requiredThe test output shown, not claimed
  1. Every change maps to the ticket
  2. The proof the ticket names is attached
  3. Nothing outside the ticket's files moves

Devin's summary

“Fixed date validation in the booking form. All tests pass. Ready to merge.”

Approve it, ask for proof, or send it back?

Send it back. The summary claims all tests pass, but no test output is attached, and the ticket demanded it shown. The diff also renames a helper in a file the ticket never named, so the boundary check fails too. One comment covers both misses: show the test output, and revert the rename outside this ticket. Devin fixes both, the checks rerun, and the next review is short.
  • Read the diff before the summary. The summary is a claim; the diff is the check.
  • Match every changed file to the ticket. A change outside it goes back as one comment.
  • A claim of passing tests needs the proof the ticket named attached.
  • Send back with one comment naming the failed check. Never merge to be polite.

Lesson 7, “Review Devin's pull requests in minutes, not evenings”, teaches the four checks on your own pull requests. Lesson 1 has you run your first real fix and check it in 15 minutes, so the check lands on work you already own.

Get my Devin plan About 2 minutes. Lesson 1 is a real fix you can use the same day.

The curriculum

The Devin course: 12 lessons, one real pipeline.

Osum’s Devin course is 12 hands-on lessons, about 4 hours in all. Lesson 1 is a 15-minute fix you check against its tests the same day. By lesson 12 you run a weekly pipeline: scoped tickets in, proven pull requests out, an automation on the watch. You need your own Devin account and a repo. You finish with a certificate you can add to LinkedIn.

Module 01

Hand Devin its first ticket

You hold one real fix on your own repo, scoped with a definition of done and returned as a pull request with proof. This is the first run of the ticket pipeline you finish in lesson 12.

  1. Get your first Devin fix back in 15 minutesHand Devin one small real bug from your own repo and check the pull request against its tests.
  2. Turn a one-line request into a scoped ticketPlan the work in Ask mode and write the definition of done before any code changes.
  3. Make Devin prove its fix before you reviewRequire test runs, screenshots or a recording in the ticket, so the pull request arrives with evidence.

Module 02

Give Devin a machine it can trust

You hold a repo that boots ready: an environment snapshot, rules in the repo, and a playbook that turns any ticket into the same scoped run.

  1. Set up the machine once so every session boots readyBuild the environment snapshot for your repo so sessions start with dependencies and tools installed.
  2. Write repo rules Devin follows in every sessionCommit an AGENTS.md with your build, test and style rules so you stop repeating them in every prompt.
  3. Save your ticket prompt as a playbook you reuseTurn the definition-of-done prompt into a playbook with a macro, so every ticket starts from the same proven run.

Module 03

Run many tickets without losing the thread

You hold the judgment layer: split work across parallel sessions, review what comes back in minutes, and let automations start tickets under a usage leash.

  1. Split a big ticket and run two Devins in parallelBreak one large request into independent scoped tickets and run their sessions side by side.
  2. Review Devin's pull requests in minutes, not eveningsUse Devin Review and a fixed checklist to judge each pull request before it merges.
  3. Put the watch on a schedule with a spending leashCreate one automation with a schedule trigger, an ACU limit and an invocation limit, so recurring tickets start themselves.

Module 04

Own the quota, the failures and the pipeline

You hold the whole pipeline: you know where the quota goes, you recover a stalled session from its worklog, and you run three tickets end to end in the capstone.

  1. See where the quota goes before it goesRead Session Insights to see what each session spent, and shape tickets that waste less.
  2. Recover a stalled session without redoing finished workDiagnose a stalled or refused session from its worklog and resume only the unfinished step.
  3. Run your full ticket pipeline, three tickets deepRun three fresh tickets through the whole pipeline: scoped, proven, reviewed, merged, with the watch running beside them.
Get my Devin plan About 2 minutes. Lesson 1 is a real fix you can use the same day.

Us vs. them

Why learn Devin here

The docs tell you what each setting does. YouTube shows you a demo. This course takes you from your first ticket to a pipeline that runs every week.

FeatureOsum courseOfficial docsYouTube walkthroughsFree guides
Step-by-step path, first ticket to weekly pipeline✓PartlyPartly✕
Hands-on exercise after every lesson✓✕✕✕
Scoping tickets with a definition of done✓✓PartlyPartly
Proof, review and the four checks, taught on your repo✓Partly✕✕
Snapshots, rules and playbooks that carry between sessions✓✓Partly✕
Practice on your own low-risk work, nothing merged blind✓✕✕✕
Certificate you can add to LinkedIn✓✕✕✕
Official, always-current settingsLinks to them✓PartlyPartly
CostMembershipFreeFreeFree

One membership

Learn Devin. Get every AI course with it.

The same membership covers Cursor for work inside your editor, Claude Code for fixes in your terminal and Codex for pull requests you’d merge. Each course has its own certificate.

Certificate

Finish it. Prove it.

Show a client, a manager or a hiring team that you can hand work to Devin and merge only what passes your checks. The certificate records a final check you passed, one question per lesson.

  • 12-question final check, one per lesson
  • Miss one? You see which lessons to review, then submit again
  • A public page you control, one click to add it to LinkedIn
  • Earn one for every course in the library

Questions

Before you start

How much does the Devin course cost?

One Osum membership covers this course, its certificate and every other course. It is a subscription. You see the price after your 2-minute plan, before you pay anything.

Do I need Devin to start?

You can start the lessons right away. For the hands-on exercises you need your own Devin account, and the Free plan's light quota is enough for lesson 1. Pro was $20 a month when we checked on 28 September 2026, and the exercises run on a repo you own.

How long does the Devin course take?

12 lessons, about 4 hours in all. Lesson 1 takes 15 minutes and ends with a real fix you can check the same day.

I’m not a professional developer. Can I do this?

You need to read a diff and run a test command. If you maintain any repo, even a personal one, every exercise works on it. The course never asks you to merge anything you have not checked.

I already write detailed prompts. Why would this work?

Prompts say what to do, not what finished looks like. Here you practice the Defined Done on a real ticket in every lesson, with a proof step and a review to check against. You finish with a weekly pipeline: assigned tickets in, proven pull requests out.

Will this stop Devin from ever going off the rails?

No course can promise a model that never guesses. You’ll learn to scope tickets so there is far less to guess, to demand proof inside the ticket, and to catch the confident wrong diff in minutes. A run that stalls becomes a recovery you can do, not a rerun.

Is this made by Cognition?

No. Osum is independent and not affiliated with Cognition. The certificate is an Osum certificate.

Keep watching agent runs. Or hand off the ticket and merge the work.

The Defined Done is four habits: scope first, define done, prove it, review before merge. You get a checked fix in lesson 1, a weekly pipeline by lesson 12, a certificate and every other course in the library. A few quick questions, then your plan.

Get my Devin plan About 2 minutes. Lesson 1 is a real fix you can use the same day.

Keep exploring

Related learning paths

Learn a useful skill. Put it to work.

Practical courses for AI tools and skills. Course and tool names are the trademarks of their respective owners; Osum is independent and not endorsed by them.