Chasing the Dream
Sadly, that's not a song title, but it should be.
This weekend, my younger brother left for Florida to start attending Full Sail where he'll be a student of Computer Art and Animation. He has a "blawg" (don't be fearful of the URL...I don't know, you'd have to ask his comrades) and his latest post talks about coming to terms with pursuing your dreams and the journeys they lead you on. Or, in the historical case of our family, not. While this doesn't correlate directly (that I see) to the principles of Agile development, I feel that, at some level, there may be...So I expound...
I can, in some way, feel Sean's pain. James Newkirk recently disclosed the availability of a position at Microsoft in their Community/Collaborative development group; you know, GotDotNet.com, etc. The position responsibilities/skill set includes familiarity with Agile Development and Test-Driven development. And while I have absolutely no formal experience in either of those two areas, I have taught myself a lot about them both. Enough to feel that if there was any development-related position at Microsoft that I had a remote chance at, this would be it.
I applied not. Why? Because it meant too much. Too much to give up. Moving to Redmond. Knowing I'd most likely be asked to commit too much time for work and "abandoning" my bride. It meant asking her to abandon all she was familiar with and risk, ultimately, our marriage, on this dream. It meant too much to risk. "Living to work".
While he said that everyone says they're proud of him, and as clecha as it sounds, I am. How can anyone not be proud and confident in someone who's chasing their dreams? I have so much respect for him in just the fact that he has the balls to risk, practically everything, for his dreams. I'd die to be able to learn and be good what he does. He's so immensely creative that I know, based on that alone, he will succeed and achieve his dream.
And bro, if you read this, Easter won't come soon enough. Be well, be safe, be smart! And have fun doing it.
This weekend, my younger brother left for Florida to start attending Full Sail where he'll be a student of Computer Art and Animation. He has a "blawg" (don't be fearful of the URL...I don't know, you'd have to ask his comrades) and his latest post talks about coming to terms with pursuing your dreams and the journeys they lead you on. Or, in the historical case of our family, not. While this doesn't correlate directly (that I see) to the principles of Agile development, I feel that, at some level, there may be...So I expound...
I can, in some way, feel Sean's pain. James Newkirk recently disclosed the availability of a position at Microsoft in their Community/Collaborative development group; you know, GotDotNet.com, etc. The position responsibilities/skill set includes familiarity with Agile Development and Test-Driven development. And while I have absolutely no formal experience in either of those two areas, I have taught myself a lot about them both. Enough to feel that if there was any development-related position at Microsoft that I had a remote chance at, this would be it.
I applied not. Why? Because it meant too much. Too much to give up. Moving to Redmond. Knowing I'd most likely be asked to commit too much time for work and "abandoning" my bride. It meant asking her to abandon all she was familiar with and risk, ultimately, our marriage, on this dream. It meant too much to risk. "Living to work".
While he said that everyone says they're proud of him, and as clecha as it sounds, I am. How can anyone not be proud and confident in someone who's chasing their dreams? I have so much respect for him in just the fact that he has the balls to risk, practically everything, for his dreams. I'd die to be able to learn and be good what he does. He's so immensely creative that I know, based on that alone, he will succeed and achieve his dream.
And bro, if you read this, Easter won't come soon enough. Be well, be safe, be smart! And have fun doing it.