Learning path
Developer AI fluency - from autocomplete to design partner
Software engineers, data scientists, and SREs who already use Copilot or Cursor and want to stop using it as autocomplete.
5 steps54 min total0/5 steps live
By the end of this path
You will (1) prompt across files, (2) use reasoning models for design and review, (3) wire AI into your editor and notebook surface deliberately, and (4) know which patterns to avoid.
Your progress
Loading your progress…
Walk the path
- 1L3 · Daily user10 minComing soonAI in your editor and notebooks - the developer surface
Why: Editor surface, not just chat - where most dev time is lost or won.
- 2L3 · Daily user10 minComing soonPrompting with images and files
Why: Screenshots and stack-traces as input, not just code.
- 3L4 · Crafted user12 minComing soonPrompting patterns for coding work
Why: Patterns specifically for code, not generic prompts.
- 4L4 · Crafted user12 minComing soonChain-of-thought reasoning patterns
Why: Reasoning patterns for non-trivial refactors and reviews.
- 5L4 · Crafted user10 minComing soonReasoning models - when to use o-series and thinking modes
Why: When to pay for o-series / thinking modes on dev work.
Next path
Prompt engineering - foundations that hold up across vendors
Continue