Bioinformatics Software Engineer
CCR Collaborative Bioinformatics Resource
Oct 14, 2026
Important
This presentation was created before the directive to use the term “Super Intelligence (SI)” in place of “Artificial Intelligence (AI)”.
Always refer to the official NIH AI Hub for the most up-to-date policy information.
Take-home message
By the end, you should feel empowered with the knowledge to use agentic LLMs proficiently for bioinformatics, without compromising the quality of your science.
Audience roles: bioinformatician, computational biologist, data analyst, research software engineer – anyone who writes code to analyze biological data.
We can write code faster than ever before
generate new code, troubleshoot bugs, search the web, write tests, execute code
We can write bad code faster, too
unreproducible work, incorrect methods, bugs, inefficiencies, unreadable code, lack of transparency, security vulnerabilities, malware, destructive agent actions
Content retrieved September 2026 from the NIH Responsible AI site. Please refer to the official site for the latest guidance.
Stop and Reconsider If:
1. Confirm the Use is Appropriate
2. Define the Human-AI Roles
3. Project Data and Outputs
4. Verify Outputs
5. Be Transparent About AI Use
Content retrieved September 2026 from the NIH AI Use Checklist. Please refer to the official site for the latest guidance.
A better way: humans judiciously use agents when appropriate to support human-driven tasks.
Image credit: Samarth Mathur
Design
Develop
Execute
Treat agents like just another tool in your toolbox.
Follow reproducible practices
Review, test, and validate all code
Document everything
Yourself ➡️ Future you ➡️ Your collaborators ➡️ Peers in your field
You are your own most important collaborator
Credit to Samarth Mathur for these project examples.
Credit to Samarth Mathur for these project examples.
Credit to Samarth Mathur for these project examples.
From the NIH Responsible AI policy:
Do not rely on the technology to be a software developer by proxy:
- All well-written code must adhere to security design and ethical principles.
- All code output needs to be reviewed for completeness, quality, efficiency, and, most of all, security.
- Leverage manual and automated validation tools and testing technologies to help ensure these factors.
- If you cannot identify or understand what a piece of AI generated code does, you should not use it.
AI outputs may be incomplete, inaccurate, biased, or fabricated.
Content retrieved September 2026 from the NIH Responsible AI site. Please refer to the official site for the latest guidance.
Please refer to the official NIH Responsible AI site for the latest guidance.
If you cannot identify or understand what a piece of AI generated code does, you should not use it.
Content retrieved September 2026 from the NIH Responsible AI site. Please refer to the official site for the latest guidance.
Challenge yourself!
If you do not understand a piece of AI-generated code, dig into the documentation and tutorials to learn how it works.
? and help(). Python: use help()Write tests to make sure the code behaves as expected.
testthat. Python: pytest, unittestsrc/mypackage/main.py
Run tests before accepting code.
Use GitHub actions to automate.
Use linters and code quality checks.
air. Python: ruff.Use pre-commit to run checks automatically on every change.
Inline comments, function docstrings, vignettes, tutorials, getting started guide
Rscript
from the very beginning of the project:
Create a document outlining how you will and will not use LLMs and agents.
Disclose use of LLMs and agents in commit messages, issue comments, and pull requests.
| Practice | Risks minimized | |
|---|---|---|
| Follow reproducible practices | unreproducible work, destructive agent actions | |
| Review, test, and validate all code | incorrect methods, bugs, inefficiencies, malware | |
| Document everything | unreadable code, unusable code, lack of transparency |
Check off every item in this checklist before you trust LLM-generated code
1. Understand
2. Test
3. Sanity check
4. Make it reproducible
5. Own it
Checklist credit: Vishal Koparde
LLMs produce outputs that look like a plausible response to a prompt 🦜
Agentic tools can accelerate bioinformatics 🚀