Whether to consider Edward Snowden a hero or traitor depends on which perspective are we taking while making such a judgement. From the standpoint of American government, Snowden could be considered as a traitor. He disclosed over a million confidential documents from the NSA’s system. Which not only put the government under censure of other governments who are related, but also posed America’s national security under massive potential danger. Because most of the over a million files from NSA’s surveillance system, such as the methods of signals intelligence, served for protecting the nation’s security. However, from a more personal perspective, and giving a regard to every normal citizen’s daily life, Snowden might be considered more as a hero. Most of citizens were either unaware of, or intentionally avoid to thinking about the over intruding that government made into our private lives. Snowden as an individual, knowing what judgement he was facing, and what power he was fighting against, bravely stood out and informed the American public about serious privacy issue the country was carrying.
Further, the morality of Snowden’s action is also disputable. Considering his motivation, at least for those he stated, if we buy it, what he did might be rebellion to moral norms. Through a lot of public press, Snowden tried to explained his motivation from a positive approach. The Wire article states Snowden’s thought on why he considered the disclosure of the documents was for justice and public morality. It reads, “He realized … that the only way to cure the abuses of the government was to expose them. But Snowden didn’t have a Senate committee at his disposal or the power of congressional subpoena. He’d have to carry out his mission covertly, just as he’d been trained. ” Besides, the article Edward Snowden’s Impact also explains what drove Snowden for his motives. In the article, Snowden says that “the law doesn’t defend us; we defend the law. And when it becomes contrary to our morals, we have both the right and the responsibility to rebalance it towards just ends.” However, despite initial purpose for leaking the documents, the way Snowden receives the information, and the consequences his action brought to the public and nation made his motives less ethical. Snowden was able to access to millions of documents for NSA on their surveillance programs while working at CIA and Booz Allen Hamilton. With the advantage of his work, he illegally used a web scraper based on keywords to grabbe countless amount of information. Going off the working regulation and confidential bondence to get classified information is not what expected for a moral employee. Moreover, without carrying a proper consideration and analysis of information, he simply gave all information to public presses. This motive result in a leak of information that beyond those relevant to government surveillance on US citizens, and secrets that citizens might not really deserve to know. The Guardian and other newspapers published how the NSA tapping into online communication in the US, spies gathering information on other countries, and intricate details about how these US agencies were able to this. From government’s perspective, Snowden not only destroyed their surveillance system, but also leaked the highest classified secrete to public, which made national security and defensive system under potential attack by other countries. But from the US citizen’s perspective, Snowden could be viewed as a warrior who took the lead to question the government's improper surveillance, and help citizens gain an awareness on privacy issues
0 评论
The interview guide constructed by our group introduced a lot of helpful information to me. Based on my experience, I found the part “anything else you wish you knew before went through the whole process” most important and useful to me. This part of information reminds me of some essential aspects of interviews that I did not pay attention to or intentionally ignored. With my experiences during undergraduate education and current graduate study, I thought I had known well about the whole internship and interview processes. And I was confident about my familiarity with interview procedures as well as every detail in either the conversational or technical testing process. Not until I read my group’s interview guide did I realized how unprepared was I for either section of future interviews, and how much more could I improve. Previously, I did not consider communication skills as significant for the success of an interview, thinking that excellence in programing knowledge was the only factor that would matter. Besides, I was definitely not very proficient with whiteboard, and did not realize how disadvantageous this weakness could possibly be for my performance during a technical interview. Fortunately, now with the new knowledge and information gained from the guide, I definitely know what was wrong and can get over these weaknesses and do better in future interviews.
As to the best advice obtained from the guide, it is the one that telling me how can I actually negotiate for my benefits. From my previous experience, I usually felt being in a relatively passive position in the relationship with employers, and was therefore afraid to ask for anything that was not originally scheduled to offer. Such concern indeed once resulted in an unfair payment for work I had done. Knowing that I could actively seek for the best “price” to sell my skills, I think I will be able to find better job offers for my career development in the future. But, in fact, besides the information learned from the guide, I know it is ND’s CSE that grants me the ability and power to seek for the future career. Even with a regard to today’s competitive and highly demanding job hunting process, I still think current ND CSE program is already doing well in preparing and supporting us for our career development. Take the graduate program as an example, course and minimum GPA requirements not only ensure knowledge is acquired adequately, comprehensively and in depth, but also guarantee the learning and practices of professional skills are completed with high quality. Given that our future employers value our professional working abilities more than our interview skills, ND’s CSE program has definitely hit the bull’s eye. Moreover, the program also provides specific career supports such as career consultants, who can help us build a solid and feasible career plans, as well as strong aluminum networks, which can provide us wide connection and valuable referrals. So as long as we fulfill all academic requirements and reach out to career services, I am confident that, we can be well prepared for our future careers with the current CSE program. When should students start preparing for interviews?
Like the old saying goes, “early birds get worms”, we should get our hands on preparing for internships or interviews as early as possible. Let’s look at internships first. When exactly should we start applying for internships? Keep in mind that more working experience is always better than less. So you should better start looking for internships or other job opportunities as soon as you have acquired basic computer science knowledge that is required for technical interviews. However, as students, we may not have enough time for internships during semesters. To make up this disadvantage, we should definitely take a wise use of our long breaks. And summer is usually our best choice. To get a summer intern, first of all, we should know that most tech and IT companies collect applications for summer interns in September and March (MIT UPOP, n.d.). This means, if we want to get an internship that starts in June, we should start preparing during the fall semester. By this way, if we failed at the first attempt, we could gain experience, and be able to have another shot in March. Similarly, we should get ourselves plenty of time to get fully prepared for both general and technical interviews. For computer science internships, there are usually three types of interviews --- the general interview that looks at the student’s overall information and working or practicing experiences; the technical interview, which tests the student’s practical level of coding, algorithms and data structuring skills; and additionally, language interviews, which is set up to quiz about the student’s proficiency in certain languages (Smallman, n.d.). Moreover, companies like Google and Facebook also conduct a team-matching after basic interviews. Even if you have passed all the other interviews, you could still fail at the last stage if you didn’t perform well during this process. Each one of these interviews requires a large amount of advanced efforts and dedication. The earlier we start preparing and planning, the better we will be able to perform, and the more likely we are to get the internship we want. How should students prepare or plan for these interviews? “Practice makes perfect.” For all interviews, the best way to prepare is to practice over and over again. But since the aims of the interviews mentioned above are different, here are some tips for each one exclusively. To prepare and plan for a successful general interview, the first step we should take is to learn about the position we plan to apply for, and the background of the company we will apply with. This helps us understand and figure out what is required for us and what we can provide to satisfy that requirement. Then, we need to prepare a decent resume that clearly demonstrates our capabilities as an eligible and qualified candidate for the job. The resume gives interviewers a preview, and likely, helps them gain a first impression on us even before meet us in person. Generally, a good resume should include the candidate’s name, contact information, education history, work experience, activities or accomplishments and technical/language skills (UNLV Career Service, 2016). Be careful that we may need several versions of resumes highlighting specific work experiences or skills when applying for different jobs. Next, get prepared for interview questions. In most cases, interviewers will ask questions based on your resume information, and also intend to learn about your strengths and weaknesses, as well as why and how you think you would fit the position or the company. Moreover, for computer science students, interviewers may want to know details about projects you have done. Questions about what the projects were about, and how did you participate in those projects might be asked. Making sure to answer these questions clearly and properly is the basis of a successful interview. Lastly, prepare questions for the interviewer. This is the chance for you to learn more about the company. But it may not be appropriate to ask about things like salaries. Good questions may be ones like “could you describe a typical day of the position?” Or “what draws you to the company?”. As to technical or language interviews, they evaluate your abilities to tackle practical problems, and how familiar or professional you are with your knowledge. Easier questions for such interviews may include problems about loops, lists or strings, while harder questions may focus more on specific data structures. According to particular professional arena, Linux Engineer questions, .NET questions and OOP design type questions may be tested (Hein, 2013). So it is important and necessary to get familiar with the job description. Items listed on the description can give you a navigation for what aspect of knowledge you should focus on, and how should you present your ability to fit the needs of the position (Hein, 2013). In addition, be clear and familiar with core principles and basics. Also, understand aspects of prospective programming languages. Do not satisfy with fundamental knowledge. Dig deeper and acquire more expansive skills. Because questions may vary from giving simple broad stroke to more advanced tasks (Hein, 2013). An easy but efficient way to practice is to find sample technical questions, and practice coding or other related skills with them. They will definitely prepare you better with the interview. Anything else you wish you knew before you went through the whole process? The first extra note is that, despite the fact that our job is dealing with computers and codes, we should do well in interpersonal communication as well. Because this is, at least, important for interviews, where you are selling yourself to the company. Secondly, get comfortable with coding on a whiteboard. Although this is not required at all companies, but it is indeed a common practice asked during technical interviews. Thirdly, behave in a good manner and dress properly. Interviewers would appreciate it if you initiate the greeting, and introduce your name, with a firm handshake, as soon as you get the chance to speak to them. Also, although we do not need to be in suit-and-tie for all the time while working, we are expected to look formal for interviews. A professional-look outfit shows your attitude and proficiency. This can of course vary between companies; it can be weird to wear a suit to an interview at a company where the programmers wear jeans every day. So if you can get an idea about what company culture is like before, you may have a better idea of what people wear at the office, and dress accordingly for your interview. Last but not the least, bring extra copies of your resume. You never know what situations you may encounter and whom you may meet. Getting ready to introduce and present yourself at all time will give you more chances to success What resources should students consider? Books? Career Services? Student groups? Students should consider visiting the career center at Notre Dame. Specifically, there is a career advisor concentrate advising careers in Engineering. He introduces many companies and small ventures, where ND alumnus are currently working. Although there are many internship opportunities with no pay, the advisor helps a student to get funded from the university while doing the internship. Because career in computer science can be varied such as software, hardware, IT security, IT business, consulting, and others, it will be nice to know what your interest is, and ask an advisor to introduce companies that match your interest. Also networking or getting a mentor of CSE alumni will be helpful for your career. Because the career center has all the contact information and company information of graduates, they also connect graduates to us so that we could ask them directly about the job environment, interview, application review, or other support. Especially for students who are interested in working in start ups, it will be beneficial to get the contact information of alumni in startups, because start-up and venture companies are often more selective when hiring or providing internships. As ND is mostly known for business and many students are interested in getting jobs at business or consulting fields, there are actually not as many engineering jobs on Go Irish compared to business job positions. Therefore, what the career center recommends students to get resources is going into websites like ‘LinkedIn’. If students want to focus on engineering jobs or technology companies, angel.co is another option that is recommended. It is very simple. If you upload your resume and desired career option, the website generates your information and provide contacts or job positions that are matched to them. Angel.co is specifically known for providing engineering jobs from small start up industries to big companies like Airbnb, Uber, and Fitbit. As the career center describes, using the ND networks will be the most efficient way to be successful in career, especially with CSE major students. Therefore, visiting the career center and getting networks with graduates will be the best option. But before that, it is always recommended to research on many companies and fields, so that students could know where they want to start. To get this type of resource, students should often visit IT news websites or blogs, campus recruiting, and contacting with the HR department of companies. What extracurricular activities should students consider? Extracurricular activities are differently recommended to the student’s field of interest. For students interested in software engineering, students can join the computer club in campus. Because the purpose of the club is to promote the interest in computer science, students and staff share information and provide tutorials for students to enhance their engineering skills. By practicing and discussing about computer engineering and skills, students will get advantages both in academics and in careers. The computer club and other clubs often feature talks by people in the tech industry, which are helpful for learning about opportunities and networking. For students interested in IT management, there is also a IT management club in campus. Students here also share information on IT industry, career, case studies and news, so that students can prepare for their careers outside the class. Students who are interested in case competition or IT start-up competition, are also welcome to join the club and they can create the teams for challenges. Other than joining clubs in ND campus, it is helpful for students to participate in school events, companies’ events, and events in major department, such as app challenge, Accenture case competition, and McCloskey business plan competition. In this way, students will have more opportunities to meet new people, make great experience, and get new skills directly for their careers. Especially if you don’t do any of these things, it is extremely helpful to code in your free time. Many interviewers will ask you about your “side project” referring to any coding you’re doing that is not required by class. Companies want to see that you’re interested in programming outside of class requirements, so it is good to have some side project to talk about. It doesn’t have to be a technically complex project; interviewers aren’t expecting you to solve world hunger with code in your free time. Even if you’re just making a simple game, it is helpful to be able to talk about it in an interview. How can students take advantage of networking and alumni relationships? You may have heard people talk about Notre Dame’s strong alumni network and how helpful it is in finding job opportunities and making connections. Indeed, Notre Dame has an extensive alumni base spread across cities all around the U.S. You may be surprised to find that your dream company is full of Domers! Although the alumni network is not quite as significant for computer science students as it is for business majors, it can still be very helpful in getting a job. Networking is a helpful skill that some people are naturally good at, while others are not. For some people, conversation comes easily, and they have no trouble making meaningful conversation with someone they just me. For others (like me), networking was an awkward process in which I had to force myself to talk to someone I didn’t know and act way more interested in their company or job position than I actually was. If you are of the second group, I’m sorry to say that you’re still going to have to do it in the future whether you like it or not. But don’t worry, although it may be uncomfortable, it isn’t too hard. When talking to a recruiter or employee, the main thing you want is to be memorable. At a career fair or recruiting event, the employee will be talking to tons of students in succession, and when all the students are computer science majors who are taking all the same questions, it can be tough to effectively stand out. In my experience, one of the best way to do this is to ask interesting questions. Don’t just ask the generic questions everyone asks like “What kinds of projects do you work on?” Actually, you should ask these questions, because you’re probably interested in the answers, but ask some more specific questions about the job too. Then, it’ll be easier for them to remember you later if you bring up the conversation. After you talk to them, be sure to get their contact information, and email them later that day. It may seem like you’re being annoying, but you come off as way more interested, and it’s better to stand out for being a little annoying than to not stand out at all. How should students approach negotiations or contracts? So, you got an offer. Congratulations! Many students are just happy to get to this point, as they should be, and immediately accept the offer. However, especially for full-time offers, it is important to evaluate all parts of the offer before making a decision. Don’t just think about the pay, too; consider healthcare, stock options, and other benefits. If you have another offer on the table, compare all aspects of both offers and determine which you prefer. Though it’s not the only thing, the pay rate is very important, which brings us to negotiation. Regarding this, it’s important to remember: you can always ask for more money. You might not get it, but the worst thing that could happen is that the hiring company says no, and you could work your way into a better package. Negotiation can be difficult, because you don’t want to come off as arrogant or selfish. So it’s important to ask in the right way and use polite language. Make sure to state clearly your reasons for wanting more money, whether they are because you think you’re qualified, because you have a comparative offer for more money, or because you believe the offer is lower than comparative offers in the same city. If you do have an outstanding offer from someone else, it may be good to mention that. It gives you some negotiation leverage, and if the company wants you badly enough, they’ll make you a better offer. One tip I’ve been told is to never start off by naming an exact number for the pay you want. It is better to just ask if it is possible for more money, and have the company throw out the first number. Sometimes, their number may be higher than what you wanted anyway, and you got yourself more money for doing essentially nothing. Some companies won’t allow you to negotiate your offer. That’s okay, don’t get discouraged by this. If you still want to work for the company anyway, you can accept your offer, or if you have a better one elsewhere (or think you can get one), you can decline it. From the readings we know that Therac-25 was a radiation therapy machine designed and produced by Atomic Energy of Canada Limited (AECL). It offered therapies with either direct electron beams or megavolt X-ray. Such therapies were designed to bring the least harm to patients while destroying tumors. Due to flawed designs and poor management, Therac-25 caused four deaths and two severe injuries with massively overdosed radiation in 1985 and 1987. Tragedies rarely happen overnight, and problems hardly occur out of a single cause. The multiple accidents of Therac-25 resulted not from one fatal mistake or flaw, but from a series of interrelated issues. The primary reason for the recurring medical accidents was conclusions drawn without efficient investigation or sufficient evidence. Concerning the case in Hamilton, Ontario, Canada, micro switches was the main cause, while numbers of other factors could be possible factors. Another reason was the lack of management. Between the first and the last incidence, AECL never considered building up an efficient managing and reporting system. As a result, Issues were not adequately discussed, and problems were not promptly solved. If AECL had been doing better in management, they might have been able to avoid the latter losses. The third problem was the blind trust on software. Software doesn’t wear out like hardware, but it could still have flaws that are hard to detect and eliminate. It was unwise to remove the hardware interlock device from Therac-25, especially when software takes almost all of the functional responsibilities for the machine. Therac-25’s design was partially taken from earlier products, the Therac-6 and -20. Since no accidents were recorded for those two devices, AECL did not conduct any software diagnosis for Therac-25’s first safety analysis, despite the fact that previous machines were based on hardware while Therac-25 relied hugely on software. Even after the problem occurred, AECL only focused on examining the device. Analyzing software should not have been overlooked, and it is vital to avoid any single hitch for a qualified program design. In other words, no component in a system should take up so much duty that it could lead to fatal consequences once crashed. Also, Therac-25 lacked an efficient and proper responding system. The patient’s response was the only reference to estimate the radiation range. Therac-25 merely relied on the operator to detect and deal with problems during the treatment. There was no independent institute to instruct or monitor the operation; the device itself was not able to detect overdosed radiation. The operating screen could show the radiation range, but the data was not accurate because the treatment room could not control high-density electron beams. Similar to what happened in 1986, even when the machine was already releasing over-ranges radiation, the operator might not be able to notice it immediately. The challenge to develop a safety-critical system is to find a qualified standard and to take as many potential operating environment and situations as possible into account. Also, it is also hard to develop a comprehensive responding system when different problems occur. Software developers should always know that fixing one bug does not mean long term safety. Software bugs always come up one after another. And no matter how perfect a safety system looks like, the best way to ensure long-run security is to keep monitoring and improving the program. I believe that manufacturers are most responsible for the safety of medical equipment because they know the machine better than anyone else. However, technicians and operators of medical equipment are also responsible. As they have day-to-day contact with the machine, they should be aware of any quirks or inconsistencies. No matter what the public opinion about the lack of diversity in the field of computer science is, we have to admit that lack of the diversity is a problem. The reading “Google finally discloses its diversity record, and it's not good” shows that in Google’s workforce, there are 60% White and 34% Asian working in technology department, which means no more than 6% people are nonWhite and non-Asia. Additionally, 83% of the workers in technology department are men. I knew there was a gender gap, but I never thought it was that huge. Admittedly, the lack of diversity does exist, but the question is: does this matter?
Firstly, the gender gap: 83% of the workers in technology department are men. Some people may claim there is already a gender imbalance in the STEM major students, but the reading “Why the STEM gender gap is overblown” shows that there is no huge gender difference in the computer science major. Moreover, some people may think that women just don’t have the ability to succeed in the “hard” sciences, computer science, or engineering. Some have even argued that women are not smart enough for these fields. However, according to the reading, “ The fact is that men and women score equivalently on tests of raw IQ, with some studies showing women scoring slightly higher. When it comes to mathematics—a core requirement for science and engineering—women score on average only 32 points lower than men on the SAT— a mere 3 percent difference.” I believe that woman and man are equally capable of doing the STEM work, but why there are huge differences between man and woman in computer science? The reading mentions “Man earn more and they believe they worth more and woman agree.” I think the atmosphere and how people think is one cause. Even in some field, such as nursing, a traditionally female-dominated profession, the gender gap is also a big problem: the average female nurse earned $51,100, 16 percent less than the $60,700 earned by the average man in the same job. The writer also claims that “ The fact that women undervalue themselves (and by extension, the work they do).”Once people doubt their ability, they lose aspiration to do the work well. People have to trust themselves and believe they are equally capable doing the same work like male and majority,and this is exactly why the lack of diversity matters in the STEM field: to boost their confidence and to activate the most ability of them. I believe it is necessary to have some programs encouraging female and minority to join the computer science field, but these programs should focus on how to give them confidence. I don’t think it is fair for the rest that more opportunities are given to the female and minority just for the sake of adding diversity. Isn’t that a kind of discrimination some way: showing that they are worse than male and minority and they need extra attention and help in the working field. Technology companies only hire the best people, especially for big company like Google, Apple, FaceBook; these companies need the best people and they would not want to lower the standard just to mitigate the lack of diversity. I think for female and minority there are not barriers for them, the only problem that they need to get over it is themselves. The main controversy in the H-1B Visa program is giving jobs in the United States to citizens vs having these jobs taken by more qualified foreigners. According to “2016 H1B visa report”, most of the top sponsors are technology companies and financial companies, where the average salary is usually higher than 80k. Moreover, University of California, Davis Professor Norman Matloff, one of the fiercest critics of the high-skilled H1-B visa program stated in an interview that: “Employers prefer to hire younger, thus cheaper, H-1Bs instead of older, thus more expensive, Americans.” In terms of patents and academic work, he found, immigrants tend to be on par with natives, busting the so-called “best and brightest” myth. On the other hand, in order to protect American workers, he argues, visas should only be granted to select immigrants because the article states “Roughly twice as many American undergraduates earn degrees in science, technology, engineering, and math disciplines than go on to work in those fields.” It means there are enough US citizens who are able to work in technology company. From my perspective, it is not that enough to convince me that it means people should have the limitation for the immigrants to get the job. Those techology companies only hire the best people in the field: everyone has the same opportunity no matter where they are from. Moreover, there are some students who do not want to work in the technology although there are STEM major. So, We can not simple using there are many American undergraduates who earn degrees in STEM major to argue we should hire less immigrants.
I favor the idea to expand the use of H-1B visa. As H-1Bis such a controversial topic, some people will argue that the U.S. government and U.S. companies should take care of the Americans first, by providing job opportunities. However, I believe that the government is doing a great job by providing education to the U.S. citizens: they enjoy low tuition if they go to a in-State university and they are offered financial aids. Moreover, the companies provide work opportunities to every, and of course, including the citizens. If they are capable of doing the work, they will be hired. According to CNN, there is overwhelming demand from American companies -- both large and small -- for educated, skilled foreign workers to fill jobs in computer programming, coding, medicine and information technology. Reasonably, more and more foreigner are being hired. As an international student in University of Notre Dame, I hope to stay in the U.S. to work, as the U.S. has the best computer science companies. They not only provide a good salary, but more importantly, offer great experience with research and technology development. Those experience will help me to be a better programmer no matter where I end up working in the long term. As a result, I will be greatly influenced by the situation of H-1B visa. Personally, I think I am experiencing a heavier pressure than my fellow American classmates: I not only have to maintain an academic ability as high as, if not more than, my other friends, I also have to be lucky, since H-1B is a lottery system. Once I don’t get it, all my plans will be destroyed. In conclusion, expanding H-1B is good for both the U.S. and the foreign works. Codes of Ethics
My code of ethics highlights the inter-individual relationship between students. As a Notre Dame student, I feel so honored to be in this community and would like to share the this code of ethics with all the CSE students and to work with them to build the better atmosphere. I think the relationship among students should always be one of the most significant part of the ethics, since group project and collaboration play such an important role in their daily study and I believe it is important for Notre Dame student to know more about the code of ethics. New student could easily relate with other students as those guidelines could help one navigate through the group works with the others. Admittedly, no documents are perfect, and I believe there must be weakness in my code of ethics. Every code of ethics cannot perfectly suit for everyone. Firstly, because my code of ethics are built for ND CSE students, it does not cover all the group of people, for example, the programmers who are working in industry. For them, the relationship between customers and employers may be one of the most important parts in their code of ethics. And for us as students, the satisfaction of professor and from ourselves with our intellectual work is more important. To solve the problem, students can learn from their internship to get a better idea of the professional work environment. Moreover, they can ask advice from alumni to get the professional side of the code of ethic which is not covered in the current one. Admittedly, human beings play the major role in the code, and not human-centered codes cannot stand for long.However, putting human in the center also brings problems. I only focused on the inter-individual relationship among students: it all relies on people’s relation and how well people follow. As people tend to follow the majority, who can be wrong from time to time, and they also have flaws in their nature, it might be hard to implement those codes in real life. For some people, the code of ethics might be too idealistic or worthless. However, I believe the code of ethics plays a significant role in our daily life. Every job and work needs a rule to follow, and it is the code of ethics that provides a guideline. It is important to fully understand what role a student should play. For example, as Notre Dame computer science students, although we are mostly just designing computer programs everyday, we need to make sure they are good for the society, because we are not only representing ourselves, but also Notre Dame, and even the entire computer science programmers. As I mentioned before, the code of ethics relies on people’s relation and how well people follow; if everyone knows how to do the right things, it will create a great atmosphere for us as computer science students. As people tend to follow the majority, if everyone stand for right value, people would then follow the right value. In my opinion, besides just following the codes of ethics, we should also encourage other students to follow the code of ethics, and give fair advice when they are lost.The 9 codes that I came up with highlight the inter-individual relationship among students. I believe that the easier to read, the more student will remember and accept. I think the ACM code of Ethics and Professional Conduct might be too much for some people, so I tried to make a shorter version to create a better working atmosphere. |