WEBVTT 00:00.080 --> 00:04.730 Okay, this is just a quick lesson to let you know what you can do if you do get stuck at any point 00:04.730 --> 00:05.570 during this course. 00:05.570 --> 00:11.690 This is a software development training course, and there's an expectation you're going to follow along. 00:11.690 --> 00:17.060 And it would be highly unusual if you managed to get from start to finish of this training course without 00:17.060 --> 00:19.070 making a mistake somewhere along the way. 00:19.100 --> 00:20.600 First of all, please don't panic. 00:20.600 --> 00:26.510 It's perfectly normal and expected to run into a problem whilst building an application. 00:26.540 --> 00:28.040 It's all part of the fun really. 00:28.040 --> 00:33.350 As software developers where we write some code that causes us some problem and then we have to go and 00:33.350 --> 00:34.220 fix that problem. 00:34.220 --> 00:38.480 And yes, it can be frustrating, but it is part of the fun. 00:38.480 --> 00:41.030 So what do you do if you do run into a problem? 00:41.030 --> 00:46.010 Well, the first step is always to gather information, because if you're looking at a blank browser 00:46.010 --> 00:52.550 window and you're not seeing any error information, then you don't really know how to solve it because 00:52.550 --> 00:54.170 you don't know what the problem is. 00:54.170 --> 00:59.270 So there's always tools that we can use to help us when it comes to gathering information. 00:59.270 --> 01:05.740 And if you do run into a problem, then please spend as much time as necessary to gather more information 01:05.740 --> 01:08.290 about the issue, we're going to take a look at tools. 01:08.290 --> 01:11.320 As we build the application, we're going to take a look at things like the. 01:11.500 --> 01:15.700 Net terminal where we run our application, things like Chrome developer tools. 01:15.820 --> 01:20.710 The debugger will take a look at fairly early on during the development of the training course, and 01:20.710 --> 01:26.920 use whatever tools you have in your toolbox to get more information about the problem that you have. 01:26.920 --> 01:31.720 Once you have an error to work with and you know what the error is, you may not know how to fix it 01:31.720 --> 01:38.140 yet, but googling the error is typically the next step because that becomes part of the research phase 01:38.140 --> 01:39.610 of solving any problem. 01:39.610 --> 01:45.340 We're using some of the most popular technologies to develop and write the code for our application. 01:45.340 --> 01:50.530 So the chances of you being the first to encounter any error that you can come across in this course 01:50.530 --> 01:52.690 is highly, highly unlikely. 01:52.690 --> 01:57.070 Somebody else will have not only come across that error, they'd have asked a question about how to 01:57.100 --> 02:02.020 solve that error, and another developer somewhere will have given them the answer of how to solve that 02:02.020 --> 02:02.710 problem. 02:02.710 --> 02:06.670 So most of the time, resolving errors is pretty simple. 02:06.670 --> 02:08.680 You just get the information about the error. 02:08.710 --> 02:10.780 You copy the error into your clipboard. 02:10.780 --> 02:14.590 Then you read up about what caused the error and what you can do to fix it. 02:14.620 --> 02:17.860 If that doesn't help, you have the source code at your fingertips. 02:17.860 --> 02:22.840 For the application that we're writing on this training course, we've taken a look at where you can 02:22.840 --> 02:25.480 get that from in the previous lesson. 02:25.480 --> 02:28.870 So please compare your code with code that you know works. 02:28.870 --> 02:32.200 And you know that code works because you've seen it working in the demos. 02:32.200 --> 02:39.220 So if you're experiencing something different to myself when I was demonstrating this functionality, 02:39.220 --> 02:44.500 then you've got the option to compare your code with the demo code to see where you might have done 02:44.500 --> 02:46.690 something different to what I did. 02:46.720 --> 02:53.680 Also, there's the course Q&A, which you can use to ask questions and get answers should none of those 02:53.680 --> 02:56.170 three steps above solve the problem. 02:56.530 --> 03:01.210 But we do like to resolve the problems that we create because it is often the best way to learn. 03:01.210 --> 03:02.650 Yes, it can be frustrating. 03:02.650 --> 03:09.250 I appreciate that, and the least frustrating and easiest way to get past a problem is to ask a more 03:09.250 --> 03:12.040 senior developer and say, hey, I've got this issue. 03:12.070 --> 03:13.120 How do I solve it? 03:13.120 --> 03:16.170 Let them come along, do their magic and the problem is resolved. 03:16.170 --> 03:21.000 But you're no better off than you were before, because you don't know or don't have that knowledge 03:21.000 --> 03:26.070 about why that problem occurred, why you did what you did, and what the reason is that that problem 03:26.070 --> 03:27.240 is now resolved. 03:27.270 --> 03:32.880 If you go ahead and fix that problem yourself by doing the research and spending the time learning why 03:32.880 --> 03:37.740 the problem is occurring, then you're going to be in a much better position when it comes to similar 03:37.740 --> 03:42.390 problems that you encounter further down the line than you were before. 03:42.420 --> 03:44.370 Also, please check the basics. 03:44.370 --> 03:51.420 Sometimes a compiler can just get stuck or your code editor is just being a bit weird that day. 03:51.420 --> 03:56.790 So when it comes to checking the basics, I'm really talking about just restarting stuff. 03:56.790 --> 04:02.760 If the compiler has got stuck, then one way to give it a kick is simply to restart something the API 04:02.790 --> 04:09.900 server or the client's developer server, or even restart Visual Studio Code if you're using that. 04:09.900 --> 04:18.270 Sometimes it can be a bit weird, and giving it a restart is often the solution to a problem, so please 04:18.270 --> 04:22.850 don't presume you actually have a problem until you know for sure that the problem persists. 04:22.880 --> 04:28.640 If you've given your compiler a kick or your code editor a kick, do come and use the Q&A. 04:28.670 --> 04:35.420 If you do run into an issue, but please do provide as much information about the problem as you can. 04:35.450 --> 04:41.540 About 50% of the time, most of my responses to you questions on there are simply asking the students 04:41.540 --> 04:42.440 for more information. 04:42.440 --> 04:47.480 Because just like you as a software developer, you need information to solve a problem. 04:47.480 --> 04:49.490 I need information to solve a problem. 04:49.490 --> 04:53.900 So please make sure you provide as much information about the error as possible. 04:53.900 --> 04:56.480 And please let me know what you've already tried. 04:56.480 --> 05:02.900 Because if it's not clear that you've checked the basics and restarted that API server or restarted 05:02.900 --> 05:07.640 VSCode, then I may suggest that as the first option. 05:07.640 --> 05:10.670 And if you've already tried that, then please do let me know. 05:10.670 --> 05:16.490 If you do have a Non-course related question, then please use a facility such as Stack Overflow, which 05:16.490 --> 05:22.250 is an excellent resource to help you resolve Non-course related questions. 05:22.280 --> 05:28.500 I'm just a single developer that doesn't have an unlimited amount of time, and I do not have the capacity 05:28.500 --> 05:35.340 to answer questions not related to this trading course, but Stack Overflow is a resource that effectively 05:35.340 --> 05:42.180 connects you to the entire developer community, and literally thousands of developers that might be 05:42.210 --> 05:46.950 able to assist you with code that's not related to this particular training course. 05:46.950 --> 05:54.570 So please do make an account on there and ask any non-course related questions on there and the Q&A 05:54.570 --> 05:55.440 response times. 05:55.440 --> 06:02.130 I usually can get back to students in 24 to 48 hours, and I'm normally on there once a day, but I 06:02.130 --> 06:08.970 do take 1 or 2 days off per week, so you can usually expect a response in 24 to 48 hours. 06:08.970 --> 06:10.860 So please do make the questions count. 06:10.890 --> 06:13.680 Provide as much information as you can about the problem. 06:13.680 --> 06:20.640 That would allow me to give you an answer to the issue, rather than asking you a follow up question, 06:20.640 --> 06:22.980 because I need to get more information from you. 06:23.010 --> 06:25.650 So now that's the admin out of the way. 06:25.680 --> 06:29.040 Let's next take a look at starting to build the application.