Reading 01: “But I worked hard to get here!”

Q: From the readings and from your experience, is the technology industry a meritocracy (what does that actually mean)? If it is, then is that a good thing or a bad thing? If it is not, should it try to be?


A: The amount of times I’ve heard the phrase, “but I’ve worked so hard to get here!”, has probably desensitized me from its impact. It’s not that it isn’t genuine nor is it filled with malicious or sarcastic intent. Instead it usually is quite the opposite, filled with compassion and authenticity, but that’s also where the problem lies in considering the technology industry a meritocracy lies.

In the article, “The Capitol of Meritocracy is Silicon Valley, Not Wall Street” by Timothy B. Lee, the main basis behind the opinion that the technology industry is indeed a meritocracy was the distinction between legitimate criteria and fake criteria of merit. While Lee compares the Ivy League and Wall Street’s use of SAT scores and the status of the Ivy League itself to Silicon Valley’s pure criteria of the ability to make great software, I think that naively thinking that software engineering as pure criteria can be dangerous. Just like the same logical fallacy of the very same introductory statement made up above, it’s based off of ignoring that a lot of what’s here and what’s possible today has a foundation built from the many people in the past, and that a lot of success is also circumstantial and luck.

A solid foundation sets up the possibility of hard work paying off for whatever goal is needed or wanted to be achieved. I don’t think many people in this class would have exposure to other’s experiences where they do indeed work hard, day and night, but never see the fruition of their work. If one is never exposed to that sort of experience, then the view of the industry being a meritocracy becomes even more established. For example, a person in high economic status will have more potential for opportunity, more chances at meeting the right people, and more time to develop skills needed than a kid in low economic status whose primary concerns center around surviving than living. I think the time that one is exposed to technology matters too, such as whether it began in college (if college is even presented as an affordable opportunity), in high school that had an AP Computer Science class, or even at a young age where a family could afford a computer or something of the sort to experiment and become familiar with. A journey laden with concrete bridges certainly seems more likely to stay stable than an old wooden rickety one.

In the article, “Why hiring the ‘best’ people produces the least creative results” by Scott E. Page, he states that there is no metric for measuring one’s skill in development, and that trying to measure that is an impossible task. It’s true because usually the needs that need to be met aren’t solely going to be measured by one piece of criteria anyway. It’s also true that breakthroughs, which is what the industry needs and wants, don’t happen from staying in one mindset or background or frame of thought. And that’s brought by different backgrounds, instead of measuring people by one standard.

Hard work does indeed matter, it can make and be the difference between skill in developers in the industry with its ever evolving challenges and changes. So I’m not dismissing the fact that hard work is needed to actually dive in and understand these topics in the technology industry in order to enter the workforce, but I’m not going to dismiss the fact that there are more barriers to entry than one might think to enter it in the first place.

Reading 00 Pt2: Programming is Magical, but not a Super-Power

Q: Is programming a super-power? Why or why not? What are the implications if it is (and what is your power)?

————————————————————————————–

A: “The programmers of tomorrow are the wizards of the future”, said the founder of Valve, Gabe Newell, in a YouTube video labelled, “What Most Schools Don’t Teach”. I remember watching this video before deciding to switch my major from Chemical Engineering to Computer Science a few years ago. I remember resonating with the hype of creating a simple Hello World program, and thinking that if these amazing people in that video initially came from a humble start, that I could do it too. But even with these recent pushes of hyping up working in technology, it’s misleading in terms of it being a smooth journey, and I don’t think that it is indeed a super-power.

Don’t get me wrong, I do think programming is something magical, but to compare coding to the abilities of the heroes of Marvel or DC universes, may seem a bit farfetched to both non-programmers and programmers, and maybe that’s because those super-powers are portrayed as something inherent, or innate in the protagonist. However, programming, has created almost magical-like properties in its advancements. Programming has created new needs, new products, and new ways to do all things imaginable. As an example, maybe 20 or so years ago, one couldn’t imagine talking to whoever or being wherever in the universe in the span of seconds, yet the instant communication available to all, the space tech that lets humanity explore outside of its home planet, and the transportation that exists today make it viable! I do think as this trend continues, the analogy comparing super-powers and programming may be closer than ever as more impossible things continue to become possible.

But programming is still not a super-power. Rather it’s something that’s been built on the backs of many people, and it continues to be handed down so that programming now becomes available to use to anyone. Just as in the reading “To Serve Man, with Software”, it states “we collectively advance the whole of programming for everyone”. So rather than blasting fire or shooting laser beams from just one person, programming is something that’s created by and available to everyone. Yet even though it’s built on the work of programmers, its feats are attributed to very few people that represent that product. It’s parallel to the fact that it’s easier to remember the main figurehead like in superhero movies where only the superheroes / actors are remembered and no one wants to stick around for the end credits. Yet, those people had everything to do with that final product, and just like coding, never see that recognition or daylight (which also in turn, blame to be unseen from as well).

Programming is also a bit over-glorified. People tend to forget the frustrating parts of it as well, as who would want to advertise something as sitting at a computer possibly staring at a huge codebase that no one knows how it works (with no documentation) or possibly just ripping your hair out and questioning your life’s existence only to realize that your error was a simple syntax mistake.

So just because programming is not a super-power, doesn’t mean its impact requires a lot of responsibility. Just like any advancement, its use needs to be ethically defined and we as programmers as responsible for what we make as well as what it’ll be used for. Great power can’t have ethically complacent, lazy programmers.

 

Reading 00 Pt1: Classic ND Introduction

In your first blog post, please write a short introduction to who you are, what your interests are, why you are studying Computer Science (or whatever your major is), and what you hope to get out of this class.

Additionally, in your opinion, what are the most pressing ethical and moral issues facing computer scientists and engineers? Which ones are you particularly interested in discussing this semester?

______________________________________________________________

To introduce myself, my name is Paul Kwak and my interests include game development as well as music production. I’m studying Computer Science because I think it’s a necessity to have in the future as well as it provides the most interesting fields to explore and puzzles to solve. I hope to be uncomfortable in this class: I want to hear opinions on difficult topics, and I want to listen and discuss views that aren’t quite the norm, or views that are the norm but may not be mine.

During my time in Silicon Valley, I think the most apparent issues were autonomous vehicles and privacy. Hilariously enough, there’s also an issue with companies offering free food to employees, as apparently it has caused major impact in the Valley’s economy. I would like to discuss the consequences of autonomous vehicles and particularly the impact it will have on jobs.

Overall, I hope this class is full of debate that make people uncomfortable but also realize that it’s a safe and academic place to share these opinions. When we enter the industry it’ll make us realize that we shouldn’t be so complacent in ethics in the industry.