The Computer Systems course I took this semester was the source of surprises. Through the study of the C language, assembly, and other concepts, I feel I have gained some more insight into how computers operate. The biggest revelation was the sheer magnitude of the assembly lines to code ratio. By writing code in MIPS assembly, I gained an appreciation for the abstraction that C and other languages provide. In short, writing and thinking about breaking code into their smaller steps helps you acquire a similar level of appreciation. The process of writing assembly code is somewhat similar to the process of building a startup. There is a procedure with many substeps. The entrepreneurship course taught me that, while the class is easy, the actual process of creating a startup is anything but easy. There are many considerations made on the basis of market research. The biggest revelation was the amount of detailed planning and adaptation required to make it as an entrepreneur. Like an entrepreneur, I had the pleasure of building relationships with faculty. My biggest success in building a relationship with a professor is in my computer systems course. I answered questions on more than one occasion in class. The greatest obstacle is letting yourself be known and giving professors a reason to invest further into your development. One strategy is to visit office hours more often and not just for administrative issues. Office hours can be busy sometimes so keep that in mind. Outside of professor support, I have fellow students that help support my academic journey. One example is the teaching assistants. They provide answers to a lot of questions you may have, and I found them to be useful for helping me understand various concepts. Students in the same year as me formed study groups to further strengthen each member's understanding. Incoming freshmen can find common ground with students in their class and form study groups to capitalize on a chance to learn by explaining or learn by hearing others explain concepts. In retrospect, I feel that I was least prepared for the long lines in office hours in my computer science class. The volume of content can be challenging to manage and grasp, so a lot of people visit office hours during many days of the week. My advice is basically the same as what the teacher will tell incoming students: "go to office hours early". I understand that it is easier said than done, but still try to go early. Going to office hours days before a project is due is not a viable strategy at all. Additionally, it is helpful to take a difficult course as CMSC216 during the spring semester. Spring break helps you get your bearings in order and have a more successful experience prior to finals and other midterms and projects. During my spring break, I was able to get some time to work on a project I had for the course and finish a significant part of it.