Nematix
Innovation Engineering
 Technology in the Service of Something Larger
Sep 10, 2023 - Last updated on Feb 01, 2026

Technology in the Service of Something Larger

Sagan's Pale Blue Dot is a call for technologists to ask not just what we can build, but whether we should — and who it serves. A thought leadership read.

Look again at that dot. That’s here. That’s home. That’s us. On it everyone you love, everyone you know, everyone you ever heard of, every human being who ever was, lived out their lives. The aggregate of our joy and suffering, thousands of confident religions, ideologies, and economic doctrines, every hunter and forager, every hero and coward, every creator and destroyer of civilization, every king and peasant, every young couple in love, every mother and father, hopeful child, inventor and explorer, every teacher of morals, every corrupt politician, every “superstar,” every “supreme leader,” every saint and sinner in the history of our species lived there — on a mote of dust suspended in a sunbeam.

The Earth is a very small stage in a vast cosmic arena. Think of the rivers of blood spilled by all those generals and emperors so that, in glory and triumph, they could become the momentary masters of a fraction of a dot. Think of the endless cruelties visited by the inhabitants of one corner of this pixel on the scarcely distinguishable inhabitants of some other corner, how frequent their misunderstandings, how eager they are to kill one another, how fervent their hatreds.

Our posturings, our imagined self-importance, the delusion that we have some privileged position in the Universe, are challenged by this point of pale light. Our planet is a lonely speck in the great enveloping cosmic dark. In our obscurity, in all this vastness, there is no hint that help will come from elsewhere to save us from ourselves.

— Carl Sagan, Pale Blue Dot: A Vision of the Human Future in Space (1994)

Sagan wasn’t writing about software. But when we read it as engineers and technologists, it lands differently than it did in 1994.

What Technology Is For

Every generation of engineers inherits a version of the same question: what is all of this actually for? It’s easy to sidestep. You’re busy shipping features, meeting sprint goals, managing infrastructure, closing contracts. The philosophical framing can feel like a luxury reserved for keynote speakers and think-pieces.

But the question doesn’t go away. It just gets answered implicitly — by the products you build, the incentives you design around, the users you prioritise, and the ones you don’t.

There are broadly two categories of technology, and most products exist somewhere on a spectrum between them. One category is built for extraction: to capture attention, to monetise behaviour, to accumulate advantage for whoever holds the platform. The other is built for genuine human value: to reduce friction in people’s lives, to extend access to services that were previously out of reach, to give people better tools for work, health, money, and connection.

Neither category is entirely pure. But the distinction matters. The companies and teams that build lasting things — the ones that are still around in twenty years — tend to be the ones that knew which category they were working in and chose deliberately.

The Scale Problem

Sagan’s framing does something useful: it collapses the distance between the abstract and the personal. The “mote of dust” isn’t a metaphor for smallness in a diminishing sense. It’s a reminder that everything that has ever mattered, happened here, on this fragile shared surface.

When you build software that reaches millions of people, you inherit a version of that weight.

Our systems are not neutral. A credit scoring algorithm decides who gets access to capital. A healthcare triage platform influences who receives timely care. A payroll system determines when workers see their wages. A government digital service decides how citizens interact with the institutions meant to serve them. These aren’t edge cases. They are the ordinary, daily stakes of software operating at scale in sectors where the consequences of a bad decision — or a careless one — fall on real people.

The engineer who built the system rarely sees this. The product manager who shipped it is already onto the next quarter. The technical debt that accumulates in legacy financial infrastructure is, in a very real sense, debt owed to the people whose lives that infrastructure touches. When the system is slow, opaque, or exclusionary, it is slow, opaque, and exclusionary to someone. Usually someone who had fewer options to begin with.

Building With Awareness

This is not a call for paralysis. Technology does genuine good. It extends access to services, creates economic opportunity, reduces friction, and improves outcomes in ways that were genuinely impossible before. The argument isn’t against building. It is for building with awareness of what you’re building and who it serves.

At Nematix, we work primarily in regulated industries — fintech, banking, healthcare, and government — precisely because the stakes are real and the standards are high. Working in these environments forces a discipline that we think every software team should aspire to regardless of industry: you have to design for edge cases, you have to think about the underserved user, you have to take security and data governance seriously, and you have to measure impact not just velocity.

Designing for the underserved is not a CSR exercise. It is an engineering constraint. Building a digital banking product that works only for users with high-speed internet, premium devices, and existing financial literacy is not a complete product. It is a product with assumptions baked in — assumptions that exclude a significant portion of the people it was nominally meant to serve.

Measuring impact, not just velocity, means asking harder questions than “did we ship on time?” It means tracking whether the thing you built actually worked — for the people who use it, not just the people who commissioned it.

None of this is easy. It adds friction to processes that move faster without it. But the alternative is to build carelessly, at scale, with consequences that outlast the sprint cycle and the product roadmap.

Conclusion

Sagan’s pale blue dot is a perspective exercise. It asks us to hold two things at once: the smallness of our context and the realness of everything that happens within it. The vastness of the universe does not make human experience less meaningful. It makes it more precious, and more worth protecting.

Technology is one of the most powerful levers our species has ever built. It can extend what is possible for hundreds of millions of people, or it can concentrate advantage and narrow options. It can be designed with care for the people it touches, or it can treat them as metrics.

We don’t have the luxury of building carelessly. The dot is too small, and the stakes are too real.

Learn how Nematix’s Innovation Engineering services help businesses build, scale, and modernise technology products.