Astronaut Selection

I wish I was writing this post to say I have been selected as an Astronaut Candidate (or ASCAN as they are called), but I’m afraid that’s (most likely) not the case. No, instead I am writing a much more useful post...why NOT being selected doesn’t matter. I’m not just saying this because I wasn’t selected, I’m saying that it doesn’t matter because that is how I have chosen to approach my attempt at becoming an astronaut. The reason I am sharing this approach is because I think it’s a philosophy that is useful in many other applications and not just for those aiming to become an astronaut.

First of all, how do I know I haven’t been selected? I don’t. The official timeline for the current round of selections is below:

Nov 15 2011:           Announcement of selection opportunity

Jan 27 2012:            Announcement closes (applications are due)

May-Sept 2012:       Applicants reviewed to determine Highly Qualified applicants. Highly Qualified applicant’s supervisors and references are contacted by mail and civilian Highly Qualified applicants are sent an FAA medical exam request by mail

Aug-Nov 2012: Highly Qualified applicants reviewed to determine interviewees

Go here to see the rest of the selection timeline...

To my knowledge, my supervisor and my references have not been contacted and I know that many of the other applicant’s references have been contacted and other applicants have received the request to obtain an FAA physical examination. According to the schedule and according to a person that works as part of the astronaut selection team the first round of down-selecting won’t be complete until October...so there is still a chance. I’m not giving up by any means, but more than likely I didn’t make the cut this time around...and if I didn’t I’ll keep on trying! This round of astronaut candidate selection had the 2nd largest number of applicants in the history of NASA astronaut selections...6300 applicants! If you want to learn more about how the selection process works and what happens to the candidates after selection all way up until their first flight visit the NASA astronaut website.

So why am I, someone whose favorite movie (Gattaca) has a character that is willing to:

  • Purchase someone else’s identity
  • Have surgery on his own legs in order to match the height of his new identity’s profile
  • Memorize orbital mechanics books
  • Risk his life (imminent heart failure due to a possible flaw in his heart) by competing against his brother in swimming contests and performing routine physical examinations as part of his employment as an astronaut

not willing to go to similar extremes on his quest to become an astronaut. The truth is, I am willing to go to extremes if they will help...but many of them don’t. I’ve had the privilege to both work with and meet many astronauts over the years and they all give me the same advice on how to maximize my chances of becoming an astronaut. Listen up, because this advice applies to life in general and not just the lofty pursuit of reaching for the stars! The advice is simple, work hard to become an expert at something you love. Be the best at SOMETHING. That’s it. That’s the secret recipe for becoming an astronaut. The competition is incredibly tough, so those that are selected are almost always without fail an expert of some kind in their particular field. It’s not so much that it’s a requirement to be some kind of an expert, but more so that the type of person that is able to achieve the title of “expert” is also the kind of person that is able to excel at flying into the unforgiving environment of space, making life and death decisions under pressure, and conducting extremely complicated tasks with crew mates who don’t speak your native language.

So I made myself a promise back before I even graduated with my undergraduate degree...I was not going to pursue advanced degrees and make career choices that looked good on paper just for the sake of increasing my odds at being selected as an astronaut. Instead I was going to go out and do things I am passionate about to the absolute best of my ability and ENJOY the journey. No destination is worth sacrificing everything in order to arrive, because if you arrive at your ultimate destination a mentally exhausted or unhappy person you don’t get to enjoy your “achievement.” One of the most important qualifications of an astronaut is being a well rounded person and you can’t achieve that unless your life in is balance. So my advice to everyone (advice that I personally live by) is to “save nothing for the swim back.” Pour everything you have into something you love and don’t look back!

Would love to hear what you all think about this advice! Is it sound? Also, if you have any questions about the process of applying to become an astronaut I would be more than happy to share what I know...contact me via my contact page or on Twitter!

Single Vision for App Dev

My last blog post talked about the important of keeping the design of the app as simple as possible. In order to make some of the difficult decisions needed to ensure the app design stays true to its original intended purpose, you need to establish (BEFORE beginning to design and code the app) the main purpose or "need" for the application. The process I am about to describe is actually a process used by Systems Engineers to design and develop highly complex systems. The reason this process is used for complex systems is that without establishing this single and simple vision you can end up building the WRONG system. 

A need statement is nothing more than a very basic sentence or phrase that states why something is needed. The only rule that needs to be followed when developing this needs statement is that the statement can't have a solution built into it. For example, if you were writing a needs statement for a kitchen timer app the needs statement shouldn't contain the phrase "kitchen timer." Kitchen timer is a solution to the need to keep track of specific durations of time while cooking and preparing food. The reason for this rule of not stating a solution in the needs statement should become obvious in the next few steps of this process. 

Now that you have established the basic need, the next step is to list out important aspects you would like the solution to employ in order to meet the need. We call these goals and the goals should be high level strategies that are absolutely essential to meet the need. For the kitchen timer example, three goals of the solution might look something like this: 

  • Goal 1: Support both time duration and local time relative timing events
  • Goal 2: Provide non-visual information and feedback to the user
  • Goal 3: Minimize the need for the user to interact with touch gestures

Goal 1 is all about having the ability to set timers based on a time duration or a user defined time offset from the local time. For example, while cooking in the kitchen you may have a casserole in the oven for a certain duration and you might also want to start chilling some wine 30-minutes before the expected arrival time of the guests. Goals 2 and 3 are about the use case of physically cooking in the kitchen. You might not always be within view of your kitchen timer so having non-visual feedback (tones, alarms, voice messages and vibration) would be useful. In addition to moving all about the kitchen the user may also have their hands covered in food. A goal to minimize finger touch interface and maximize things like gestures (think of using the back of one of your knuckles to trigger a timer when your fingers are covered in goo). Voice commands could also be used to help meet this goal (can you say Siri API?).

We have arrived at the last piece of the vision for the solution we are aiming to design and that is the objectives. Objectives are simply ways to measure whether we have achieved the goals. Objectives are high level technical performance requirements, but more importantly they are a measuring stick to keep you honest as a developer. Typically these objectives are really important. If you find yourself during the design process worrying about other aspects of the design and you are aren't meeting your objectives you know you are focusing on the wrong things.

For the kitchen timer example, the following could be objects that address the goals we just created:

  • Objective 1: Timer function shall support 4 timers at once
  • Objective 2: Timer function shall support clock based timers
  • Objective 3: Timer function shall use 4 different vibration alerts
  • Objective 4: Timer function shall use 4 different alert tones
  • Objective 5: Timer function will respond to a swipe gesture
  • Objective 6: Timer touch target will be at least x pixels wide

So how does all of this fit together and help a developer focus on what's important? Below is how the objectives flow up into the goals and ultimately back to the need:

As you can see from the diagram, this exercise has created a very clear set of objectives that can be measured during app development. The examples shown here are greatly simplified. In reality you will end up with much more specific and more easily measurable quantities for your objectives. The important thing to take away from this is that spending a few hours fleshing something like this out for your next app could really pay-off when later down the road when you have to start makind critical design decisions. Remember, it should all link back to the basic need you are satifying with the app. If it doesn't, then you are going down the wrong path.

Yes, I am still workng on developing my 1st iOS app and no it's not a kitchen timer. When I release the app I'll post my needs, goals, and objectives and see if all of you and my customers agree that my app stayed focused on the need that spurred the creation of the app in the first place.

Creative Commons License
This work is licensed under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.