The University of California Board of Regents dismissed a professor from the Riverside campus named Rob Latham after his student issued a formal complaint alleging him of sexually harassing that student with the comment “ride you hard,” and distributing drugs to other students.
If a heterosexual man had made the exact same statement, no lewd implication would ever have been inferred.
The University of California Board of Regents dismissed a gay professor from the Riverside campus named Rob Latham.
One of his students issued a formal complaint alleging him of sexually harassing that student with the comment “ride you hard,” as well as distributing drugs to other students.
The Hearing Committee dismissed the original charges of “flagrant, serial sexual harassment,” and instead charged him for his recurring “psychological illness.”
I can’t stop thinking about the funny and hard things I learned at my previous college.
Sometimes, I wish I learned these things earlier.
*Sigh* Well, at least it’s a good thing that I learned them.
“Why’d you have to go and make things so complicated?” *Shrugs*
#1 How to use a smartphone
No joke. I got a smartphone as my high school graduation present.
At first, the smartphone felt huuuge in my small hands compared to my first cellphone.
It took me forever (the entire freshman year of college) to learn how to use a smartphone. (And I’m still learning how to use it as I continue to update it.)
I feel bad for all my family and friends who had to put-up with me trying to use my phone. My family would have a tough-time communicating with me because of long-distance calls, while my friends and I were really into texting each other.
It’s frustrating. Smartphones have so many features, and it’s difficult to manage all of them.
Here are some of the things I learned (because I feel like listing them, and looking back at this post with giggles):
1.) There are different volume settings for ringtone, media, notifications, system, and calling.
2.) Make sure you completely mute your phone whenever you need to. (Make sure you manually adjust all the volume bars for the ringtone, media, and calling modes.)
3.) If you call someone with a low calling volume, and you tell them that you can’t hear them when they can hear you on their end, then they’ll think you’re crazy (and most likely try calling you again to get the same results).
4.) If you call someone and they sound muffled even though your calling volume is fine, then either you, the person you’re calling, or both of you are not in a calling-friendly setting.
5.) It’s hard to use the touchscreen when you’re in calling-mode because the touchscreen automatically turns-off and blacks-out in that mode.
6.) You need to download an emoji keyboard from the app store because your default keyboard doesn’t always have the emoji option in all the messaging apps.
7.) You don’t have to use the default wallpaper and screensaver options.
8.) Don’t use live wallpapers and screensavers even though they’re so cool and your old cellphone never had those options.
9.) A “butt-dial” means that you accidentally made a phone call, regardless of whether or not your butt was the cause of it.
10.) You can lock your phone so that you don’t accidentally touch any applications (and accidentally “butt-dial” people).
11.) Use your (then-new) Facebook account to keep yourself updated with college events and news.
12.) Facebook Messenger (supposedly) has a clearer-sounding calling feature than my default phone app.
13.) Don’t keep any apps running in the background because they use up your 4G, and consequentially slow down the loading-time for your apps.
14.) Just turn-off your phone whenever you travel. I always remember to turn-on “Airplane Mode”, but I usually forget to turn it off.
15.) You can delay message sending.
16.) Don’t delay message sending anymore. This feature causes a lot of problems, including failed message sending. (My messages don’t always send at the predicted time. They either don’t send at all, or get sent much, much later.)
And last, but not least…
17.) It’s okay. You were trying to get accustomed to new technology. Some of the problems you had were either due to the manufacturer, the not-so-calling-friendly environment, or just your clumsiness. Just thank God that this isn’t your phone:
Jotting down all my coding ideas on paper before typing them on the computer has helped me become a more efficient programmer.
As a freshman college student who had no prior programming experience before college, learning a programming language was a tough challenge for me.
As a noob placed in a computer science class mixed with experienced and non-experienced programmers, I mimicked my class’ overall programming style: typing code, checking errors through compiling the program, and revising the code until the program works.
Essentially, I was mindlessly programming.
That method of programming led me to confusion and frustration. Not only was I heavily dependent on the compiler to identify errors, but I could neither trace my own code nor understand code written by other programmers. Looking at long lines of multicolored code on computer screens became a sore to my eyes. Countless hours were spent debugging and, unintentionally, creating new bugs.
Looking at long lines of multicolored code on computer screens became a sore to my eyes. Countless hours were spent debugging and, unintentionally, creating new bugs. Old concepts were occasionally forgotten, and new concepts became increasingly difficult to understand.
I would attend lectures in hopes of grasping a better understanding of what I learned from the readings and getting hints on how to tackle the upcoming programming assignments. The professor not only summarized the assigned readings, but he ignored questions and comments that “can be answered by the textbook.”
Because our class’ textbook (zyBooks) is designed for students to complete interactive activities while compiling their programs within the textbook, I relied on the textbook’s built-in compiler just like how I relied on the compiler in my Cloud 9 workspace.
When I finally flunked the exam, I was handicapped at a grade lower than my overall class grade and my seat for the succeeding computer science course was dropped.
On the brightside, I was able to reflect on how I have been studying for computer science during the break that followed exam week. As soon as I realized that the A’s that I have been receiving on programming assignments were not reflective of how efficiently I can write code, I began to wonder to myself: “How can I train myself to become a human compiler?”
Since the exams for computer science were taken on paper and without the help of a compiler, I decided to revisit all of the previous chapters I read and recomplete all of my programming assignments on paper. Also, as I was doing those things, I made it a goal for myself to create successful programs within at most ten tries.
By the time the new quarter began, I was able to train my brain to predict the result of my programs. Determining the type of errors produced by my programs and writing the simplest codes to solve complex problems became a breeze to me.
I saved all of my written programming notes in a binder so that I can see my thought process as I was trying to meet the program specifications, review mistakes I need to avoid, and write comments for each line of code.
Along with those written notes are all the programs I saved in my Cloud 9 workspace. For every program that I created on paper first, I would type them out in Cloud 9, compile them, add comments to lines that had errors that I failed to see, and duplicate a copy of those programs so that I can compare my revisions to the original code.
As my winter quarter is coming to a close, I hope I can prepare myself for the final exam. I remember that the final exam is a lot more challenging than the midterm exam, since it requires students to actually write code instead of selecting an answer from multiple choices.