Net Neutrality

I have heard the term “net neutrality” many times but never fully understood what it represented. For readers in the same boat as I was, net neutrality is the idea that companies which provide consumers with access/connection to the internet should not discriminate based on the sites we choose to visit. The clearest example, in my opinion, is a hypothetical situation where Comcast limits Xfinity wifi subscribers’ connection to content providers like Netflix who compete with the Comcast subsidiary, NBCUniversal. This example really brought me back to the days where my big brother would keep a toy from me simply because he didn’t want me to have it. Obviously, that is just not cool, but should my parents (the FCC of my analogy) have established a rule that my brother could no longer do that? Or, would it have been more effective to have provided me access to a bunch of other toys providing the same function, thus making my brother’s actions harmful only to himself resulting in an unhappy brother (consumer) who could just switch to another toy and be content?

I have always been a defender of capitalism and I am typically not in favor of big government, so I prefer the latter scenario. While I support the idea and noble intentions of the FCC’s attempts to enforce net neutrality, I agree with Jeffrey Dorman’s point of view that more choices would be more effective than more regulations. A rule stating “don’t do that” will not be any more effective in preventing Comcast from justifying its actions than my parents scolding my brother for withholding toys. One thing that will certainly stop Comcast from being selfish is the loss of customers. I think I can speak for most consumers and say that when faced with the decision between two Internet Service Providers (ISPs), if my ISP noticeably restricts my Netflix (or comparable content provider) stream quality and a competitor exists that would not, then you can count on me to switch providers. I think there exists an attraction to creating legislation which explicitly says a company cannot do something because the document can be held and referenced. However, I believe the less attractive option of letting natural laws of capitalism take over would be much more effective.

Supporting my belief are the weaknesses of the Open Internet Order highlighted in an article published by the Electronic Frontier Foundation, “Why the FCC Can’t Actually Save Net Neutrality.” To start, the FCC claims to have ancillary authority which may seem fine for now, but what happens when they decide to enforce policies that are not as widely accepted as net neutrality? Also, the law included exceptions which enables the FCC to cooperate with law enforcement agencies upon request. I find this troubling that a federal organization can bypass its own order if a request is made by a different federal organization. Finally, how can the public check the power of the FCC that has proclaimed ancillary authority over the internet? Consumers would then be faced with powerful media conglomerates that act as ISPs and a federal regulatory agency that proceeds unchecked by the public.

To conclude, I would like to acknowledge that I do not believe there is a straightforward solution to the enforcement of net neutrality. Also, I consider myself a defender of net neutrality, but I do not agree with the current strategies in place to protect this idea. I believe that competition is the best way to ensure providers are held accountable for their decisions and consumers are positioned to find the best available package to fit their needs.



IMO: Interviews

Screen Shot 2016-02-16 at 4.04.10 PM

I can’t speak for everyone else, but I think I have a unique opinion towards interviews. My opinions really began to form when I interview for the global engineering firms at my freshman year at Notre Dame. I pretty much brought nothing to the table, and it was clear to me all of my interviewers know that. There decision to interview me was probably more of a professional courtesy to my connection in the industry who recommended me, but I appreciated it nonetheless. Experience is key to mastering interviews (not that I am a master) and that initial experience helped me moving forward.

The most important part of Matt and I’s interview advice is the notes on preparation. Our comments were very different and I think that is the most important takeaway. There is no interview preparation book that applies to everyone. Some students cracked the coding interview in their high school education, so they are way ahead of the curve and probably need to practice answering behavioral questions. Some students coded a little in high school, but succeeded as social butterflies and developed useful communication skills, so they probably need to practice answering technical questions. Some students have no experience coding at all (besides MATLAB), so they might not be able to crack the coding interview even if they tried. So what’s the answer? If you’re an engineer, use your problem solving skills to develop the best solution for interview preparation. I think that each student’s interview preparation can be viewed as a unique engineering problem. Examine yourself and determine the best guide to help you prepare for an upcoming interview.

My personal guide went roughly like this:

  1. Brush up on basic syntax/structures
  2. Have confidence you can solve weed out questions
  3. Know that technical questions above your head are worth attempting, but you can always be honest about your lack of knowledge of a topic
  4. Brainstorm memories that can apply to general behavioral memories
  5. Go to sleep on time

I think the most important part of my guide is number 3, it is completely okay to admit when you don’t know something. The first time I was flown out to a company’s offices, I did three consecutive interviews. During those interviews, I probably came across four or five questions that related to subjects I never studied. I made the interviewer aware, but still asked for a chance to solve it based on the general knowledge I had of programming. Typically, the interviewer and I ended up working through the problem together until the answer made sense to me. Flying back to ND, I assumed there was no chance they would offer me a job, but that ended up being my first internship.

I wish I would have known to be confident in my own technical skills. Naturally, I would compare myself to my peers in computer science. In retrospect, that was a useless practice because we all came from different backgrounds. Fortunately, companies are pretty good at determining a candidate’s ability to learn, not just what they already know. From my experience, what I already knew was actually less important than my strength of being able to pickup new technologies quickly. I hope that future students at Notre Dame who find themselves in my shoes will have confidence in their current skills and faith in their ability to learn.