Skip to content

Considerations for FIT for AI #108

@k-doering-NOAA

Description

@k-doering-NOAA

Based on our brainstorming at the March meeting. The topic was: AI can now generate complete, functioning codebases. What changes do we need to make to FIT given this new reality?

Some pathways we may want to consider that arose out of brainstorming:

  • NOAA and/or FIT policy regarding generative AI (including use of agents) is not completely clear - can we help people know what they are allowed to use and how they are allowed to use it?
  • AI could have benefits for us, e.g., help with our code review checklist?
  • AI could benefit developers, e.g., help with tests and documentation
  • Maintenance could be an issue if AI generated code is included in the FIT - if AI wrote it and no one knows how to maintain it, the software quality won't be reliable.

This could be a discussion topic this summer, if the FIT meeting lead desires; or FIT committee could take action on this. Otherwise, it may be best to follow up on these ideas in the fall

Metadata

Metadata

Assignees

No one assigned

    Labels

    FY26ideaideas not captured in the strategic plan.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    Status
    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions