Longer version of my story

Being a US Navy F/A-18 Pilot

As a US Navy F/A-18 pilot, I had to say that my job was pretty much the coolest thing ever. I mean, how many people can say they got to fly supersonic jets for a living? It was like being a real-life superhero, except without all the spandex and uncomfortable underwear.

But seriously, being a Navy pilot was an absolute blast. The first time I strapped into the cockpit of an F/A-18 was like a dream come true. I felt like Maverick from Top Gun (minus the love triangle and the tragic ending).

One of the best parts of the job was the constant training and drills. It wasn't just about flying the jets, it was also about maintaining peak physical and mental condition. I ran miles in full flight gear, performed water survival drills, and even learned how to fight off a full-grown man while strapped to a spinning chair (it was harder than it looked).

But the real fun started when I was up in the air. There was nothing quite like the rush of pushing an F/A-18 to its limits, feeling the G-forces pressing against my body as I pulled off daring maneuvers. And let's not forget about the weapons systems - it was pretty satisfying to blow stuff up in a simulated environment (just don't tell my mom).

Of course, being a Navy pilot wasn't all fun and games. There was a lot of hard work and dedication involved, and it was a serious responsibility to fly a multimillion-dollar aircraft and protect our country. But even with the long hours and intense training, I wouldn't have traded my job for anything. It was the ultimate thrill ride, and I felt lucky to be able to do it every day.

MBA School

So, before I left the military, I went back to school to get my MBA. I chose William & Mary because of its reputation and the fact that it was close to where I lived. It was a challenging program, but I loved every minute of it. I made some great friends, learned a ton about business, and even got to do a school trip to China!

Transitioning to Software Developer

But eventually, all good things must come to an end, and I found myself transitioning from Navy F/A-18 pilot to software developer. It was definitely a change of pace, and there were a few things that took some getting used to.

The biggest adjustment going from Navy F/A-18 pilot to software developer was the lack of G-forces. I found myself constantly wanting to tilt my chair back to try and recreate that feeling, much to the confusion of my coworkers.

I also had to get used to the fact that crashing was no longer an option. In the Navy, if something went wrong, I had a parachute and could eject. In software development, if something goes wrong, it's usually just a matter of frantically trying to fix it before the deadline.

The dress code was also a bit of a culture shock. Gone were the flight suits and combat boots, replaced with business casual and sneakers (if I was feeling rebellious). It was a strange feeling to be discussing code while wearing khakis and a polo shirt.

One thing I really missed was the camaraderie of being in the military. In the Navy, I was part of a tight-knit team, always working together towards a common goal. In the software industry, it's more of a cutthroat environment, you are on your own until it suites someone to help out.

The biggest difference, however, was the lack of excitement. Don't get me wrong, I love software development, but it's just not the same as flying a supersonic jet and blowing stuff up (in a simulated environment, of course). I do miss the rush of being up in the air, but at least I get to sit in a comfortable office chair all day.

Fighting a different kind of war

As someone who works on cutting edge military technology for the air force, I have to say that my job is pretty darn cool. I mean, how many people can say they get to work on top secret projects that could potentially change the course of history? It's like being a real-life Tony Stark (minus the billions of dollars and the Iron Man suit).

One of the best parts of the job is the constant research and development. It's not just about designing new technology, it's also about testing and refining it to make sure it's the best it can be. But the real fun starts when I get to see my technology in action. There's nothing quite like the feeling of watching one of my creations soar through the sky, knowing that it's helping to protect our country and our way of life. And let's not forget about the weapons systems - it's pretty satisfying to see my designs take out a simulated enemy target.

Of course, working on military technology isn't all fun and games. There's a lot of hard work and dedication involved, and it's a serious responsibility to create technology that could potentially be used in combat.

Fighting the military acquisition system is like trying to wrestle a giant, stubborn octopus. You think you have a grip on something, and suddenly it wriggles free and smacks you in the face with an arm. And just when you think you've finally won, it grabs you with another arm and sucks you back in. It's a never-ending battle, and it can be exhausting.

Another challenge is the bureaucracy. It's like trying to navigate a maze made of red tape and bureaucracy. You have to jump through so many hoops and fill out so many forms that it's a wonder anything gets done. And don't even get me started on the meetings. They go on forever, and it's like trying to herd cats to get anything accomplished.

But perhaps the biggest challenge of all is the fact that the military acquisition system is just plain old. It's like trying to use a flip phone in the age of smartphones. It's slow, it's clunky, and it can't keep up with the rapid pace of technological advancement. It's a constant struggle to try and modernize it, but at least I get a good workout trying to push it forward.