Important Announcement: After blogging for more than a year, the UT CS Department has given me an opportunity to speak about the importance of writing as a CS major. It's my pleasure to invite you out to GDC 6.102 this Friday at 12PM to the talk. Lunch will be catered with Cane's. Additionally, a raffle will be held at the end of the session, post Q&A, for a FREE Raspberry PI kit and APPLE WATCH. Finally, the first 5 people who RSVP to the sign-up link at the bottom of the blog post will get an exclusive UTCS Blog T-Shirt. Hope to see you guys out there!
This past week has been quite a busy season for me. After returning from MHacks the weekend before where I lived off of only 4 hours of sleep a day and got to hang out/hack with a few of my friends that I knew in Michigan, I found myself thrown back into the hay of things here at UT. Finishing up Graphics project #1 was a struggle and having to spend most of the days cycling through work, school, and church stuff, I found myself with very little room to breath or time to really rest.
These past few days have been quite the recruiting experience. Usually, whenever I think about recruiting, my mind does a double take because of the mixed feelings I have about the whole process - spending days upon days perfecting a resume, reading and writing dozens of emails to various companies, and receiving the sad but real amount of rejections post first-round interview all the way till final interview. Basically, a roller coaster of emotions (definitely a lot of good times though).
What is your vision? Why do you do what you do?
Urban Dictionary defines Sophomore slump as a time "During a college student's sophomore year, [where] their GPA drops after having a high GPA from their freshman year".
This slump is something I know many of my friends have expressed to me, and I, myself, have had my own share of exasperation. Even after OS (The best and worst class in CS), I find myself potentially experiencing Sophomore Slump pt. 2 because of my non-CS classes.
In light of the end of my Sophomore slump, though, I've found this past semester to be a fruitful time:
As finals are coming up, and deadlines for projects approach along the horizon, I have found that I am guilty of procrastination on so many levels.
Procrastinating occurs through habit, mindless action, and/or intentional avoidance of responsibility. Whether watching a late night show of celebrities doing peculiar acts, reading blog posts, or surfing Facebook on the latest memes or doggo content, I've found procrastinating to be focused on activities that have some to little/no value in the moment.
This past semester, I got accepted as a tech organizer for Freetail Hackers. By joining them, I've been able to have the wonderful opportunity to partner with many other students at UT with the vision of making hackathons smoothly run and amazing. I have to say that I really loved being in the org. The community within Freetail Hackers is really amazing, not only because of the miscellaneous Assassins games we hold or the various number of memes that get shared, but also because of all the amazing leaders and skilled organizers I get to meet and work with in the org.
When I came to college, I didn't really come with much passion for CS. Sure, I came in with a lack of clarity in what the future held and a bright amount of curiosity as a freshman. I had a far-reaching desire outside of class to try out new things, scour the school for free food and shirts at events, and traverse through many different orgs surrounding the inner campus. But when it came to programming, I had considered it more of a matter-of-fact chore to do. Having taken CS classes in high school, I assumed much of programming to be self-explanatory.
Hackathons are really fun. Unlike college, where most projects in class are set in stone, hackathons are loosely structured, which gives a lot of flexibility on the wide range topics that can be pursued in 24 hours. Things can become easily scattered, though, even when there is a set theme behind a hackathon. Which means one of the first (and hardest) steps that need to be taken is to come up with an idea to work on.
I haven't always loved hackathons. In fact, I used to think hackathons were rather dull.
Because of a bad experience, a lack of coding ability, and no team, I found a lot of distaste in hackathons and completely shunned the idea. 24 hours staying up while stress gorging over fruit snacks and random assorted foods because of a project that may not be completed and needed to judges may look with dull looks on their faces? Not my ideal weekend.
The views, opinions and positions expressed by the authors and those providing comments on these blogs are theirs alone, and do not necessarily reflect the views, opinions or positions of UT Computer Science, The University of Texas or any employee thereof.