Lecturer: So, who is this course for?
First, architects.
Defining API is one of the core concepts
of the system architecture
and usually the architect is the one
who should design and define the API.
So, naturally architects will benefit the most
out of this course.
But actually anyone with some development background,
like developers, team leaders, dev managers,
even QA can benefit from this course.
The API of the software you are working on
is one of the most crucial points of the software
and it will probably make or break the software.
So anyone who deals with a software development,
even if not as a direct developer,
will benefit from this course.
Now, if you are a developer, then you preferably
have some kind of experience, of development experience,
and preferably some back-end development experience.
Naturally, front-end development is little less related
to REST API design, even though the front-end
is actually the one who is using the API,
so it's also important,
but in order to develop the REST API
you should have some kind
of back-end development experience.
Now, I want to emphasize again
what we said in the previous session.
This course has no coding requirement.
You will not have to code, not even a single line of code.
What we'll use is some kind of mocking techniques,
and specifically we will use Postman and Beeceptor.
Again, you don't need to know those tools right now.
We will talk about them later in this course,
and you will know everything there is to know about them.