When Pope Leo XIV addressed the College of Cardinals last week and declared that war is "never blessed by God," he didn't just make a theological statement-he dropped a gauntlet that challenges every technologist, engineer. And developer who builds Military systems. For those of us in the software trenches, the Pope's words land with the weight of a code audit that reveals a design flaw at the architectural level of our entire profession. If war can't be blessed, then every line of code that enables conflict carries a moral cost that no performance optimization can offset.
The original report from Detroit Catholic captured a momentous shift in Catholic teaching on war. While previous popes had hedged with just-war theory, Leo's outright rejection forces a reckoning not only for believers but for the trillion-dollar defense industry that relies on the tacit approval of religious and secular moral frameworks. As a software engineer who has spent a decade building both civilian and defense-adjacent systems, I can tell you: this isn't an abstract debate. It is a concrete engineering challenge.
Below, I break down why Pope Leo's statement matters for anyone writing code, designing AI. Or architecting distributed systems-and what we can do about it.
The Context: Pope Leo's Bold Declaration
Pope Leo XIV's consistory address wasn't a offhand remark. According to multiple sources including The Daily Beast, Leo explicitly reframed the just-war tradition as "the language of failure," arguing that any resort to armed conflict constitutes a failure of human reason and Christian charity. This is a radical departure from the nuanced positions of John Paul II or Benedict XVI, who maintained that defensive wars could be morally permissible under strict conditions.
For the technology community, this shift has immediate practical implications. If the highest moral authority in the Catholic Church declares war inherently flawed, then the systems we build to wage war-from autonomous drones to battlefield logistics software-carry a prima facie ethical burden. Engineers can no longer hide behind "just following orders" or "my code is neutral. " The Pope's words invite us to ask: can a weapon system ever be blessed?
The Just War Theory in the Age of Algorithmic Warfare
Traditional just-war theory rests on criteria like last resort, proportionality, and discrimination between combatants and civilians. But as our engineering tools become more autonomous, these criteria become harder to satisfy. In 2019, I worked on a project that used reinforcement learning to improve supply chain logistics for a humanitarian organization. A year later, a similar algorithm (same architectural pattern, different objective) was being used by a defense contractor to route military convoys through contested zones. The code wasn't evil-the use case was.
Pope Leo's blanket condemnation of war challenges the very premise that a "just war" can exist. If war is never blessed, then no amount of algorithmic tweaking can make it right. This isn't a Luddite position it's a call to redirect our engineering talent toward conflict prevention and peacebuilding technologies-early warning systems, dispute-resolution platforms. And open-source verification tools-instead of ever more efficient killing machines.
Why Engineers Must Care About the Ethics of Their Creations
The standard reply among my peers is: "I just write the code; I don't decide how it's used. " This is the software equivalent of the Nuremberg defense. In production environments, we found that every commit carries implicit assumptions about the user's intent. A facial recognition API trained on biased data becomes a tool of oppression regardless of the developer's intentions. A drone-strike algorithm that reduces civilian casualties by 10% still kills innocents-and the engineer who tuned the model is complicit in every misclassification.
Pope Leo tells cardinals war is 'never blessed by God' - Detroit Catholic carried the story with the nuance it deserves. But the engineering community has yet to respond with equal seriousness. The Politico piece highlights how the Vatican's stance may clash with US foreign policy. But the real battleground is in the codebases of tomorrow.
Autonomous Weapons: A Case Study in "Blessed" vs "Unblessed" Tech
Consider the L3Harris Ghost Robotics quadruped-a military ground drone capable of autonomous navigation. Its software stack includes perception, path planning, and target acquisition modules. Each module is developed by teams that may have no visibility into the final weaponization. If Pope Leo is correct, the entire pipeline-from the computer vision team at a Midwestern startup to the integration engineers at the prime contractor-is participating in an endeavor that can't receive moral blessing.
This isn't hypothetical. In 2020, several major tech companies (Google, Microsoft, Amazon) faced internal revolts over military contracts. Engineers at Google walked out over Project Maven, an AI-powered drone surveillance system. The walkout was a direct expression of the same moral intuition Leo articulated: some uses of technology are so contrary to human dignity that they must be refused, even at the cost of one's career.
How Open Source Collaboration Could Foster Peace
If war is never blessed, what is? The Vatican itself has been investing in open-source peacebuilding tools. The Dicastery for Promoting Integral Human Development has funded several initiatives around conflict early warning using natural language processing to detect hate speech in local media. These are the kind of projects that deserve our engineering attention-not because they're more "exciting" than defense tech. But because they align with the Pope's vision of technology as a gift for unity, not division.
Open-source frameworks like UNDRR Early Warning Systems provide real-time data pipelines that can predict ethnic violence before it erupts. By contributing to such projects, engineers can literally write code that prevents war, rather than enabling it. Pope Leo tells cardinals war is 'never blessed by God' - Detroit Catholic reported this with a local angle, but the global implication is that our keyboards are weapons-or shields.
The Role of Data Science in Conflict Prediction and Prevention
Data scientists have a unique role to play. Using publicly available datasets like the UCDP/PRIO Armed Conflict Dataset, researchers have built models that forecast conflict onset with 80% accuracy at the country-year level. However, the same methods used for forecasting can be repurposed for battlefield targeting-the so-called "dual-use" dilemma. Pope Leo's teaching suggests that we should actively disambiguate our tools: build prediction models that are explicitly tied to prevention funding, resource allocation. And diplomatic intervention, not kill chains.
At a conference last year, I met a team from the UN Development Programme that uses satellite imagery to detect crop failures and displacement patterns before violence escalates. Their pipeline uses TensorFlow, R Shiny. And Kubernetes-the exact same stack used by defense intelligence agencies. The difference is the intent, and the contractual safeguards. Engineers should insist on ethical use clauses in their employment agreements, referencing frameworks like the IEEE Ethically Aligned Design guidelines.
Debunking the Myth of Technological Neutrality
The idea that technology is "just a tool" is one of the most persistent and dangerous fallacies in our industry. Every API - every microcontroller, every neural network architecture embodies the values of its creator and the constraints of its intended use. A feature for "persistent tracking" in a surveillance system isn't neutral; it's a design choice that assumes surveillance is acceptable. A drone's "loitering" mode isn't neutral; it's a weaponization of patience.
Pope Leo's statement forces us to confront this myth explicitly. If war can never be blessed, then any tool specifically designed to make war more efficient is inherently disordered. Engineers who work on such tools must ask themselves: am I building something that could ever receive a blessing? If the answer is no (and for weapons systems it almost certainly is), then the only ethical course is to redirect one's talents.
Practical Steps for Developers to Align with Ethical Principles
What does this look like on Monday morning?
- Audit your employer's clients. Are you building for the Department of Defense, border enforcement, or police surveillance? If so, consider whether the Pope's teaching (or your own moral framework) can accommodate that work.
- Contribute to open-source peacetech, Projects like Humanitarian ID or Ushahidi need experienced engineers. Your Docker, PostgreSQL, and React skills are in high demand for crisis mapping.
- Advocate for ethical review boards Push your company to adopt the IEEE Global Initiative on Ethics of Autonomous and Intelligent Systems recommendations.
- Refuse to work on "black box" military AI. If you can't explain what your model decides and why, you cannot be sure it aligns with moral constraints.
Frequently Asked Questions
- Does Pope Leo's statement mean all military technology is evil? Not necessarily. But it does mean that any technology whose primary purpose is to wage war is morally problematic. Defensive systems may still be debated, but the burden of proof now lies heavily on those who argue for them.
- Can Catholic engineers still work for defense contractors? The Vatican hasn't issued a definitive ban. But the Pope's clear language suggests that such work requires extraordinary justification-and that the default position should be non-participation.
- What about cybersecurity and information warfare? Cyber operations that target civilian infrastructure or spread disinformation would also fall under the Pope's condemnation, as they're forms of conflict that harm civilians.
- How does this relate to AI ethics guidelines? Many secular frameworks (e, and g, EU AI Act, IEEE) already call for "human-centric" AI. Pope Leo's statement adds a theological layer that could influence faith-based investors and institutions to divest from defense AI.
- What can a junior developer do to make a difference? Choose open-source projects that align with peacebuilding. Use your voice in team meetings to ask ethical questions. Your refusal to build a weaponized system may inspire others to do the same.
Conclusion
Pope Leo XIV has done something remarkable: he has reminded the world that some lines should never be crossed, even with the most advanced technology. For the software engineering community, his words are a challenge to examine our work not just for bugs and vulnerabilities. But for its ultimate purpose. If war is never blessed by God, then let us use our skills to build things that are blessed: peace, justice. And human flourishing.
The next time you think about tackling technical debt, consider moral debt as well. Write code that you would be proud to have blessed-and if you can't, rewrite it.
What do you think?
Should software engineers have a professional code of ethics that prohibits building weapon systems, similar to medical oaths? Or is the "just a tool" argument still valid in some contexts?
If Pope Leo XIV called on every tech company to publicly divest from military contracts within five years, would that accelerate the shift toward peacetech,? Or would it create a dangerous gap filled by less-accountable nations?
How can we design performance metrics for conflict prediction systems that incentivize prevention rather than targeting-and who should define those metrics?
.
Need a Custom App Built?
Let's discuss your project and bring your ideas to life.
Contact Me Today →