Leidos uses Sourcegraph Cody to accelerate software development and cut senior developer mentoring time
Leidos needed an AI coding assistant that met the highest security standards for government and defense clients, avoided LLM lock-in as the field rapidly evolved, and could retrieve context from entire code repositories rather than just the currently open editor tab.
Many evaluated alternative coding assistants were eliminated for insufficient security and privacy controls, and their context retrieval was limited to only the open editor tab rather than full repositories.
Cody accelerated Oracle-to-PostgreSQL migrations to 80% to 90% complete within minutes, and senior developers reduced time guiding junior developers from about eight hours of the week to two.
Engineers also save time writing documentation, generate boilerplate in seconds, and debug significantly faster.
Show all 5 reported metrics
Frequently asked questions
What did this team achieve with this AI workflow?
Cody accelerated Oracle-to-PostgreSQL migrations to 80% to 90% complete within minutes, and senior developers reduced time guiding junior developers from about eight hours of the week to two.
What tools did this team use?
Cody, Sourcegraph.
What results were reported?
Oracle-to-PostgreSQL migration completion: 80% to 90%; Senior developer mentoring time per week: eight hours of the week... cut this down to two; Documentation time: saving time writing documentation for their code; Boilerplate generation time: generating boilerplate in seconds (source-reported, not independently verified).
What failed first in this deployment?
Many evaluated alternative coding assistants were eliminated for insufficient security and privacy controls, and their context retrieval was limited to only the open editor tab rather than full repositories.
How is this quality assurance AI workflow structured?
Engineer invokes Cody → Context retrieval from repos → Code and documentation generation → Legacy migration acceleration → Mentoring time reduction.