CST 338: Week 1
For the first week of CST 338 we were mostly taught how to set everything up with InthelliJ and make it compile java language using JDK. We were also instructed on how to set up android studio which we haven't gone much further other than installing it and setting it up for future projects. We were also given task which required us to use Github and learn from the experience.
I haven't code nor do I have experience in coding java but one of the practices that help me was the coding challenges in codingbat.com. The knowledge I have with java is the documentations I read and basic ideas like initiating variable, some few logic flows like if statements and loops, and some basic arithmetic set up. The challenges in codingbat.com is beginner friendly and starts easy and it amplifies the difficulty as user moves a long. I like this method since I get comfortable as I move along. Some of the challenges I've encounter are remembering syntax and methods I can use for certain problems. I always find myself re-reading some documents on which method to use and how to invoke them. For example, one of the errors I encounter is how I try to access certain index in a list like python but in java the syntax is different. I have to keep some notes open as well when I was doing the Map portion of the challenges. Luckily the website provide the ones that I would need in solving the problems.
There are problems that took me a while to get or answer correctly. The way I would usually go about problems is to breakdown what I need, think of all the methods I need and can use, then execute the solution I have. The solution I have are smaller parts put together so I can easily debug which part I got wrong. For simpler problems which are the 1 stars, I simply just return what comes first to my mind. Overall this method is what worked best for me, since there is no debugger, I have to rely on myself to check what is wrong that is why it is best to try to get the proper answer in 1 try. There are times where I have to debug my code and to see where the problem is. Luckily the website also provides me all the test cases and the expected result which help me figure out what I'm doing wrong most of the times.
Comments
Post a Comment