Build a page in small Devin sessions

An engineer used Devin to ship a deals page in stages, with each chunk handled in a separate session and PR.

Done with Devinยท Intermediate

What they did
She linked both the backend and frontend repositories to Devin through GitHub, then let it create its own workspace. She supplied the Deal schema, a database diagram, and PR numbers for related work that had not been merged yet. Devin broke the job into separate sessions, started with the first slice, and then tried lint and TypeScript fixes before opening a PR.
How it went
The first PR landed in under 10 minutes, but CI did not pass. Later PRs were mostly acceptable, though they included extra edits, and Devin incorrectly claimed Joi was not used anywhere else. The last session, which was meant to get the app running locally, ran into usage limits.
Tips
Treat each session as isolated, since Devin does not carry context across them and the split cannot run in parallel. Keep an eye on scope creep, verify library usage yourself, and watch usage caps; she used all 150 ACUs in less than a week, and the docs warn that performance drops after 10 ACUs per session.

Try it yourself with Devin

In [repo name], help me build [feature/page] in small, separate steps. First do [step 1], then stop and show me the plan for [step 2], and only continue after I approve it. For each step, keep the changes tightly scoped, open a PR when that step is done, and explain any CI or TypeScript issues you find. Before making any irreversible change such as [sending/deleting/submitting/paying], pause and ask for my approval. If you mention a library or dependency, check the code or docs and clearly separate what you confirmed from what you are inferring.

Fill in the [brackets]. Agents can make mistakes, so review anything before it is sent, paid or deleted.

Read the original on qubika.com โ†—

Get 3 agent uses like this every morning

With the day's top AI news. Free, and one click to unsubscribe.