WEBVTT 00:03.790 --> 00:04.740 Hey there, everyone. 00:04.750 --> 00:07.570 My name is F.h. and I'll be your instructor for this course. 00:07.570 --> 00:12.640 And welcome to the very first video of this course for all those who have taken my other courses in 00:12.640 --> 00:13.120 the past. 00:13.120 --> 00:14.200 Welcome back again. 00:14.200 --> 00:18.820 For those who are taking this course for the very first time and are learning with me for the very first 00:18.820 --> 00:20.860 time, I would like to welcome you on board. 00:20.860 --> 00:24.820 And let me assure you, this is going to be a very fun ride, very enjoyable. 00:24.820 --> 00:29.170 You're going to understand every single bit piece of code that you are going to write, not just able 00:29.170 --> 00:31.750 to write along with me, but able to understand this. 00:31.990 --> 00:37.210 In order to move further, I would like to first clear up some of the basic ground rules that I am trying 00:37.210 --> 00:42.490 to put up here, some of the cautionary stuff and what the goal I'm trying to put with this course. 00:42.610 --> 00:47.230 Now, as soon as you mark any course as full stack development, that gets more attention because people 00:47.230 --> 00:48.850 want to learn this more. 00:48.850 --> 00:53.350 But there is something very important that I would like to share as a back end development. 00:53.530 --> 00:58.000 Now, back in development these days are considered as like it should be there as a full stack developer, 00:58.000 --> 01:01.540 but still you are going to see that in a lot of companies still back in. 01:01.540 --> 01:07.090 Developers are demanded as a separate skill and if you have this just a skill set, your chances become 01:07.090 --> 01:10.660 high because you are showing expertise in just the back end. 01:10.720 --> 01:16.060 Now, I often, often compare back in developers as CPU of the computer. 01:16.090 --> 01:21.730 You all know that everybody plays an important part in the organization like frontend developers, the 01:21.730 --> 01:23.950 UI, UX, even the operations. 01:23.950 --> 01:25.750 Everybody plays important role. 01:25.780 --> 01:29.800 Just like in the computer, it's important that everybody plays equal role. 01:30.010 --> 01:36.130 But back in developer, I personally call them as CPU just like the brain of the computer. 01:36.130 --> 01:40.540 Back in development, guys are considered as the brain of the entire application. 01:40.720 --> 01:43.720 A lot of time you are not going to see what your work is being done. 01:44.010 --> 01:48.910 It doesn't show up right up in the front end, but the moment it breaks, it shows up everywhere. 01:48.910 --> 01:53.980 For example, you decided one day that somebody is uploading images in your application. 01:53.980 --> 01:57.460 You decide that I don't want to host these images on a OS. 01:57.460 --> 02:00.750 Rather, I would like to host these applications on Cloud Ordinary. 02:01.240 --> 02:06.250 Nobody is going to notice that your front end guys have no idea that you have made these changes, and 02:06.250 --> 02:08.470 that is the beauty of the back end developer. 02:08.470 --> 02:13.450 What is being done at the back end doesn't really go up in the front end that much often. 02:13.450 --> 02:20.110 But also I would like to give you another operation here that in the world of the back end development, 02:20.110 --> 02:24.160 you are also going to decide that how your application is going to run through. 02:24.190 --> 02:27.100 You decide that how the application will function. 02:27.100 --> 02:30.220 You decide how your application flow is going to be there. 02:30.370 --> 02:35.920 Just taking another example, you decide that there is some very sensitive information tokens while 02:35.920 --> 02:36.490 login. 02:36.490 --> 02:41.080 You decide that I am expecting that somebody needs to put that token in the cookie. 02:41.080 --> 02:44.500 The entire front end is going to be run through that flow. 02:44.500 --> 02:46.420 You decide that cookie is not good. 02:46.420 --> 02:50.050 I expect that this token should be there in the header information. 02:50.050 --> 02:52.930 Now this information is going to come through the header. 02:52.930 --> 02:55.780 We don't really care that what is being used at the front end. 02:55.780 --> 02:59.920 It is react, it can be angular or it can be any other thing really doesn't matter. 02:59.920 --> 03:04.030 This is the flow that we are deciding and that's how everybody is going to follow through. 03:04.030 --> 03:08.740 So you play a really important role as a back end developer to decide the brain of the application, 03:08.740 --> 03:12.370 the functionality, the workflow, how the frontend guys are going to do it. 03:12.370 --> 03:14.560 So this is a really crucial job. 03:14.950 --> 03:19.270 Now with this, I would like to bring your attention to something very realistic. 03:19.450 --> 03:24.790 I, of course, can put this as a full stack developer course, but I rather thought that it should 03:24.790 --> 03:29.710 be better or it is going to be better to make you absolute pro in the back end developer. 03:29.830 --> 03:35.380 In order to become absolute pro, it is very important that you get introduced to the reality and the 03:35.380 --> 03:40.090 reality in the backend development world my friend is it's going to be a tough ride. 03:40.390 --> 03:46.240 I will make sure that I try to make it as easy and as smooth as possible, but let's just be honest 03:46.240 --> 03:47.140 with each other. 03:47.140 --> 03:48.640 This is going to be tough. 03:48.670 --> 03:52.090 Your bug hunting is going to be tough in some of the previous courses. 03:52.090 --> 03:57.520 During the back end segment, students sometimes took two weeks to resolve the bugs. 03:57.520 --> 04:00.430 Yes, I'm saying two weeks, not just two days. 04:00.430 --> 04:02.290 Three days, it's two weeks. 04:02.290 --> 04:03.520 And what was the issues? 04:03.520 --> 04:09.580 Sometimes just capitalization, sometimes just like order was written as orders or some comma. 04:09.580 --> 04:12.760 Yes, it is that much of difficult in the front end. 04:12.760 --> 04:15.760 Sometimes spotting the bugs are comparatively easy. 04:15.760 --> 04:20.020 I'm not saying it is too much easy, but sometimes it is comparatively little easy because you can see 04:20.050 --> 04:22.120 what's going on wrong in the back end. 04:22.120 --> 04:23.500 That is not that easy. 04:23.500 --> 04:28.510 You're writing some code in the file and that this new file is breaking the code that you have written 04:28.510 --> 04:29.590 two days ago. 04:29.590 --> 04:32.890 And sometimes it's difficult to trace those bugs. 04:32.890 --> 04:38.380 And despite we might have some of the test cases, test suites still we see that the Facebook and Amazon 04:38.380 --> 04:44.410 and application at that level also goes down simply because bugs are a little bit difficult to debug 04:44.410 --> 04:47.050 and to find and to hunt them in the back end. 04:47.050 --> 04:49.480 So make sure you keep that as in mind. 04:49.480 --> 04:51.970 But again, every bug is meant to be solved. 04:51.970 --> 04:54.400 It's going to take some time, but it will be solved. 04:54.400 --> 04:59.380 So all I want to say that, yeah, this is going to be there and I'll show you a lot of bug situation 04:59.380 --> 05:01.540 and I will solve that in front of you some. 05:01.540 --> 05:01.680 I'll. 05:01.750 --> 05:02.800 Intentionally introduced. 05:02.800 --> 05:05.800 Some will happen and I'll introduce you with all of them. 05:06.220 --> 05:11.440 So this is the hard reality of that and a couple of cautionary things now I would like to share with 05:11.440 --> 05:12.400 you on this one. 05:12.550 --> 05:18.250 First thing is, please, please just don't watch and write the code. 05:18.280 --> 05:24.160 I know a lot of people just start my videos and even put them on the mute and on another computer. 05:24.160 --> 05:25.660 They just write what I'm writing. 05:25.660 --> 05:27.830 They just even listen to music at that time. 05:27.850 --> 05:29.170 This is not good. 05:29.200 --> 05:34.660 No matter how hard I try, if you are going to just repeat what I'm writing here, then it's no sense. 05:34.660 --> 05:36.310 I'm giving you already the exercise file. 05:36.310 --> 05:38.860 Just go ahead and see those exercise file and write them. 05:38.890 --> 05:42.550 The reason why these are videos so that you can understand what I'm saying. 05:42.550 --> 05:46.090 My feelings that I'm trying to convey with the code and what can go wrong. 05:46.090 --> 05:49.690 These all theories are necessary, so please go ahead and follow them. 05:49.870 --> 05:55.390 I also see that sometimes people watch these videos in 1.5 X or one or two x even. 05:55.390 --> 05:56.290 That is okay. 05:56.290 --> 05:57.310 I'm not judging you. 05:57.340 --> 05:58.240 Go ahead and watch it. 05:58.240 --> 05:59.470 Even in the ten x. 05:59.470 --> 06:03.520 But sometimes there are crucial information where more emphasis should be given. 06:03.520 --> 06:07.090 When you watch them in the high speed, it just rushed through. 06:07.090 --> 06:10.510 It just goes like a flash and I don't want that to happen. 06:10.510 --> 06:12.790 So if possible, only if. 06:12.790 --> 06:14.260 Then please go ahead and watch it. 06:14.260 --> 06:18.550 And as the same speed as I'm trying to just convey the fact, just like a live class. 06:18.550 --> 06:23.830 But again, it's up to you if you can afford or you can simply understand me in 1.5 x, please go ahead 06:23.830 --> 06:26.350 and watch in that I have no problem in that. 06:27.220 --> 06:29.710 OC Another very, very important thing. 06:30.340 --> 06:33.970 Please understand what I'm trying to say before writing the code with me. 06:34.000 --> 06:38.680 Surely please go ahead and write code with me, but also understand what I'm trying to say. 06:38.710 --> 06:42.490 I cannot stop development that is not in my control. 06:42.520 --> 06:47.350 Every application, every repository, every package that I'm going to introduce, there is a continuous 06:47.350 --> 06:48.670 development in that field. 06:48.670 --> 06:53.710 And no matter how hard I try, the course is eventually going to be a little bit outdated. 06:53.710 --> 06:55.480 Not too much, but a little bit. 06:55.570 --> 07:00.190 And the only fact that how you can overcome with that, if you understand what I'm trying to say, I'm 07:00.190 --> 07:02.500 not going to magically bring the code and the code editor. 07:02.500 --> 07:07.210 I'll show you that from where this code is coming up, and I'll introduce you to these documentation. 07:07.210 --> 07:11.440 So you need to also understand that if something is changed in the documentation, you have to bring 07:11.440 --> 07:16.540 in the updated code and have to understand the flow that how this is going to happen mindlessly. 07:16.540 --> 07:19.360 Just writing along with me is not going to make you a better developer. 07:19.360 --> 07:20.740 So always remember that. 07:20.740 --> 07:25.690 So make sure you read a lot, you understand the things, and then write along with me. 07:25.690 --> 07:27.220 That is all I want to say. 07:27.370 --> 07:32.530 So with this I would like to say that this is the biggest thing that I want to say that hang in there. 07:32.530 --> 07:34.840 I will make sure that the journey is good. 07:34.840 --> 07:39.580 It's absolute crucial for you and you become an absolute pro back end developer. 07:39.580 --> 07:43.810 That is my intention with this course and I'll make that, I promise you with that. 07:43.930 --> 07:45.880 So go ahead and get started with that. 07:45.880 --> 07:47.500 Now coming up on to the goal. 07:47.500 --> 07:50.020 What is my biggest goal with this course now? 07:50.020 --> 07:55.300 It is a little bit kind of overambitious, but I'm pretty sure I will achieve that and I will turn you 07:55.300 --> 07:56.950 into a pro back and developer. 07:56.950 --> 08:02.020 And in order to just say that what makes you a pro back end developer is you will be able to design 08:02.020 --> 08:05.470 the back end that can be consumed at a lot of places. 08:05.470 --> 08:06.670 What do you mean by that? 08:06.670 --> 08:11.290 It simply means you are going to write a back end and we are going to write majorly focusing on the 08:11.290 --> 08:17.050 rest APIs that how you can build such a robust system that can be consumed on the web. 08:17.050 --> 08:20.170 Now by web, I, I don't know what's going to come in the front end. 08:20.170 --> 08:22.710 It can be react, it can be angular, it can be view. 08:22.720 --> 08:24.190 I have literally no idea. 08:24.190 --> 08:29.140 Anything can come up and we want to write a system which can just take care of all of these things. 08:29.140 --> 08:34.930 Not only that, we are also going to see that how we can modify the minimum amount of code or even can 08:34.930 --> 08:41.320 make the system so much robust and affordable as well as so much flexible, that it can also understand 08:41.320 --> 08:43.060 everything that's coming up from Mobile. 08:43.060 --> 08:44.560 I don't know what's in the mobile. 08:44.560 --> 08:49.390 It can be native Android, iOS, React, Native Flutter or something else that you're writing. 08:49.390 --> 08:52.150 It will be able to adapt in all of those. 08:52.150 --> 08:54.160 That's kind of a system we want, right? 08:54.160 --> 08:59.800 For example, just taking another one for the front end as a web, you decide that everything should 08:59.800 --> 09:03.880 come up in the cookies in the Android and iOS cookies can be done. 09:03.880 --> 09:09.010 But in the case of React Native, it's not easy to put up and expect information from cookies. 09:09.010 --> 09:12.190 So I'll show you all these information and a whole lot of journey. 09:12.190 --> 09:17.410 It's going to be a long one, but I expect a lot of patience from your side and rest. 09:17.410 --> 09:19.330 I'll take care of all of that. 09:19.330 --> 09:24.190 So let's go ahead and start the journey of becoming a pro backend developer.