How To Write An Exam Review That People Want And Need!

As I reach the end of Spring semester as a junior in college, my mind already wants to shift towards Summer vacation mode. I have one thing keeping me from being free of my class obligations: FINAL EXAMS.

Ending the semester on a good note can make your grade sky rocket to where you need it to be. Students cannot expect professors to give study guides for exams. Therefore, I prioritize making a study guide that’s easy to understand, underlines basic concepts, key vocabulary and practice questions. This is what I do:

First, I begin by going through the notes I took during class, usually from PowerPoint or directly from the professor’s lecture. Understanding the content that will go on a good review is the first part.

Secondly, I read the selected chapters from the coursepack on Omega Notes. The second part includes the structure and layout out of the document. Make the study guide attractive by bolding vocabularyhighlighting equationsinserting images & graphs and tailor the language! Sometimes professors use language that can make material more difficult to understand; make the guide in the language you comprehend. By bolding the vocabulary words and highlighting the equations, I  can differentiate those words from the rest and memorize them. Adding addition personal notes such as page references or examples from class really help because.

If you feel like the professor may be moving to fast or there is just too much to write or type, write the main points and go back to them on the course pack or textbook later. Writing every single word on the PowerPoint slide may not help you understand the big picture of the concept. Often exams are tailored around understanding the big idea and knowing how to apply it to questions. What’s better than having a solid study guide for the exam that ensures a good grade? Well, making money off of it! By going to class every day and taking the time to make a study guide, you create a valuable product students will pay for. I sell all of my study guides on Omega Notes and earned over $300. That’s right, the big benefit is that I make money studying at really no cost.

5 Easy Ways Of Getting Into Coding

5 easy ways of getting into coding

As we all know, everything today is about technology. As this massive trend moves forward in our life, it is becoming essential to be involved in every aspect of it. Coding does not definitely scape one of the fundamental topics that millennium have to learn about this technological boom

1. Start by brainstorming

This is probably one of the most important points before developing anything. This is relevant because coding is not a sequential activity that you can engage very easily. It requires a lot of thinking behind to understand the logic of what you want to program. Brainstorming is proved to be one of the best ways to start basically any project, not only coding, but also a paper, an exam, etc. Brainstorming basically puts your brain to think in a very open and broad way; the most important key to remember is that all ideas are valid. Do not discard anything related to what you want to do.

2. Have an overall design of the code

Having a design that can represent how your code is going to look like is very important for planning out the behavior of the program. This is probably the most important and critical point of the coding because it allows you to think what classes are going to do, as well as the relation they are going to have inside the program. Designing good code is considered to be even better and more clear than just coding. In fact, there is a specific language called UML (unified modeling language) that provides you the standard way of visualizing the the design of your code. My favorite tool to use to design an UML for your program would be LucidChart.

3. Do a quick pseudo code the overall idea

Pseudo code is absolutely a relevant step you definitely should take before start programming. This will allow you to have a dumb down version of your program in simple words without confusing yourself in the code. It is a very simple way to organize what you are going to do by putting words in the logic behind the code you are trying to accomplish. Furthermore, this will allow you to understand what level of the code you have made a mistake if that is the case. Remember just to keep you pseudo codes easy to understand so that you won’t have any problem going back whenever you get stuck figuring out an error that your code might have. 

4. Start by working on a small scale

This is one of the most tempting parts of the process. For some, once they feel like they have some experience in the previous steps, they think they are going to fly. For some others, they get intimidated by the amount of complexity the code might have (based on the UML or pseudo code). But what is most important is to always start small; only little is going to get accomplished if you think you are going to code four hundred lines of code in the first couple of programs. Instead, think about experimenting first; start testing things, see how they are, what they do. That is the only way you are going to learn without spending too much time trying to figure out what you have messed up in your code. Plus it is pretty easy to build up on previous code once you get started with the easy part. So just try to simplify the complexity of your code into a smaller scale.

.Test your code

Do not hesitate This won’t particularly happen to everybody, but for the ones that are a little more hesitant about new technologies, specially for something technical as coding, it is OKAY to make mistakes. And they will surely happen!! Specially if you are new to this. But guess what, as everything in life, you are going to learn from what you made wrong. Not everything is about wining or getting everything right. There always need to be some sort of imperfection in what you do. If not, we were not humans at all. So I would recommend that whenever you have your code ready to test, hit that enter keyboard and see what happens. There is absolutely nothing more satisfactory than figuring out why your code was not compiling, or giving you the wrong data. So go ahead and try this!!