Module 3 · Files, tools and your own data Lesson 10 of 15
Editor integrations and your own tooling and your first script
The editor is a product rather than an endpoint, and the pattern worth copying from it — give a model the project, take back a diff — is what you build on any provider API. You do not need this to finish the course, and you do not need it for a fresher job either — but an afternoon here is what turns "I have used Cursor" into "I have built with it", which is a different sentence in an interview.
The concept
The editor is a product rather than an endpoint, and the pattern worth copying from it — give a model the project, take back a diff — is what you build on any provider API. The idea is simple: the same model you have been chatting with also answers a web request, so you can put it inside a script, a spreadsheet or a page. A key identifies you; a request sends the text; a response comes back as data.
The reason to try it once, even if you never build anything: it makes the chat version less mysterious. You see that the whole conversation is text in and text out, that your instructions are literally lines of a request, and that "the model" is one parameter among several.
A first call looks like this:
# The habit this course is really about, in one line:
#
# describe the change -> read the diff -> run the tests -> commit
#
# With AI in the middle it becomes:
#
# describe the change -> the assistant proposes a diff
# -> YOU read the diff
# -> you run the tests
# -> you commit with a message saying why
#
# The two steps that stayed yours are the two that matter.Common mistakes
The mistake is letting the assistant commit. Read the diff and write the message yourself — the commit history is the record of your judgement, and it is what a reviewer reads first.
Worked example
A script that takes a code file and returns a reviewed version with comments is a small but honest demonstration that you understand the pattern under the editor.
Your practice task
Get a key, run one request that works, and change one word in it to see the answer change. That is the whole of the first afternoon.
Do this before moving on. Reading a solution teaches the shape of it; typing it teaches you.
Key takeaway
The editor is a product rather than an endpoint, and the pattern worth copying from it — give a model the project, take back a diff — is what you build on any provider API.
Keep your place in this course
A free account saves which lessons you have finished and unlocks the certificate. The lesson itself stays free to read.
Create free account or sign inCourse complete
You finished every lesson.
Your certificate is ready, and the projects you built are the proof to attach to an application.
Almost there
15 lessons left of 15
Finish every lesson to unlock the certificate. Each one ends in a practice task — do them and the final project brief writes itself.