Why Are We Even Doing All This? A Reflection from the Tech Community

In the tech world—especially in AI and open source communities—we often find ourselves immersed in iterating on models, polishing products, and integrating tools. But every once in a while, a simple question breaks the momentum: "Why are we even doing all this?"

This question appeared in a Hacker News discussion. No lengthy essay attached, no specific project referenced—just a single question that cuts straight to the core. It resonated because it touches a deep, shared confusion among technologists: beneath the daily grind of building and optimizing, are we clear about where we're ultimately trying to go?

When "How" Drowns Out "Why"

The tech community has a natural bias: it rewards concrete solutions over abstract questioning. A clever library, a successful deployment, a performance improvement percentage—these earn upvotes and retweets. By contrast, "why do we need this" is often dismissed as empty talk.

This bias is especially pronounced in AI. Model size, benchmark scores, inference speed, API call costs—these metrics form the coordinate system of daily conversation. But metrics themselves don't answer questions of purpose. When an entire industry revolves around "capability" as its axis, the sense of direction easily blurs.

That question on HN is like a pause button. It doesn't deny technological progress—it reminds us that technology is a means, not an end. If the means keep upgrading while the end remains vacant, then so-called progress may just be spinning in place.

Hacker News (HN) is a tech community founded by Y Combinator in 2007, known for its high signal-to-noise discussions, with a user base spanning founders, engineers, and researchers. Its voting mechanism tends to reward verifiable technical solutions and first-hand experience rather than abstract debate, so when a brief question makes it to the front page, it often means it has struck a long-unspoken consensus in the community. HN's discussion threads are also famous for "one sentence sparking long chains of in-depth replies"—a structure that allows meta-questions to compete on the same stage as concrete technical details.

The Tension Between Efficiency Worship and Loss of Meaning

Over the past decade, the tech narrative has been dominated by "efficiency." Do more with fewer resources, reach results via shorter paths, replace manual work with automated processes. Efficiency itself isn't wrong—but when efficiency becomes the only yardstick, values that can't be quantified—curiosity, the joy of exploration, community trust, genuine help to people—get pushed out of view.

The open source community exemplifies this tension particularly well. Many developers pour substantial spare time into maintaining projects, and the returns they get are often not money but recognition, learning, and a sense of connection. Evaluated purely through an efficiency lens, much open source work is "not worth it." But it's precisely these "not worth it" efforts that constitute the public infrastructure of the tech ecosystem.

When someone asks "why are we even doing all this," they may not be seeking a standard answer—they may be inviting the community to re-examine assumptions that have been taken for granted.

Open source public infrastructure refers to open source projects that are widely depended upon but often maintained by a handful of volunteers or small teams—such as OpenSSL, cURL, log4j, and others. They typically lack stable funding and staffing yet underpin critical functions of commercial software. When the log4j vulnerability erupted in 2021, maintainers patched it in their spare time—an event that brought "not worth it from an efficiency standpoint" open source work into public view. The value of these projects is hard to measure by short-term ROI, yet they form the trust foundation of the entire tech ecosystem.

From Question Back to Action: A Few Possible Answers

Faced with this question, community reactions typically split. Some consider it too vague to help solve concrete problems; others believe it's precisely this kind of meta-question that prevents technology from becoming alienated.

If we were to offer a few possible answers, perhaps they could be framed like this:

To understand the world. Technology is a way of knowing. Writing code, training models, designing systems—all are acts of modeling reality. Understanding has value in itself, even without immediate application.

To connect people. The ultimate significance of many tech projects isn't in the code but in the collaboration, communication, and community it enables. Open source, documentation, tutorials, discussion forums—all are vehicles for human connection.

To give more people choices. Good tools lower barriers, enabling more people to create, express, and solve problems. That in itself is a form of empowerment.

To become a better version of yourself along the way. For individuals, tech practice is a way of cultivating patience, logic, and creativity. Meaning isn't necessarily at the endpoint—it may be along the path.

These answers aren't mutually exclusive, nor are they complete. But they remind us: purpose isn't discovered—it's chosen. In the absence of externally given meaning, communities and individuals need to actively construct their own answers.

Technological alienation borrows from Marx's concept of "alienation." In a tech context, it refers to tools created by humans coming to dominate humans, where means obscure ends. For example, metrics shift from measurement tools to pursued goals; engineers optimize for KPIs and forget user needs; algorithmic recommendations amplify extreme content for the sake of dwell time. The Frankfurt School's critique of instrumental rationality is also frequently cited: when efficiency becomes the sole standard, value rationality is marginalized. Asking "why do all this" is precisely a daily immunization against this tendency toward alienation.

The Ability to Keep Asking Matters More Than Finding Answers

The tech industry is accustomed to solving problems. But some questions aren't meant to be solved—they're meant to keep us lucid. "Why are we even doing all this" belongs to that category.

It shouldn't only surface when we're exhausted or lost—it should be part of daily practice. Before launching every new project, before every feature iteration, before every pursuit of a metric improvement, we can take a few seconds to ask: What purpose does this serve? Who benefits? What's the cost?

That HN discussion offered no conclusion, nor does it need one. Its value lies in making the question visible. In an environment that rewards action and output, allowing yourself to pause and question is itself a form of resistance.

Perhaps what truly matters isn't finding the ultimate answer to "all this," but maintaining the courage to keep asking—and to keep adjusting course through the asking. Technology is an extension of humanity, and humanity's meaning has never been defined by technology.

One-line Summary

Beyond efficiency and metrics, the tech community needs to re-ask: "Why are we even doing all this?"

Paragraph Summary

Starting from a Hacker News post asking "Why are we even doing all this?", the article points out that the tech community naturally rewards concrete solutions while dismissing questions of purpose—especially in AI, where model size and benchmark scores replace a sense of direction. Efficiency worship further squeezes out unquantifiable values like curiosity and community trust, with open source public infrastructure as a prime example. The article outlines four possible answers: to understand the world, to connect people, to empower more people, and to become a better version of oneself along the way—emphasizing that meaning isn't discovered but chosen and constructed. The ultimate conclusion: the ability to keep asking matters more than finding the ultimate answer.