When code thinks about the future: sustainable software

How far does a developer’s responsibility go? We’re not talking about optimizing queries or reducing memory consumption. We’re talking about something deeper: the social and environmental impact of the software we build, the legacy we leave for the teams that will maintain our code. Furthermore, we’re talking about the ethical decisions we make under pressure.

These questions took center stage in Sergio García’s talk on sustainability in development, organized by the Node.js Madrid meetup, which we hosted at Orbitant’s offices. A session that transcended the technical and left more uncomfortable questions than easy answers. Exactly the kind of talk that makes you grow.

Beyond clean code: the real impact of software

When you’re in the thick of development, you focus on what you’re building, and in those moments it’s hard to think about the social or environmental impact, or about who will maintain the code you’re writing.
— David, software engineer at Orbitant

That’s the key. There’s no point in obsessing over making reusable and scalable code if you rarely ask yourself why you do it or what the consequences are of not following these practices.

Sergio García introduced a concept that particularly resonated: utopian pragmatism. It’s not about achieving absolute perfection or blocking projects due to unattainable ideals. It’s about raising awareness. About doing small things that, when added up, make a difference.

AI, energy consumption, and the myth of “building for building’s sake”

One of the most tense moments of the talk was when the impact of artificial intelligence was addressed. David’s reflection sums it up well:

There’s no point in building proprietary solutions just to feel smarter. That creates noise and unnecessary waste, like water consumption in Silicon Valley.
— David, software engineer at Orbitant

This idea connects directly with the way of working we promote at Orbitant: we don’t use a technology because it’s “trendy”; we use it if it solves a real business problem in the most efficient way. It’s worth remembering that sustainability isn’t just an environmental or ecological issue: it’s making conscious decisions about what, how, and for whom we build.

Three key ideas about AI and sustainability

• AI is a tool, not an end in itself. If a solution already exists, don’t reinvent the wheel just for technical ego.
• The hidden cost is real: every trained model, every active server, every unnecessary request has an energy and resource impact.
• What isn’t measured can’t be improved: if we don’t know how much what we build consumes, we’ll hardly be able to optimize it.

The uncomfortable question: professional ethics in times of urgency

This was the question posed by one of our software engineers, Fernando, during the debate. It’s the eternal dilemma: business urgency versus good practices. What the talk made clear is that becoming aware of this is already a first step.

The society we live in imposes certain timelines and processes that are unavoidable, but not everything goes. Avoiding deceiving users, not making processes deliberately difficult, not forcing conversions at the expense of ethics… There are red lines that shouldn’t be crossed.

How honest are we with ourselves? Bugs that need urgent fixing, deadlines we can’t meet that force us to rush without adding tests or documentation, code that isn’t built to last… Who bears that cost?
— Fernando, software engineer at Orbitant

A philosophical debate about software

After the talk, the debate began. Some attendees contributed their own perspectives on the evolution of sustainable principles in development. Topics like:

• The morality of our actions when a superior asks us to prioritize conversion over ethics
• The real cost someone will have to bear: the company or the developer with their personal time?
• The difficulty of maintaining these principles in high-pressure environments

Ultimately, it was a talk that, although it touched on technical aspects, could be considered suitable for all audiences with real-world examples that engaged people. That accessibility is what made the subsequent debate so rich. And so long. And so necessary.

Building community, not just software

Creating spaces like the one we’ve provided to Node.js Madrid meetup to learn about code and debate its moral, ethical, or philosophical implications is part of Orbitant’s culture. Not just for training and exchanging ideas, but for creating connections between professionals from different contexts so they can share real experiences. Plus, technical knowledge is built better when shared over pizza 😛

That’s why we’ve opened our offices: from now on, Node.js Madrid meetup will have a place to meet every month to keep learning. And if you’re reading this and feel like participating, you can submit your proposal directly to their talks repository.