Assistants in the professional workflow
On This Lesson 4 topics
The content for this lesson is written and waiting for review. The outline below shows what it covers. It will be published once it is approved.
In this lesson
know what an AI assistant is good for, and when to leave it off.
Planned topics
- An assistant suggests code (completion), answers questions (chat), and proposes edits (refactoring).
- Good uses: boilerplate, explaining unfamiliar code, first drafts of tests, small refactorings.
- Weak uses: new design decisions, security-sensitive code, anything you cannot check.
- It can be wrong and sound sure. You are responsible for every line you commit.
- Do not use it to skip learning: if you cannot explain the code, do not commit it.
Draft outline details
Demonstration
a table: task / use the assistant? / why.
Check your understanding
Who is responsible for AI-written code you commit?
Show answer
You are.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.