Software & DevOpsDone with Devin 2026-10-12
Build a deals page step by step with Devin
An engineer had Devin implement a deals page in steps; it opened a PR in under 10 minutes, but CI failed, it added unnecessary changes and gave a false answer about a library.
- What They Did
- The engineer connected the backend and frontend repos to Devin through its GitHub integration and had it set up its own environment. She gave it the Deal schema and a DB diagram, plus PR numbers for related unmerged work. Devin split the task into separate sessions, opened a PR for the first piece, and retried CI lint and TypeScript fixes. Each later part got its own session, with PRs based on the earlier ones.
- How It Went
- The first PR opened in under 10 minutes but failed CI. Later PRs were acceptable but carried extra changes, and Devin wrongly said Joi wasn't used elsewhere. The final session, getting the project running locally, hit usage limits.
- Worth Knowing
- Separate sessions don't share context, so the split can't be run in parallel. She used all 150 ACUs in under a week, and the docs say performance degrades past 10 ACUs per session.
Try it yourself with Devin
In [repo name], implement a [page or feature, e.g. deals page] in small steps: [step 1], then [step 2], then [step 3]. Open a PR after the steps, make sure CI passes, and don't add changes outside the scope. If you're unsure how a library works, check its docs and tell me what you verified versus what you assumed.