Hey there, everyone.
My name is F.h. and I'll be your instructor for this course.
And welcome to the very first video of this course for all those who have taken my other courses in
the past.
Welcome back again.
For those who are taking this course for the very first time and are learning with me for the very first
time, I would like to welcome you on board.
And let me assure you, this is going to be a very fun ride, very enjoyable.
You're going to understand every single bit piece of code that you are going to write, not just able
to write along with me, but able to understand this.
In order to move further, I would like to first clear up some of the basic ground rules that I am trying
to put up here, some of the cautionary stuff and what the goal I'm trying to put with this course.
Now, as soon as you mark any course as full stack development, that gets more attention because people
want to learn this more.
But there is something very important that I would like to share as a back end development.
Now, back in development these days are considered as like it should be there as a full stack developer,
but still you are going to see that in a lot of companies still back in.
Developers are demanded as a separate skill and if you have this just a skill set, your chances become
high because you are showing expertise in just the back end.
Now, I often, often compare back in developers as CPU of the computer.
You all know that everybody plays an important part in the organization like frontend developers, the
UI, UX, even the operations.
Everybody plays important role.
Just like in the computer, it's important that everybody plays equal role.
But back in developer, I personally call them as CPU just like the brain of the computer.
Back in development, guys are considered as the brain of the entire application.
A lot of time you are not going to see what your work is being done.
It doesn't show up right up in the front end, but the moment it breaks, it shows up everywhere.
For example, you decided one day that somebody is uploading images in your application.
You decide that I don't want to host these images on a OS.
Rather, I would like to host these applications on Cloud Ordinary.
Nobody is going to notice that your front end guys have no idea that you have made these changes, and
that is the beauty of the back end developer.
What is being done at the back end doesn't really go up in the front end that much often.
But also I would like to give you another operation here that in the world of the back end development,
you are also going to decide that how your application is going to run through.
You decide that how the application will function.
You decide how your application flow is going to be there.
Just taking another example, you decide that there is some very sensitive information tokens while
login.
You decide that I am expecting that somebody needs to put that token in the cookie.
The entire front end is going to be run through that flow.
You decide that cookie is not good.
I expect that this token should be there in the header information.
Now this information is going to come through the header.
We don't really care that what is being used at the front end.
It is react, it can be angular or it can be any other thing really doesn't matter.
This is the flow that we are deciding and that's how everybody is going to follow through.
So you play a really important role as a back end developer to decide the brain of the application,
the functionality, the workflow, how the frontend guys are going to do it.
So this is a really crucial job.
Now with this, I would like to bring your attention to something very realistic.
I, of course, can put this as a full stack developer course, but I rather thought that it should
be better or it is going to be better to make you absolute pro in the back end developer.
In order to become absolute pro, it is very important that you get introduced to the reality and the
reality in the backend development world my friend is it's going to be a tough ride.
I will make sure that I try to make it as easy and as smooth as possible, but let's just be honest
with each other.
This is going to be tough.
Your bug hunting is going to be tough in some of the previous courses.
During the back end segment, students sometimes took two weeks to resolve the bugs.
Yes, I'm saying two weeks, not just two days.
Three days, it's two weeks.
And what was the issues?
Sometimes just capitalization, sometimes just like order was written as orders or some comma.
Yes, it is that much of difficult in the front end.
Sometimes spotting the bugs are comparatively easy.
I'm not saying it is too much easy, but sometimes it is comparatively little easy because you can see
what's going on wrong in the back end.
That is not that easy.
You're writing some code in the file and that this new file is breaking the code that you have written
two days ago.
And sometimes it's difficult to trace those bugs.
And despite we might have some of the test cases, test suites still we see that the Facebook and Amazon
and application at that level also goes down simply because bugs are a little bit difficult to debug
and to find and to hunt them in the back end.
So make sure you keep that as in mind.
But again, every bug is meant to be solved.
It's going to take some time, but it will be solved.
So all I want to say that, yeah, this is going to be there and I'll show you a lot of bug situation
and I will solve that in front of you some.
I'll.
Intentionally introduced.
Some will happen and I'll introduce you with all of them.
So this is the hard reality of that and a couple of cautionary things now I would like to share with
you on this one.
First thing is, please, please just don't watch and write the code.
I know a lot of people just start my videos and even put them on the mute and on another computer.
They just write what I'm writing.
They just even listen to music at that time.
This is not good.
No matter how hard I try, if you are going to just repeat what I'm writing here, then it's no sense.
I'm giving you already the exercise file.
Just go ahead and see those exercise file and write them.
The reason why these are videos so that you can understand what I'm saying.
My feelings that I'm trying to convey with the code and what can go wrong.
These all theories are necessary, so please go ahead and follow them.
I also see that sometimes people watch these videos in 1.5 X or one or two x even.
That is okay.
I'm not judging you.
Go ahead and watch it.
Even in the ten x.
But sometimes there are crucial information where more emphasis should be given.
When you watch them in the high speed, it just rushed through.
It just goes like a flash and I don't want that to happen.
So if possible, only if.
Then please go ahead and watch it.
And as the same speed as I'm trying to just convey the fact, just like a live class.
But again, it's up to you if you can afford or you can simply understand me in 1.5 x, please go ahead
and watch in that I have no problem in that.
OC Another very, very important thing.
Please understand what I'm trying to say before writing the code with me.
Surely please go ahead and write code with me, but also understand what I'm trying to say.
I cannot stop development that is not in my control.
Every application, every repository, every package that I'm going to introduce, there is a continuous
development in that field.
And no matter how hard I try, the course is eventually going to be a little bit outdated.
Not too much, but a little bit.
And the only fact that how you can overcome with that, if you understand what I'm trying to say, I'm
not going to magically bring the code and the code editor.
I'll show you that from where this code is coming up, and I'll introduce you to these documentation.
So you need to also understand that if something is changed in the documentation, you have to bring
in the updated code and have to understand the flow that how this is going to happen mindlessly.
Just writing along with me is not going to make you a better developer.
So always remember that.
So make sure you read a lot, you understand the things, and then write along with me.
That is all I want to say.
So with this I would like to say that this is the biggest thing that I want to say that hang in there.
I will make sure that the journey is good.
It's absolute crucial for you and you become an absolute pro back end developer.
That is my intention with this course and I'll make that, I promise you with that.
So go ahead and get started with that.
Now coming up on to the goal.
What is my biggest goal with this course now?
It is a little bit kind of overambitious, but I'm pretty sure I will achieve that and I will turn you
into a pro back and developer.
And in order to just say that what makes you a pro back end developer is you will be able to design
the back end that can be consumed at a lot of places.
What do you mean by that?
It simply means you are going to write a back end and we are going to write majorly focusing on the
rest APIs that how you can build such a robust system that can be consumed on the web.
Now by web, I, I don't know what's going to come in the front end.
It can be react, it can be angular, it can be view.
I have literally no idea.
Anything can come up and we want to write a system which can just take care of all of these things.
Not only that, we are also going to see that how we can modify the minimum amount of code or even can
make the system so much robust and affordable as well as so much flexible, that it can also understand
everything that's coming up from Mobile.
I don't know what's in the mobile.
It can be native Android, iOS, React, Native Flutter or something else that you're writing.
It will be able to adapt in all of those.
That's kind of a system we want, right?
For example, just taking another one for the front end as a web, you decide that everything should
come up in the cookies in the Android and iOS cookies can be done.
But in the case of React Native, it's not easy to put up and expect information from cookies.
So I'll show you all these information and a whole lot of journey.
It's going to be a long one, but I expect a lot of patience from your side and rest.
I'll take care of all of that.
So let's go ahead and start the journey of becoming a pro backend developer.