First, data analytics is NOT a coding course!!! However, we do need the basic SQL and R skills to manipulate data.
I do know it may be your first time to touch the nerd-like syntaxes, statements, or even the ugly UI of MySQL Workbench. I had the same feelings when I was a freshman only trying to pass a C programming class several years ago.
Here are my suggestions to survive an intro-level coding class. Please take your time to review the slides/class capture and complete ICA #4. I believe the one who just knows how to master driving is the best teacher for those who sit behind the wheel for the first time.
- Read/run the sample codes. Understand the goal of a piece of sample codes and then try to run it in the corresponding software platform (Integrated Development Environment, IDE, e.g., MySQL Workbench, RStudio, Microsoft Visual Studio, etc.) Pay attention to the code details (e.g., letter case, space, colors of words showed in a SQL query tab, etc.) The final goal is to get the very basic statements to realize the very basic requirements – maybe show “Hello, World!” on the screen (i.e., console panel);
- Close the slides/textbooks and try to realize the basic requirements and write codes by YOURSELF. Now, you should have some sense to replicate the codes in step 1. Try to write and run them by yourself. If you cannot write them, jump to step 1 and try again;
- Compare your codes with the sample ones. You may find minor typos or major differences. Check whether you can tell the reasons of those deviations. If you cannot, google it/sent me an email/visit office hours on Mondays and Wednesdays. If you can, congrats! You can write your codes!
After implicating these survival skills, you may find coding is not that boring. Actually, you can create your own programs. Just as people enjoy building their own Minecraft worlds, requiring creativity from players. If so, consider the following tips.
- Codes are cold while reliable. Codes can only be executed to realize your requirements (if no errors). They will not do more than you required or change the outcomes by themselves except you trained them to do so. However, they are thus reliable. For example, if you program yourself to check conditions (such as your wallet and keychain in the left pant pocket, your mobile phone in the right pant pocket) before you execute to hang out every time, you could always have the confidence to close your apartment door without worrying about being locked out or losing contact with friends.
- Programming as teaching a young teenager. Before starting writing your codes, think about how to reach the goal as you are teaching a young human to do so. Then try to put all the steps (or algorithm) you taught into codes. For example, if you want to write your own MAX() function used in our class, first try to think about how to teach a 3/4-year-old human to find the largest one in a basket with 12 apples. Maybe you can ask the young to grab one in hand, and then draw another from the basket to compare their sizes. Keep the larger one in hand and put the other in an empty basket. Then repeat the two steps above until he/she compare all the apples. Finally, the one in his/her hand must be the largest apple out of the 12 ones.
- Find the beautiful parts of coding. Codes can be treated as your servant without any complaints. You can assign them to do almost endless boring repeated work. They will always be loyal to you as a developer unless you train them to be independent. You can learn almost every single languages via online resources, such as YouTube, Lynda, W3Schools, etc. You can design a beautiful and user-friendly graphical user interface(GUI)/App/MIS/Website…
Hope these could help you get to know coding and good luck!
Best,
Zhe (Joe) Deng
Leave a Reply