Source | http://amp.weforum.org
In 2005, the late writer David Foster Wallace delivered a now-famous commencement address. It starts with the story of the fish in water, who spend their lives not even knowing what water is. They are naively unaware of the ocean that permits their existence, and the currents that carry them.
The most important education we can receive, Wallace goes on to explain, “isn’t really about the capacity to think, but rather about the choice of what to think about.” He talks about finding appreciation for the richness of humanity and society. But it is the core concept of meta-cognition, of examining and editing what it is that we choose to contemplate, that has fixated me as someone who works in the tech industry.
As much as code and computation and data can feel as if they are mechanistically neutral, they are not. Technology products and services are built by humans who build their biases and flawed thinking right into those products and services—which in turn shapes human behavior and society, sometimes to a frightening degree. It’s arguable, for example, that online media’s reliance on clickbait journalism, and Facebook’s role in spreading “fake news” or otherwise sensationalized stories influenced the results of the 2016 US presidential election. This criticism is far from outward-facing; it comes from a place of self-reflection.
I studied engineering at Stanford University, and at the time I thought that was all I needed to study. I focused on problem-solving in the technical domain, and learned to see the world through the lens of equations, axioms, and lines of code. I found beauty and elegance in well-formulated optimization problems, tidy mathematical proofs, clever time- and space-efficient algorithms. Humanities classes, by contrast, I felt to be dreary, overwrought exercises in finding meaning where there was none. I dutifully completed my general education requirements in ethical reasoning and global community. But I was dismissive of the idea that there was any real value to be gleaned from the coursework.
Upon graduation, I went off to work as a software engineer at a small startup, Quora, then composed of only four people. Partly as a function of it being my first full-time job, and partly because the company and our product—a question and answer site—was so nascent, I found myself for the first time deeply considering what it was that I was working on, and to what end, and why.