 Writing code is like creating a recipe. You know, how do you make a pizza, right? Or make a bread or something. What material need, what are the steps you need to take in order to build that thing? So you need all the ingredients. These are the inputs. And then the way you combine them is the processing part. These are the instructions to process or build or bake that pie or that cake, whatever it is. And the output is when you've got the baked cake or whatever that output is. So before you solve your problem, before you even develop a program, you need to find out what the problem is. So you go through the analyzing process. This is very typical for not only programming, but when you talk about a process in manufacturing or build something or even solve a problem. Or even like, you know, we design office space in your office. Same, same idea. So you define the problem, what that is. You don't know if you don't know the problem, you can't really design something to fix it, right? You don't know how to code your problem to solve the problem. So you must understand the problem first. And you have to understand it really well to make sure your code works the way you should. So analyze the problem. And then you design, you plan that problem. And then design interface is just basically draw on the output, basically this part here. And I'll basically like buttons and, you know, text locations and columns and rows and things like that. And then you do the processing part here. Write the code. Step five is test and debug. And then step six is whenever it's completed, then you basically write the documentation. This part here is after everything is all done and you're ready to publish your code or program. And then you will write a full documentation. This is more of a manual for your program. Both and a separate, you know, document also inside the code itself. I'll recall this code documentation, which I highly recommend you do as well when you start coding, okay? So here again, these are the designing part. A lot of time you will spend on designing the interface, the layout we look like. Not a lot of time you spend here, but it does take some time to do that. You spend about, I would say to me, like a third of your time will be doing this part here. Or maybe a fourth of your time, one quarter of your time here. And maybe one quarter of your time or maybe more, I guess, I'd say about, or a third or more of your time coding. A lot of your time will be spent using step five. So in a life of a programmer, you will see that most programmers will spend about 50 to 60% or more of your time testing and debugging. Okay? And you will see why later as you start coding. I have students like spend hours and hours to solve a really simple problem because something that doesn't work or it is the error that couldn't fix it, right? So when you write a program, when you want to deploy it for production ready, you have to test it. And when you test it, you have to do all sorts of testing to make sure that all the possible errors are caught and fixed before you could publish that program or that output of that, whatever it is, right? So you want to make it as perfect as possible. That's why a lot of time is spent in this step number five because testing here doesn't mean you just test. It's also involving recoding your code. You go back and we code again, fix your code. That's why it's so much, it takes so much time.