I helped set up the physics exhibition by Dr. Gary Deleo on September 18 as part of the Society of Physics Students. Unfortunately I couldn’t stay for long. Despite not being able to see the second half of the exhibition, I got to play around with some sweet physics stuff and eat some great pizza.
Iron Filing Letters:
Dr. Deleo demonstrating a nifty gadget:
Last week, I attended the Fall Career Fair, which was also my first career fair. It was a great experience, and I will definitely be attending next year as well. I went in business formal attire, though I did spot a few students in business casual attire. There were over 150 companies and a mass of students there. Needless to say, I was sweltering in a full suit, and the sheer number of bodies did not help either. I had trouble getting to some of the popular companies like the Big Four. About half the companies I interacted with were not accepting sophomore resumes as they had no opportunities for sophomores. I had better luck with some of the smaller tech companies; many of them seemed promising for an internship. I only handed out 2/3 of the resumes I had brought to the career fair, but I came mainly for the experience anyway. Hopefully I will have obtained a summer internship as well.
Later on, I will post pictures that I took at the career fair.
I am going to discuss a topic that is pretty touchy: cheating. I am not referring to cheating during a test; no one is foolish enough to blatantly do that. The cheating I am referring to is copying someone else’s work. When you are either pressed for time or do not understand a subject, you might be tempted to copy someone else’s work. You might copy from an online source or from a friend. When you copy work from a friend, you put your friend at risk as well. Generally, if you are caught copying someone else’s work, both parties will be held responsible. It may not seem fair, but allowing someone to copy your work will put both of you at a disadvantage.
Today, my CSE-17 professor discussed academic integrity. He mentioned it today because he noticed that several people had work that was very similar. For a subject such as computer science, it is very easy and tempting to copy someone else’s code. You can simply copy and paste and maybe change some variables. However, if you do this you run a huge risk of being caught. The code that we submit is run through a complicated cheat detecting software that should have no issues finding similarities in people’s code. To put this in perspective, last year, 12 people received failing grades because they were caught cheating.
As a Teaching Assistant for CSE-2, I understand the importance of learning the concepts and working individually. However, I do think that working in groups is quite productive. As long as there is no copying occurring, working in a group can help individuals learn concepts in a more accessible manner. When someone asks me a question, I will first try explain the concept. If that does not work, I will make small suggestions and hints. Finally, if he/she cannot understand, I will give them the solution and walk him/her through the solution and how to come by it. Through this way, I can still help people without the risk of cheating.
Basically, do not cheat or you will eventually regret it.
Tonight was the Microsoft Coding Competition, essentially a hackathon sponsored by Microsoft. It was ran by the recruiters who were at the career fair yesterday. You were able to team up with 2 other friends and try to complete as many coding problems as possible. Whichever team had the most points at the end of a two hour span won.
Myself and another friend teamed up. There were a total of 6 problems, some having different point values. The problems were surprisingly difficult, especially for a two hour event, but then again this was Microsoft and you need to be the best. My friend and I did not win, unfortunately. We were glad to get some problems and see our team name up on the leaderboard at least, and get some free food of course.
I’m glad I went. It was definitely an experience and I had fun. I even won a t-shirt! So that was cool. I am saving all the problems that were a part of the competition to do on my own time for more practice.
I partook in the first of many projects to come at Lehigh IEEE. It was informative, neat and simple. I had a lot of fun!
Yesterday was the career fair. It was very crowded and hot. Luckily, I got there early before the big crowds came. It was very helpful. I was able to talk to recruiters from many different companies and give out my resume. It was difficult to talk to recruiters from the top companies, such as Microsoft, Lockheed Martin, IBM, Boeing, and others, because everyone wants to work there and it was a mob scene around each one of their booths.
The best part of the career fair was I was able to stop by and talk to the recruiters of companies I have already applied and interviewed for. The woman I had my initial phone interview with for the company that is my top choice currently was there, so I got the opportunity to speak with her for quite some time.
All in all, it was a great experience and am hoping I meet the needs of some companies and hear back from them soon.