Okay, this is just a quick lesson to let you know what you can do if you do get stuck at any point
during this course.
This is a software development training course, and there's an expectation you're going to follow along.
And it would be highly unusual if you managed to get from start to finish of this training course without
making a mistake somewhere along the way.
First of all, please don't panic.
It's perfectly normal and expected to run into a problem whilst building an application.
It's all part of the fun really.
As software developers where we write some code that causes us some problem and then we have to go and
fix that problem.
And yes, it can be frustrating, but it is part of the fun.
So what do you do if you do run into a problem?
Well, the first step is always to gather information, because if you're looking at a blank browser
window and you're not seeing any error information, then you don't really know how to solve it because
you don't know what the problem is.
So there's always tools that we can use to help us when it comes to gathering information.
And if you do run into a problem, then please spend as much time as necessary to gather more information
about the issue, we're going to take a look at tools.
As we build the application, we're going to take a look at things like the.
Net terminal where we run our application, things like Chrome developer tools.
The debugger will take a look at fairly early on during the development of the training course, and
use whatever tools you have in your toolbox to get more information about the problem that you have.
Once you have an error to work with and you know what the error is, you may not know how to fix it
yet, but googling the error is typically the next step because that becomes part of the research phase
of solving any problem.
We're using some of the most popular technologies to develop and write the code for our application.
So the chances of you being the first to encounter any error that you can come across in this course
is highly, highly unlikely.
Somebody else will have not only come across that error, they'd have asked a question about how to
solve that error, and another developer somewhere will have given them the answer of how to solve that
problem.
So most of the time, resolving errors is pretty simple.
You just get the information about the error.
You copy the error into your clipboard.
Then you read up about what caused the error and what you can do to fix it.
If that doesn't help, you have the source code at your fingertips.
For the application that we're writing on this training course, we've taken a look at where you can
get that from in the previous lesson.
So please compare your code with code that you know works.
And you know that code works because you've seen it working in the demos.
So if you're experiencing something different to myself when I was demonstrating this functionality,
then you've got the option to compare your code with the demo code to see where you might have done
something different to what I did.
Also, there's the course Q&A, which you can use to ask questions and get answers should none of those
three steps above solve the problem.
But we do like to resolve the problems that we create because it is often the best way to learn.
Yes, it can be frustrating.
I appreciate that, and the least frustrating and easiest way to get past a problem is to ask a more
senior developer and say, hey, I've got this issue.
How do I solve it?
Let them come along, do their magic and the problem is resolved.
But you're no better off than you were before, because you don't know or don't have that knowledge
about why that problem occurred, why you did what you did, and what the reason is that that problem
is now resolved.
If you go ahead and fix that problem yourself by doing the research and spending the time learning why
the problem is occurring, then you're going to be in a much better position when it comes to similar
problems that you encounter further down the line than you were before.
Also, please check the basics.
Sometimes a compiler can just get stuck or your code editor is just being a bit weird that day.
So when it comes to checking the basics, I'm really talking about just restarting stuff.
If the compiler has got stuck, then one way to give it a kick is simply to restart something the API
server or the client's developer server, or even restart Visual Studio Code if you're using that.
Sometimes it can be a bit weird, and giving it a restart is often the solution to a problem, so please
don't presume you actually have a problem until you know for sure that the problem persists.
If you've given your compiler a kick or your code editor a kick, do come and use the Q&A.
If you do run into an issue, but please do provide as much information about the problem as you can.
About 50% of the time, most of my responses to you questions on there are simply asking the students
for more information.
Because just like you as a software developer, you need information to solve a problem.
I need information to solve a problem.
So please make sure you provide as much information about the error as possible.
And please let me know what you've already tried.
Because if it's not clear that you've checked the basics and restarted that API server or restarted
VSCode, then I may suggest that as the first option.
And if you've already tried that, then please do let me know.
If you do have a Non-course related question, then please use a facility such as Stack Overflow, which
is an excellent resource to help you resolve Non-course related questions.
I'm just a single developer that doesn't have an unlimited amount of time, and I do not have the capacity
to answer questions not related to this trading course, but Stack Overflow is a resource that effectively
connects you to the entire developer community, and literally thousands of developers that might be
able to assist you with code that's not related to this particular training course.
So please do make an account on there and ask any non-course related questions on there and the Q&A
response times.
I usually can get back to students in 24 to 48 hours, and I'm normally on there once a day, but I
do take 1 or 2 days off per week, so you can usually expect a response in 24 to 48 hours.
So please do make the questions count.
Provide as much information as you can about the problem.
That would allow me to give you an answer to the issue, rather than asking you a follow up question,
because I need to get more information from you.
So now that's the admin out of the way.
Let's next take a look at starting to build the application.