Month: January 2018

As I prepare to make the move to the west coast, I constantly hear the phrase “Oh, what a good thing to do while you’re young!” The attitude most people have towards my decision to move west reflects my attitude towards job jumping. I think job jumping can be great! I agree with the articles that discuss how job hopping can increasing your pay and your value as an employee. However, I think there is a point where we must draw the line.

My personal career path is headed towards one dream job, but there are multiple potential paths to get there. The job I have already signed for is not my dream job, but it is a great place to start out and I feel very lucky to have the opportunity. I think if I do not change companies after a few years, I will most likely at least change teams within the company to diversify my skills. Otherwise I may change companies a couple times and work on making myself a better candidate for my dream role. However, once I feel ready to apply to my dream company I am not sure I could see myself wanting to be anywhere else. Maybe I would consider switching teams or divisions within the company, but I think if you are happy with where you are at, why change?

I think job jumping can be fun and exciting when you are young and chasing money. It keeps you engaged and satisfies your need to continue learning more and pushing your self to become better. It can also help you increase your own value as an employee. I recently talked to a woman who loved her job at the smaller company she was working at but felt she was not being paid enough money, so she moved to a new position at a big tech company, and then her old company offered her much more money to come back after a year or so. It is unfortunate that some companies do not realize what they are missing until it’s gone, but good for this woman to finally be paid what she is truly worth by the company she most enjoyed working at.

I do, however, feel there is a point in life where job jumping will lose its value. One major flaw to job jumping is never staying at a company long enough to fully vest your stock options or retirement. People will lose out on so much money by leaving companies before they earn their full potential of stock or before they are eligible to receive and keep their companies 401k matching policies. Another flaw not staying long enough to earn a promotion. I think being promoted within a company can say a lot more on your resume than seeing you work the same role at two different companies. There is also a point in your life where you will have important things that require a little more stability, like a spouse or children. When a family is involved in your decisions you have to think more about switching locations or jobs, along with switching health and insurance plans. You also might want a more stable job that requires less outside time so you can spend more time with your family instead of constantly needing to spend outside of work time interviewing, preparing for interviews, emailing recruiters, applying to new jobs, and learning the skills required for a new job.

Company loyalty is another fear with job jumping. I have already told one story in this blog where switching jobs ended up being a good idea for someone and allowed them to return to the company she previously worked for and still get the raise she deserved. In that situation, she showed loyalty to the company, but it seems unfair to her that the company did not just pay her what she deserved in the first place. While I do see how company loyalty can look good on an resume, I also think it is fair to have the understanding that just as I can be let go at anytime from a company, I should be able to leave at any time for any reason as well.

Non-competes and NDA’s are tricky. I understand from the company’s point of view that they would not want a former employee using their former companies ideas and tools at another competing company. However, as an employee, I feel I should be able to seek employment at another competing company if I feel I am being treated unfairly at my current company. For example, if it were someone’s dream job to work on e-commerce, but they were being treated unfairly in their current e-commerce position, it seems unfair to tell that employee that for the next year and half they can not work at their dream job, or use the skills they know how to use best, just because they are afraid of their secrets being traded between companies. It seems unethical to restrict someone from working in a job that they love for selfish reasons.

I think Mark Zuckerburg gives the best description of what a hacker is:

The word “hacker” has an unfairly negative connotation from being portrayed in the media as people who break into computers. In reality, hacking just means building something quickly or testing the boundaries of what can be done. Like most things, it can be used for good or bad, but the vast majority of hackers I’ve met tend to be idealistic people who want to have a positive impact on the world.

I really like his explanation of what a hacker is because it is optimistic and focuses more on the good a hacker can do than on the bad. He also includes

Hackers believe that something can always be better, and that nothing is ever complete. They just have to go fix it

I think this addition to his statement above solidifies his opinion that hackers are trying to better the world. Unfortunately, the other articles I read seemed to focus more on the freedoms that hackers deserve and the unfair treatment of hackers, and these are the arguments against the “negative connotation” that I personally find holes in and that cause me to relate less and less to the idea of being a “hacker.”

I relate to Zuckerburg’s core values he identifies: Focus on Impact, Move Fast, Be Bold, Be Open, and Build Social Value. These values I think are a great way to sum up the core values of what a hacker should strive for! However, as stated above, most articles on “hacker culture” focus on other values that I disagree with. According the the wikipedia article on Hacker Ethics,  the core values of a hacker are: sharing, openness, decentralization, free access to computers, and world improvement. I was ok with this list until they continued the list with additions from Steven Levy. The two most problematic additions for me are “Access to computers—and anything which might teach you something about the way the world works—should be unlimited and total. Always yield to the Hands-On Imperative!” and “All information should be free.” In many articles I find that the biggest thing i disagree with is Hackers belief that they should just be able to access anything. I do not think Hackers should be able to access all information, and I think certain boundaries are necessary. This promotes Zuckerburg’s idea of nothing being complete, and that anyone can help to fix things that require fixing. But this also means bad people can exploit these errors, and can have access to information that is not necessary for them to have access to. By allowing all information to be free and anyone being able to access any computer, we are allowing the bad guys to also have access to any information and anyones computer.

The idea of anyone being able to access anyone’s information is selfish on the part of the hacker. I feel like this is allowing those who have the knowledge of hacking to be able to exploit those who do not. I think security and privacy are there for a very important reason and giving hackers too much power is dangerous.

I do however, agree with a few of Levy’s additions to hacker ethics.

• Hackers should be judged by their hacking, not criteria such as degrees, age, race, sex, or position
• You can create art and beauty on a computer
• Computers can change your life for the better

I think there should be more equality in computer science than there is now, and I think we should be judged solely on our skills. I also agree that hackers can create beautiful things and change peoples life in a positive way! These three statements support Mark Zuckerburg’s definition of a hacker that I so closely relate to and I find it a shame that anyone would take such a beautiful art and ruin it for others. It is not enough to encourage hacker ethics, unfortunately there will always be bad people out there who ruin the fun for everyone, and use their power for evil.

I agree with the author of “Hackers and Painters” that Hacking can be a beautiful and expressive art form. However, it is people like the author of”The Conscience of a Hacker” that ruin the fun and beauty for everyone. I find this author to be arrogant, whiny, and dangerous. He makes some valid points about hacking culture, however the paragraph where he admits he is a criminal whose crimes include being “curious” and “outsmarting you” is the reason hackers are given a bad name. People who believe they are above others because of their skill, and who should have access to whatever they want are dangerous.

There are many lessons to learn from the Parable of the Talents. My biggest take aways are that success is related to the level of work we put into something and that we are held accountable for our work. The first and second servant are  rewarded for their hard work and their use of the talents they were given. The third servant does not work hard like the first and second servant and instead bury’s his talents, producing no more. Their master is displeased with the third servant and he now must be held accountable for his lack of success.

I do understand that in this parable “talents” refers to a form of currency. However, it is easy to think about it using the other definition of talents as well. If we think of talent to mean “a special natural ability or aptitude” (as defined by dictionary.com), this story is about two servants who take their god given abilities and work hard to learn new ones. They are then rewarded for their successes and hard work. When I watched the video clip of Karlie Kloss assigned with this reading, I connected her message, with this parable and my life as a computer scientist. Kloss discussed having a love for math, and not being sure what she could do with it other than become a doctor. No one recognized her talents for math and suggest she take a computer science course or pushed her towards engineering. However, she recognized her talent for problem solving and is working right now to expand her god-given talents and she discusses the rewards of finding a way to use her talents. I had a similar journey into computer science. I loved math, had no idea what to do with it, and had no one suggest to me or push me to learn how to code. This resulted in me finding out about computer science kind of late in the game.

I was very intimidated hearing my classmates in my computer science intro course talk about their prior experience  with the field and I felt very behind. I later learned I was not alone and many people were learning how to code for the first time, but before I had this knowledge it pushed to work even harder to perfect this new talent. In the video “What Most Schools Don’t Teach” they further discuss the pleasure one feels when you have a success in computer science. The first time you see “Hello World” pop up in your terminal, every bug you finally fix, and any final working product can bring someone an amazing sense of pride. If I had done as the third brother, and buried my talent when I felt intimidated by other students talents, I would have never found the sense of reward that exists in computer science. If you work hard and recognize your own talents, you will find success and happiness.

On the other hand, the third brother who buried his talents and did not work hard was scolded for his actions and held accountable. This is a smart lesson to remember as you journey through computer science.  It is important to remember that we always accountable for a product we produce. Some computer scientists will eventually face a difficult situation where the work they are doing may make them feel morally uncomfortable. For example, the author of “The Code I’m Still Ashamed Of” writes about a project he consulted where he did what the customer asked, but the product may have greatly affected the lives of people who used it, and may have even caused death. Although the part of the project he worked on was not the cause of death, he still felt guilt because he was a part of the team that promoted this product.    He worked hard and found the success of completing the project as customer asked, but now feels accountable for being a part of the problem. As computer scientists we must remember that what we do can hurt others and have negative side effects.

Being a computer scientist has highs and lows. We experience amazing pride as we work hard and find success, but we also can be held accountable for our work if it goes bad. The overall lesson I am taking away from this parable is that we must work hard to find success in life and to develop our talents, but we also must remember the ramifications of our hard work and actions. If you work hard for the wrong cause, you will be held accountable, or at least experience guilt.

Hi! I am Kylie Hausch, a senior Computer Science student at Notre Dame. I am in my final year of the five-year dual-degree engineering program with Saint Mary’s College and Notre Dame. I graduated from Saint Mary’s in May 2017 with a B.S. in Computing and Applied Mathematics. I chose to study Math and Computer Science because of my love for solving puzzles. In high school, math was my favorite subject and I was unsure what I could do with that in the future. One of my teachers encouraged me to consider engineering. When I found out about Saint Mary’s dual degree program, I was excited to discover a way to study both math and engineering. Upon taking the intro to engineering class, I discovered computer science and I could not be happier with my decision. I love the problem solving, logic, and puzzles that computer science challenges me with everyday. I hope to use my degrees to work as a software engineer in the entertainment industry.

I’ve lived in Grand Rapids, Michigan my entire life except for two summers for internships. In the summer of 2016 was an IT intern at AbbVie in North Chicago, Illinois. I worked for the global business analytics group where I created dashboards for bug tracking, tested dashboards, and reengineered the distribution of dashboards to better classify data. In the summer of 2017 I was a Software Development Engineering Intern at Amazon in Seattle Washington. I worked for the Amazon Education team and built an offline mode for children’s reading app and worked on my project management skills.

My hobbies include field hockey, skiing, and watching movies. I also enjoy doing different kinds of puzzles. I am interested in computer graphics, animation, and virtual reality.

I hope in this class to gain a better understanding of some of the hot topics in computer science by discussing the different sides to certain topics and understanding other people’s stances on big issues.

To me, one of the most pressing ethical and moral issues in computer science today is how we handle AI. As computer scientists we must understand that our actions have huge consequences. We are often on a quest to develop the coolest and most exciting new technologies, but we often do not stop to think what negative ramifications these new technologies could have. We do not check, double check and triple check our work we leave for bad people to exploit errors and use our technology for bad. In AI, we leave room for allowing people to teach computers negative qualities and bad things. We are creating technology that if not set up correctly can be used for evil.

One topic that I am very passionate about and hope we discuss in class is women in computing and encouraging women to pursue computer science, along with encouraging men to create a welcoming environment for women. I think tackling the “brogrammer” culture is a huge step that needs to be made.