Boeing vs. SpaceX: A 'How It Started vs. How It's Going' Tale of Space Race Promises

Level 1: Bragging vs Doing

Imagine two kids in school who both say they’re going to do something really cool. One kid (let’s call him Boeing) stands up in front of the class and says, “I’m going to build a bigger, better rocket than Elon’s!” He’s very sure of himself and even challenges the other kid, Elon, to a race to see who can get to the planet Mars first. Elon just smiles and says, “Go for it.” Now, Boeing’s really hyped and shouts, “Game on!” meaning “It’s a challenge!” Everyone is excited at the start because Boeing sounds so confident.

But building a rocket (just like doing a big school project) is hard. Boeing the kid keeps running into problems with his project: maybe the engine he’s trying to build doesn’t work right, or the rocket cracks during tests. He thought it would be easy to win, but it turns out to be much tougher than he said. Meanwhile, Elon the kid is quietly working on his own rocket every day after school. Elon’s rocket starts flying little test flights; there were a few crashes at first, but he learned from them and improved quickly.

By the time it matters — say the teacher needs a rocket for the school science fair — Elon has a reliable rocket ready to launch, and Boeing’s rocket still isn’t finished or safe to use. So the teacher says, “We’ll use Elon’s rocket for the fair since it’s working, and we won’t use Boeing’s yet.” In the end, the kid who bragged loudly couldn’t deliver on time, and the kid who focused on actually doing the work succeeded. It’s a bit funny and a bit sad: funny because the big talk didn’t match what happened, and sad (or embarrassing) for Boeing because he had to eat his words.

This meme is showing exactly that kind of story with real companies and astronauts. Talking big about being first is like bragging, but actually being ready and doing it is what wins the day. So it teaches a simple lesson: just saying you’ll do something grand (even in front of a bunch of people) doesn’t mean much if you can’t back it up — you have to walk the walk, not just talk the talk.

Level 2: Space is Hard

This meme shows a before-and-after comparison — a popular “how it started vs how it’s going” layout — to tell a story about big promises vs real outcomes. On the left, in 2017, the CEO of Boeing (a huge airplane and spacecraft company) publicly said something like, “We’ll get to Mars before Elon Musk does!” (Elon Musk is the head of SpaceX, a rival rocket company). Elon Musk even replied “Do it” as a dare, and Boeing’s official account answered “Game on!”. That set the stage like a race or a challenge in front of everyone. This was a major hype moment — essentially, Boeing was bragging that they would outperform SpaceX in space exploration. It’s similar to when a tech company’s boss loudly claims their product will outshine a competitor’s soon. It gets a lot of attention and creates pressure to deliver something great fast.

Now fast forward to the right side: a post in 2024 says NASA (the U.S. space agency, basically the big customer for both Boeing and SpaceX in this context) decided to use SpaceX’s Dragon capsule to bring astronauts home from the International Space Station, and not use Boeing’s Starliner capsule. This is a major update because originally Boeing’s Starliner was supposed to be one of the vehicles for these astronaut trips. So “how it’s going” is showing that, seven years later, Boeing hasn’t reached its goal — in fact, it’s behind SpaceX in a very basic way. Boeing’s spaceship project had so many delays and issues that when the time came, NASA chose the working solution (SpaceX’s capsule that was ready and proven) over Boeing’s delayed one. In simpler terms: the person who did the bragging (Boeing) didn’t get their job done on time, so the big customer went with the other person (SpaceX) who did get the job done.

For someone newer to these terms: Starliner is the name of Boeing’s spacecraft designed to carry astronauts, and Dragon (specifically Crew Dragon) is SpaceX’s spacecraft that does the same thing. Both companies were hired by NASA to taxi astronauts to and from the space station (this was part of NASA’s Commercial Crew Program). Boeing is an older, established firm (known for airplanes and space hardware), and SpaceX is a newer company that’s been very aggressive in developing rockets and capsules quickly. In 2017, Boeing’s chief made a bold statement about beating SpaceX to Mars (a very ambitious target — Mars is far away and hard to reach with people). It was like saying “we’ll be first to achieve this big dream!”. SpaceX, led by Elon Musk, of course has its own goal to go to Mars, but Musk’s playful “Do it” response on Twitter was basically him saying “go ahead, I’d love to see you try.” Boeing doubling down with “Game on!” made it feel like a direct competition.

However, aerospace projects are notorious for being complicated and taking longer than expected — there’s even a phrase in the industry: “Space is hard.” Building a new spaceship (or writing a large software system, similarly) often runs into unexpected problems. Boeing’s Starliner program experienced several setbacks: test flights failed or faced serious glitches, software errors had to be fixed, and timelines kept slipping year after year (schedule slippage is the term when planned dates keep getting pushed out). On the flip side, SpaceX, despite some early explosive tests, managed to successfully fly astronauts with their Dragon capsule in 2020 and has been doing regular trips since. By 2024, Boeing’s Starliner still hadn’t flown any astronauts due to those delays and technical issues — meaning it wasn’t ready for NASA to use when needed. NASA, being the stakeholder (the party that needs the service), can’t wait forever; they have astronauts that need rides. So the announcement in the right panel basically says: SpaceX’s capsule will be used to bring the astronauts back, and Boeing’s capsule won’t be used for that mission. In context, that’s a bit of an embarrassment for Boeing (imagine being publicly passed over for your competitor’s solution).

This is very much a project hype vs delivery story. The initial hype was Boeing saying they’d outdo SpaceX and conquer a major goal quickly. The delivery (or lack thereof) is that Boeing’s product isn’t even ready for a routine task, while SpaceX’s product is already operational and gets the nod. People in tech or project management see this and nod because they’ve seen similar patterns: a company or team promises something huge to keep up with competition or impress clients (stakeholder pressure can push leaders to over-promise), but the project encounters real-world difficulties and falls behind. Meanwhile, a competitor or another team that focused on actually building and testing steadily ends up delivering first. The humor or irony here comes from how stark the contrast is: the confident “Game on!” challenge from years ago versus the humbling news now. It’s like if two students said they’d each build the best science project: one student boasted loudly but is still tinkering with their project past the due date, and the other quietly finished theirs and got first prize. The meme uses the Twitter screenshots as evidence of this turnaround. It’s a bit of a corporate humor snapshot, showing how big talk can lead to big blushes later. And the phrase “How it started… How it’s going” is commonly used online to highlight exactly this kind of dramatic change or outcome, often in a tongue-in-cheek way. In summary, Boeing vs SpaceX here is a lesson that making something work (and meeting your deadline) is what counts in the end — big promises alone don’t fly the rocket.

Level 3: Failure to Launch

For seasoned developers and engineers, this meme sparks a knowing grin (or maybe a groan). It highlights the classic industry pattern of corporate moon-shot bravado followed by a hard reality check. On the left, we have the quintessential overconfident executive proclamation – Boeing’s CEO essentially thumping his chest and saying “Game on!” to Elon Musk in a high-stakes space race. This is corporate culture at work: big promises made under stakeholder pressure (be it investors, board members, or, in this case, NASA contracts) to show that “We’ve got this, we’ll beat the competition.” It’s the aerospace equivalent of a CTO boasting in an all-hands meeting, “We’ll outship our rival’s product by next summer, no sweat.” Everyone who’s been through a few product cycles knows to cringe a little at those moments, because bold claims without grounding in the team’s reality are usually a prelude to unrealistic deadlines and painful crunch times.

Fast forward to the right panel: “How it’s going.” Ouch. Boeing’s much-delayed Starliner capsule still isn’t ready for a routine astronaut taxi ride, so NASA is tapping SpaceX’s Dragon capsule to do the job instead. In plain terms, the competitor actually delivered, while the boaster slipped behind schedule so far that the customer (NASA) had to change plans. This turn of events is both funny and painfully familiar to veterans of big projects. It’s humorous in that schadenfreude way – seeing an overly confident pronouncement fall flat – but it’s also too real. Many of us have lived through projects where managers promised the moon (sometimes literally, in Boeing’s case) and later found ourselves explaining to leadership why we’re nowhere near liftoff.

The meme cleverly uses the “How it started vs How it’s going” format to juxtapose rosy beginnings with sobering outcomes. In software project terms, "How it started" is the kick-off meeting with cheerful Gantt charts and quotes like “We’ll be the first to market, guaranteed.” "How it’s going" is the status update a year later where the deadline has slipped multiple quarters, dependencies didn’t line up, and the competitor already launched their feature while you’re still debugging critical issues. The Boeing vs SpaceX saga is a case study in project management challenges. Boeing had a lot of legacy process and perhaps overconfidence from decades of aerospace dominance, whereas SpaceX, the scrappy newcomer, iterated quickly and accepted early failures (they blew up a few prototypes to get it right – a very different culture!). Internally, Boeing’s engineers were likely grappling with bureaucratic hurdles, exhaustive compliance checks, and integration headaches. Imagine being an engineer on that Starliner team in 2019, watching a demo flight fail due to a clock synchronization bug – you know the schedule just got blown up along with your morale. Meanwhile, SpaceX was pushing out updates and flying multiple test missions. It’s the old industry trend of a nimble team with modern practices outpacing a slower-moving giant weighed down by process (we’ve seen this in tech with startups vs incumbents, and here it’s playing out in space).

From a corporate rivalry perspective, Boeing and SpaceX were in a public relations duel as much as an engineering one. Twitter (now X) became the arena for their macho posturing – Elon’s casual “Do it” retort and Boeing’s “Game on!” tweet show a very public stake being driven into the ground. That’s like two dev leads of rival projects trash-talking on Slack about who will hit performance milestones first. It might energize the troops, sure, but it also raises the stakes for embarrassment. And indeed, by 2024, Boeing got the proverbial pie in the face. NASA’s announcement effectively said: we don’t trust Boeing’s capsule schedule anymore, we’re using the one that works. This is analogous to a big client dropping a stalled enterprise project in favor of a startup’s solution that’s already in production. For senior engineers, it’s a lesson in humility: shipping code (or in this case, spaceships) matters more than flashy promises. It also underlines the danger of unrealistic deadlines: Boeing’s timeline to “beat Elon to Mars” wasn’t just optimistic — it was fantastical, given that neither company has landed anyone on Mars yet and Boeing’s own near-Earth project was struggling. The stakeholder pressure to show progress can lead companies to promise absurd timelines (“sure, we can get to Mars soon!”) that come back to bite them.

Ultimately, this meme is a tech-industry morality tale dressed in space-race clothes. It mocks the hype-driven project management failures we’ve all seen. The left side is the hype (big talk at the project kickoff), and the right side is the delivery (or lack thereof). The comedic contrast resonates with anyone who’s had to debug grand plans under a looming deadline. It’s funny because Boeing set itself up for this punchline — they literally said “Game on!” in front of millions, turning a hard engineering marathon into a brash contest of egos. And in true ironic fashion, the one who quietly focused on delivering a working product (SpaceX) ended up winning that unspoken game. For those of us in development, we see a parallel: it’s like that rival team that was quietly unit-testing and iterating while your team was stuck in meetings about “beating them to market.” The meme’s aerospace face-off is just a high-profile version of the age-old tech lesson: deliverables speak louder than declarations.

Level 4: Physics vs Hype

At the most fundamental level, this meme underscores a harsh truth of engineering: you can’t cheat reality with bravado. In aerospace (and any ambitious tech project), no executive tweet or bold PR statement can bend the laws of physics or the realities of complex system development. Boeing’s CEO proclaiming “We’re going to beat Elon Musk to Mars” was pure hype meeting the unforgiving constraints of rocket science. Consider the monumental challenge of reaching Mars: the delta-v (change in velocity) required is enormous, life-support and re-entry systems must be fail-safe, and every extra kilogram of payload demands exponentially more fuel (thanks to the rocket equation, a fundamental formula dictating rocket fuel requirements). Boeing’s boast in 2017 essentially wagered that their traditional aerospace approach could outpace SpaceX’s breakneck innovation. But Nature cannot be fooled – no matter how many press releases or PowerPoint slides one creates, the chemistry of propellants, the rigor of safety-critical software, and the years of testing required all march to the beat of physics, not PR.

In fact, this scenario echoes a famous lesson from the Challenger shuttle disaster: management’s wishful thinking can’t overcome physical reality. (Physicist Richard Feynman once put it succinctly: “For a successful technology, reality must take precedence over public relations, for Nature cannot be fooled.”) Boeing’s commitment to beat SpaceX was a classic case of rhetoric colliding with engineering complexity. Building a human-rated capsule isn’t just another quarterly project; it involves thousands of interconnected components (from spacecraft avionics to parachute systems) and strict oversight from NASA. Each subsystem is a potential single point of failure that must be discovered and corrected via painstaking integration tests. Such complex systems have emergent problems — e.g., Boeing’s Starliner encountered a timing software bug in 2019 that prevented a proper orbital insertion, a tiny glitch with massive schedule impact. This phenomenon will resonate with any senior engineer: it’s reminiscent of finding a critical concurrency bug in a distributed system right before launch, forcing a painful redesign. There’s a project management analogue to the laws of physics here: Hofstadter’s Law, which wryly states that everything takes longer than you expect, even when you account for it taking longer. In other words, major projects inherently hide “unknown unknowns” that no amount of initial optimism can eliminate.

So, Boeing’s grand promise to beat Musk to Mars ran up against the inescapable constraints of time, complexity, and gravity. You can declare a moon-shot goal, but the actual trajectory is governed by Murphy’s Law and orbital mechanics, not by press bravado. The meme’s punchline — Boeing’s Starliner getting sidelined in favor of SpaceX’s Dragon — is effectively physics saying, “Checkmate.” In tech terms, it’s like a legacy enterprise vendor claiming they’ll ship a revolutionary new system by year’s end without a working prototype: the fundamental effort required isn’t swayed by the announcement. Reality won here, as it usually does, illustrating that in engineering, reality > rhetoric every time.