AWS Builder Center
Version 1776

Version 1776

From the Continental Congress to quantum computing: why building under uncertainty is the spirit of what the 4th of July celebrates.

Series: A Veteran's Guide to AWS (5 articles)

  1. …
  2. 5
    Version 1776 This article
Founder & CEO of Altivum® Inc., Army Veteran, and 11x AWS Certified

The American Prototype

Every founding document America has ever produced was a build. The Declaration of Independence was a spec. The Constitution was version two, shipped after the Articles of Confederation failed in production. The Federalist Papers were the design docs where three people debated in public about edge cases, failure modes, and the tension between speed and stability. The United States as we know it has been an iterative process built into existence by people with no guarantee it would work, who shipped anyway, and who kept patching and debugging through a civil war, two world wars, a civil rights movement, and every recession in between.
This is the core of what the 4th of July celebrates. Yes, we remember the incredible accomplishments that founded this country but the human characteristic we celebrate is the spirit of innovation. Today we celebrate the spirit of building under uncertainty, because that is precisely what founding a country, a company, or any organization is.

The Embodied Spirit of Innovation

Let's take the visionaries and assess their character traits through the lens of a company founder and a politician. Both demand that you take responsibility for an outcome that does not yet exist, using resources that are never quite sufficient, under conditions that refuse to hold still. Neither offers a guarantee. Both punish hesitation and reward the willingness to act on incomplete information, then correct course in real time once the information improves.
This is why a veteran who becomes a founder or a politician is not making a massive career pivot. They are redirecting the same impulse that put them in uniform. That impulse is an innate refusal to be a bystander to a problem they are capable of positively affecting. Service, when viewed under that light, becomes less about the uniform and more about being accountable to something larger than your own comfort, and that accountability does not end on your last day of active duty. It just needs a new area of operations.
For a growing number of veterans, that theater is now a codebase, a cap table, a lab bench, or a workshop. Veterans currently own roughly 1.6 million U.S. businesses generating over a trillion dollars in receipts. This statistic looks like commerce on paper but it actually functions like a second enlistment. It is a very similar oath, restated as a business plan.
I do want to be very clear about one thing: this impulse was never exclusive to anyone who served. It is the impulse of anyone who looks at a broken or absent system and decides, somewhat unreasonably, that they personally are going to be the one to fix it. The veteran-builder and the civilian-builder are two expressions of the same appetite for consequence, and that shared appetite is what actually deserves the toast today, not the uniform and not the résumé.

The Next 250 Years

While the spirit of innovation remains resilient, the speed at which this drive now gets tested has significantly increased.
Let's look at the scale of the last comparable national endeavor. At its funding peak in the mid-1960s, the Apollo program used close to 4.4 percent of the entire federal budget, a commitment so massive that it would mean spending about $300 billion on a single moonshot. That was what ambition actually cost when a nation decided to build something it did not yet know how to build, and it took the better part of a decade to pay off.
Now let's look at how fast the current bet is moving by comparison. In 2022, Amazon Braket put the first neutral-atom quantum processor on the cloud, at 256 physical qubits. This year, Rigetti brought a 108-qubit gate-based system onto that same cloud at 99.1 percent two-qubit gate fidelity, and AWS announced an expanded partnership with QuEra to deliver Libra, a fault-tolerant, megaquop-scale machine capable of a million reliable logical quantum operations, to Braket by 2028. Four years, from proof of concept to a published architecture for fault tolerance. In about the same span, autonomous AI agents went from an academic curiosity to production infrastructure inside a majority of enterprises, with Gartner projecting that 40 percent of all enterprise applications will embed task-specific agents by the end of this year, up from under 5 percent in 2025. Industrialization took generations to remake the country. The space race took a decade. This is happening in single-digit years, because the tools we use for creation, compute, capital, and now cognition itself, have become much more accessible to any individual willing to use them.
The founders did not have the luxury of asking for permission from an established order. They built the order. Every builder alive today, veteran or civilian, quantum researcher or first-time indie hacker, inherits that same absence of permission, now paired with tools that let a single person move at a pace that used to require a massive budget.
Building anything real, a company, a quantum algorithm, an agent architecture, a piece of legislation, a life after service, is still mostly composed of unglamorous repetition: debugging at two in the morning, a fundraising rejection you did not see coming, an experiment that fails for the fortieth time before it works once. The romance in all of this is in the choice to keep showing up to solve a problem that you have decided is worth solving regardless of what it costs you personally.
That is the actual thread running from the Continental Congress to the Apollo control room to a Braket notebook to a garage where someone is training a first model tonight.
So on a day set aside to mark the country's founding, the most useful thing to celebrate is the spirit of innovation that recognizes our amazing country as an unfinished one: a system still being actively built by the people inside it, generation after generation, patch after patch, each one working at whatever speed their moment allows. The veteran who trades a rifle for a GitHub repository has not left service behind. The civilian engineer pulling an all-nighter on a project has not wandered off from anything serious. Both are doing the work the founders did: refusing to accept the current state of the system as final, and being willing to be wrong in public in order to make something better exist.
That is The Builder's Oath.

Series: A Veteran's Guide to AWS (5 articles)

  1. …
  2. 5
    Version 1776 This article
Any opinions in this article are those of the individual author and may not reflect the opinions of AWS.
Enjoyed reading this content? Let the author know!

Your likes, comments, shares, and saves help creators reach more builders.

Loading recommendations

Loading article