Source evidence
Every finding begins with a source you can open.
Review release notes, changelogs, deprecation notices, and version changes with the dates and context needed to judge the change yourself.
Course maintenance for software educators
What changed. Which lesson it affects. What to update.
TeachCurrent tracks the tools and frameworks you teach, shows the source evidence behind every change, points to the lessons it affects, and drafts the update for your review.
Course review · sample data
3 findings
Source evidence
ConfirmedReact release notes
New guidance changes a previously taught pattern.
Affected lesson
Needs reviewModule 4 · Lesson 12
Two code samples and one slide need review.
Suggested update
Action requiredRewrite sample + callout
Draft replacement prepared for approval.
Illustrative example — not a live course review
The problem
Your course can age even when the teaching is still sound.
Software changes between cohorts. APIs are deprecated, recommended patterns shift, and a lesson that was accurate when published can quietly become misleading. Finding every affected reference by hand is slow and easy to postpone.
Upstream change
A tool, framework, or source publishes something new.
Course impact
The change may touch lessons, slides, code, or examples.
Instructor decision
Someone still needs to verify and approve the right edit.
The product
Course maintenance, not content generation.
TeachCurrent is built to help educators evaluate changes against material they already teach—without surrendering the final editorial decision.
Affected lessons
Changes mapped to your actual course material.
See the modules, lessons, code samples, and slides where an upstream change may require your attention.
Suggested updates
Drafts remain under instructor control.
Review a proposed update, adjust it, approve it, or dismiss it. TeachCurrent does not publish changes on your behalf.
Review trail
Know what is confirmed and what still needs review.
Explicit finding states keep incomplete analysis visible instead of presenting it as finished work.
How it works
From upstream change to approved edit.
A transparent workflow keeps the evidence, the affected material, and the instructor’s decision connected.
- 01
Connect your course
Point TeachCurrent at your existing modules, lessons, and code samples, then identify the tools and versions you teach.
- 02
Watch the sources
TeachCurrent monitors releases and deprecations for those dependencies and records the evidence behind each change.
- 03
Review and apply
See the affected lessons and a suggested edit for each finding. Approve, adjust, or dismiss every draft yourself.
Evidence standard
We show our working.
A maintenance tool is only useful when you can check it. Findings without a verifiable source are labeled as unreviewed and never counted as complete.
- Each change links to a dated primary source.
- Lesson matches identify the exact file, slide, or sample.
- Suggested edits remain drafts until an instructor approves them.
- Unverified findings are clearly labeled, never hidden.
Now open
Connect your first course and start reviewing what changed.
Create an account on TeachCurrent, or contact USA Research Group to learn more about the business.