Deepti’s response reminded me of my beginning of learning to code. I was using a different language, I didn’t have a programming background, and I had never taken a course for that language. Yet I was tasked to build a monitoring software, and the only thing provided to me was a programming interface to start the work.
The software had to work with a hardware device, so I googled a lot of articles using the language’s name and the device’s name as the keywords. I forgot how many days it took me to finally reach the first milestone, but at least I had made something.
Since the first day of my programming life, it has been 15 years and I have not mastered a programming language through course. It has always been hands-on work that matters the most.
If people can achieve a certain objective with a certain Python package, and I don’t know about it, then I google “package objective example”. Then, I read, I copy any example code to my jupyter notebook, and I experiment.
If I went back to 15 years ago to the moment right before I was tasked that software, given that I would not retain my memory over the 15 years and so I didn’t know that I would manage to finish it. @Mohannad_Abdelfattah, let me ask you,
- should I take up that task?
- should I ask my boss to wait and let me finish a few courses first?
- should I ask my boss back whether I should take up the task?
I think the key here is, because I decided to finish the software, I had to take whatever actions I needed to help me get through all of the obstacles. It was my decision.
At that time, I didn’t know what problem was ahead, and nobody on the team knew about that software language, but I did know there might be discussions and examples on the internet, and there was a library nearby. I had a programming interface and a keyboard, and I could type and try. I could read and experiment. I could learn from my mistakes.
@Mohannad_Abdelfattah, I hope you don’t have less than what I had, so then the question is, what is your decision? Do you require yourself to know how to code? If you do, then my recommendation is whenever you read something you don’t know, write that something down on a piece of paper, and then start googling about it. After you manage it, cross it out from the paper.
It will take as long as you need to get everything clear, and it is one way of self-learning.
Nobody here can tell you what you cannot do. I also think we cannot tell you what you should do, but only you can decide what you want to do.