Written August 15, 2008 at 22:55 MDT Tagged inspiration
This post is way overdue!! Chalk it up to disappearing into the vacation zone for a while!! The original contest was posted here.
In total, there were 16 entries. It took a bit of time to get through the entries (which were all incredible). After reviewing the entries please use the poll at the bottom of this post to vote for your favorite entry. The winners will be announced next Friday!!
Entry 1 - Matt Skriba
My Life in a Nutshell
My life begins in a small Midwestern town. I was born in the midst of a snow storm on December 29, 1977 to David and Mary Smith. When my parents brought me home from the hospital my siblings eagerly awaited. David Jr, Brad, and Laura had a "Welcome Kyle" sign in the doorway to greet their new brother. Just a day earlier they were arguing over whether they would be welcoming a new brother or sister.
My dad is a self employed dairy farmer. He co-owns our farm with his brother, Jerry. They inherited the farm from their father and mother, Frank and Margaret. And with it they also inherited a long fulfilling, yet tough career. Where I grew up, my entire family lives within a single square mile. Our dairy farm is located at my Uncle Jerry and Aunt Amy's house. We have over 60 Holstein cattle. Everyone in my family works long and strenuous hours. Working on a dairy farm is a 365 day a year job. In addition to raising cattle, we plant corn, soybeans, wheat, and alfalfa, so the cows have their food and bedding. The cows must be milked every day. We milk our cows 2 times a day (3:00 am and 3:00 pm). Raising cattle is a lot like having permanent dependent children, you have got to be there to take care of them on a daily basis.
My mom was a homemaker, doing her very best to raise her 4 children. She was a deeply religious person. I was brought up devout catholic. We would never miss a Sunday mass at our local church. My mom's life with my dad were her "best years."
I would soon learn that being brought up in a loving and hard working family would not be as simple as it may seem. I remember as a small boy, as I was running around the house, that my mom was dropping dishes in the kitchen a lot. I also remember her being disoriented, resulting in her falling down and bruising herself. It turns out that my mom was not right, at all. She was diagnosed with Huntington's disease (HD).
HD is a fatal hereditary disease that destroys neurons in areas of the brain involved in the emotions, intellect, and movement. HD progresses without remission over 10 to 25 years and patients ultimately are unable to care for themselves. HD usually appears in middle age (30-50 years), but can develop in younger and older people. Any child, male or female, with one affected parent has a 50% chance of inheriting Huntington's disease.
We cared for my mom at home the best that we could. She eventually required 24 hour a day care due to her illness. Therefore, she unfortunately had to be placed in a nursing home. We visited her in the nursing home often. On November 7, 1995 my mom passed away, with my family and I by her side. I was only 16 years old. I don't have any memories of having a healthy mom.
Life could only get better, right? Well, unfortunately not. While playing basketball for my junior varsity team I noticed I was getting "winded" very easily, so I asked my coach to take me out after only a minute into the game. I also noticed that I was very thirsty, and it was nothing for me to slug down a 2-liter of Mountain Dew. In addition, I was urinating frequently and had lost some weight (which I had attributed to being active and going through a growth spurt). After the basketball season was completed, I went to the doctor and he diagnosed me with type 1 diabetes.
Type 1 diabetes is usually diagnosed in children and young adults. In type 1 diabetes, the body does not produce insulin. Insulin is a hormone that is needed to convert sugar (glucose), starches and other food into energy needed for daily life. Having type 1 diabetes increases your risk for many serious complications. Some complications of type 1 diabetes include: heart disease, blindness, nerve damage, and kidney damage.
I soon found out that I would have to take insulin injections 3 times daily and test my blood sugar by pricking my finger at least that often.
My adolescent years were by far the most difficult time of my life. Everything I was brought to believe in was being challenged. It was hard to understand that my mom was going to be in a better place with God. It was even more difficult to contemplate the possibility that my siblings and I could inherit the cruel disease that took my mom's life far too early (she was only 55, but had not been well for many years before she passed away). It was also difficult to deal with learning about diabetes and all of its complications. Those years were most certainly life-altering.
Horrible things can either make you or break you. I realized that I was dealt a tough hand. My hand was not the greatest, but I finally figured out that I needed to make the best of what I had been dealt. I could sit around and make excuses for myself or turn the negative into a positive life- altering experience. At this point in my life I met a girl named Molly, whom I'd later marry. After meeting Molly, I started to figure out that life is short. I'd need to work hard, to play hard. I soon started working as hard as I could academically. I went from a 3.0/4.0 grade point average (GPA) my freshman year in high school to a 3.7 GPA in my senior year. I got all 4.0s during my last 3 years of high school. My goal was to be in the top ten of my class. I fell a little short, at 15, but had come a long way.
I then continued my journey of academia at Michigan State University. I worked and supported myself, all while taking classes full time. MSU is where I found my love for C++ computer code. While in college, I attended Microsoft groups around campus. I remember when Microsoft did a preview on their new language, C#, and I was blown away. I graduated with a Bachelors of Science in Computer Science in 2002.
Shortly after college, I got my first job in .net doing web development with C# (1.0). After working for a year in mid-Michigan, I took a job in West Michigan. I was the only software engineer at this manufacturing company. I worked entirely by myself for 4 years. I worked 55 hours/week to keep on top of C# and SQL. Other people may have not "stuck it out" in that scenario, but I looked at it as an opportunity to gain experience and grow. I am the type of person who loves learning new things. I am not the type of person who throws in the towel without first trying something. I make no excuses. Too often I've worked with people in programming who just want to do the status quo. They don't know any more than the very basics or care to try harder to make the best product possible. One time when I interviewed at a place here in West Michigan, I asked the programmer that was interviewing me if they used the 3-tiered architecture. He told me that it would take too long to do. I asked him if he had any experience in doing it that way. He said "No." Funny, how could he know that it would take longer if he had never done it that way before?
I've also come to love .net. I worked alone at my job, so I turned to the internet to learn new things. I have listened to dnrtv podcasts. That is how I found your blog and episodes. I then used resharper at my job. I would soon have to leave my job at the manufacturing company in West Michigan because the company closed.
I then took a job working with a 55 developer team at EDS back in mid-Michigan. EDS had a large contract with the State Of Michigan to re-write the drivers-license system. It was an asp.net (C#) project. I worked within the Business Services Layer group for the project. The project was going south when I worked there. EDS did not have enough .net programmers for the project. A lot of the work force was older EDS employees who were completely new to .net. After a few months, EDS changed leadership, with Paul Kimmel stepping in as the architect. Paul Kimmel has written UML books and is also the chairman of the Greater Lansing User Group .Net (GLUGNET). I was in charge of unit testing within our BLL team. EDS then bought another company in Ohio, Saber Systems. Saber Systems already had 90% percent of the functionality of what we were developing, so that ended my stint at EDS. I was back on my way to West Michigan. I have taken a contract to hire job for a business auditing firm. I am working with a small development team of 2 people. We are working on asp.net, c#, and tsql.
How I've Inspired Others
While working as a consultant at EDS, in Lansing Michigan, I worked with older programmers that did not have .net experience. My role was the lead unit tester for the BLL group. I had been given the responsibility of unit testing the 60,000 line code base for our project. The code base was written very poorly. It contained static classes with static functions and void return types on every single class that was in the project. There was gluttony of problems with this lack of design. There were no classes that I could create new instances of for the NUnit test. There were static methods being used which create isolation problems because they're tied to everything the static method uses. Lastly, everything was done on the call stack with no return type. The parameter lists where huge: 10+.
I spoke with Paul Kimmel our architect about unit testing. I told Paul that I had been researching using mock frameworks for the unit tests. I told him that I was looking at using either Rhino or Type Mock for the tests. He told me that he did unit testing before, but he had never used the dependency injection method and mock objects. I was explaining to him the idea for a code example that I wrote. A few days later, Paul presented me with a book about unit testing, for me to keep. He told me that he liked the idea of using mocking objects. He wanted me to take charge of it for our team. I was really happy to introduce mocking and dependency injection to our team. I was able to show Paul something new, that was interesting and worthwhile. Paul Kimmel is a UML author and was keeping very busy as our project lead. I didn't want to bother him with questions about new stuff without having examples to back up the work. He respected the fact that I took the time to learn and help make our team better.
My wife, Molly, has said that I've inspired her as well: maybe not professionally, but personally. She was raised in a family that did not have a very strong relationship with God. Her parents attended church every now and then, but not regularly. After she had her Catholic confirmation in the 8th grade, her parents stopped going to church at all and the rocky foundation that they had started crumbled. After she met me, she began attending church with me more regularly again and her faith in God once again grew strong. Now that we have been married for 4 years and are considering the possibility of starting a family, we are going to ensure that our children will be raised in a loving household with ever-present Catholic values.
She knows what I have overcome and what I am faced with, yet I still live life to the fullest. She states that when she is feeling low, she thinks about how I have handled challenges in my life, and it makes her realize that there is no obstacle too big.
Entry 2 - John Miller
Software development is one of the few fields where, regardless of our experience, the amount we each individually have yet to learn will always out weight how much we already know. I'm still a young pup (been a full-time developer for 4 years now) and I have yet to reach a point in my relatively short career where I felt I held enough knowledge to slow down the learning process (nor do I expect to ever reach that point). Every day there's a new concept, pattern, framework, etc. discovered that gives us a new way to solve business problems in a more elegant manner. And that constant change and new discovery is what makes this field so exciting! It will never get dry and stale; there will always be something new out there to challenge us!
That thirst for improvement is incredibly contagious. I think when one person starts actively challenging themselves to continuously become better at their craft (regardless of the field), it affects those around them. On one of my moonlighting projects, I was leading a project with a couple of brand new to the field developers who were just starting to cut their teeth in web development. When I was brought onto the project, it was already starting to unravel. The scope was poorly defined and on a daily basis the client was coming up with new features that just had to be included in the version one release (which can create a stressful situation on a fixed bid project!). The two newbie developers were struggling to keep themselves afloat. I began working with each of them 5 or 6 hours each week, helping them work through some of the issues they were having. Our first few training sessions were geared around setting up a procedure for handling new feature requests from the client. Instead of coming back from a meeting and jumping into coding, I challenged them type out there notes and create mockups to send back to the client...just to be sure it was what they really wanted. While that wasn't a silver bullet, it did help reduce the amount of throw away code they wrote. That little bit of turnaround they were seeing from simply making a few process changes really seemed to boost their confidence and pretty soon they were doing their own research to find ways to bring in continuous feedback from their clients! It was amazing what they were able to accomplish once their attitude towards the project changed!
While a positive attitude is infectious, a bad attitude can be just as contagious. Prior to our weekly little pow-wows, they were working with a senior developer to help them learn where they could improve their code and overcome some of the obstacles they were facing. And while this developer was extremely intelligent, he was also very condescending in his replies to questions which made the younger guys dread coming him with questions.. One of the guys actually got to the point where he felt that he wasn't cut out for life as a programmer and was considering going back to school to learn a new trade. We decided to start having one on one sessions where the two of us took whatever his current challenge was and pieced together a solution using proven design techniques and after a while, you could almost see the light bulb turn on in his head. It was starting to sink in for him and as things were becoming clearer, he was getting more and more exciting. It's amazing how fast he was picking up new techniques once he started getting enjoyment out of what he was doing! To this day, he remains one of the most passionate developers I know. And he eventually did go back to school in his spare time (to continue his Computer Science degree!).
But we need to be careful that the drive to excel professionally remains in harmony with the other areas of our lives. In a field like this where there's so much left to learn, it can be really easy to neglect those around us. I personally struggled with this my first couple of years out of college. But we have to accept that no matter how much we take in, we're never going to be able to absorb it all. That doesn't mean we lower our goals or standards, but we need to be able to manage those goals in a way that enables us to enjoy our other passions whether that be our families, spirituality, sports, movies, etc. I'm sure we have all been given many different blessings in our lives and we were meant to enjoy all of them, not just one!!
Entry 3 - David Robbins
I wish that this contest were about how great the team I lead is, as they are who I hope to work with for the rest of my career. They are dedicated, talented, and supportive of team and company goals, but most of all they are great individuals whose values extend beyond our technical objectives.
I direct a team 6 people from a variety of educational and business backgrounds. To some extent we have individuals who have great experience with our company, but are still developing in areas of application development. Some need to refresh some skills, while others are fresh on the quest to become better programmers.
I pride myself on my own ability to learn and implement solutions using a variety of resources and techniques, and many times I lead by example by jumping into a solution with a new tool and encourage people to flex and grow. However, this has not been what has made us successful and spurred growth. I lead by the Wolf's Credo:
"Respect the Elders;
Teach the Young;
Cooperate with the Pack"
We have team members who support legacy applications, yet I have found that their input with new processes or techniques to invaluable, and ask them their opinion first. They have gone before us, and have great wisdom. I also challenge them, and have seen them come alive with the new opportunities to solve issues with out of the box solutions. Even when we have consultants and subject matter experts work with us, they have a say.
Many times I'll select a team member for a project who has no experience with a certain tool, pair up with them or with another senior team member, put them through a mini trial by fire and encourage them to fail in order to learn.
"Play When You Can;
Hunt When You Must;
Rest in Between"
I encourage people to read, discover, think, and try new ideas. I have always pushed for "What's a new way to get rid of this problem?" or "How can we stack the game so we can win by doing less?" It's great to see junior team members struggle with a concept, then come up with an idea that the more experienced amongst overlooked. Many times we laugh at my dumb solutions - most of our meetings are filled with a great jocular irreverence.
"Share your affection;
Voice Your Feelings"
Going beyond the above phrase, there have been times when we have needed to pull together and in those moments that we all have faced, when it looks like it'll head South, my team works without backstabbing, coming to each other's aid without question. Because I encourage honest discussion and that we honor each other as people, we don't have sniping, period. This affection and respect for one another have enabled so many people to acquire new skills and develop together as a team, it amazes me. That's why I think the contest should be about them.
Entry 4 - Freek Leemhuis
Okay, so I'm old. I'll be 40 this year. I work with a lot of young and talented developers, and by some of them I'm regarded as somewhat of a guru, something I've never thought would happen until a few years ago.
I've always had a keen interest in computer technology, but it's always been just one of many interests, and when it came to choosing a study I opted for a degree in Psychology at the University of Amsterdam. I've had some fabulous years there getting to know different ways to study the workings of the human mind, but when I started working in the field I was again drawn to technical aspects of it, and gradually I did more and more programming.
I moved to Scotland for love of the country, got married there and found a job in IT. I've enjoyed the years spent discovering what it meant to be a professional developer, but for a long time I've felt that having this different educational background left me playing catch-up with other developers. These guys had a formal education in Computer Science, so they really knew what they were talking about. Or so it seemed at the time. I assumed that I'd never be as good as these guys, so I did what was required to keep up with technology just enough to perform the daytime job of developing software, and spent a lot of free time, well, in the pub.
Things changed when, in the wake of the arrival of our daughter, we moved back to Holland, where jobs were hard to come by at the time. I joined a small software house working as an in-house developer. I had few sparring partners, missed the contact with end-users, and got into a bit of a rut.
I went for an interview for a large software firm, and was interviewed by Eric. To my surprise, he was really enthusiastic about me having the background in psychology.' That's fantastic!', he said, 'Do you realize how much Psychology is involved in software development?'. Having my kind of background made me stand out from other candidates, who had similar technological skills. It then dawned on me: I've got something to offer here, I've got a wealth of experience, and if I really try my best it might not be too late to make a 'real' career for myself.
I started working for Eric and from then on I took my job seriously, spent all of my free time educating myself in things like design patterns, agile software development and learning new tools and languages. At the ripe old age of 38 I was learning more than I ever did before, at amazing pace.
I hindsight, all I needed was someone to see the potential in me and have the confidence that I could realize that potential. I have since developed myself as a speaker, and I've given several sessions on 'the psychology of programming'. I've become active in the developer community. Most of all, I've enjoyed coaching and mentoring young developers. I try to teach them the lessons that I've learned the hard way: you're never too old to learn and if you really try, you can probably achieve more than you can imagine.
Entry 5 - Travis High
My story is really a sort of synopsis of a couple of life events, but paints a larger picture of how being positive and receptive to growing can not only improve your skills but the lives of others.
In December of 2004, I was graduating from college with an undergraduate degree in Computer Science. I had no prospects for employment, a fiance I was to marry the coming fall, and no idea on whether I was going to remain in the small town I grew up in, or move on to a more metropolitan area in search of work. I had served an internship for a large financial services company a couple of months prior, and they expressed interest in bringing me on board as soon as they could get a position approved, but it had been a couple of months without contact, so I continued sending out resumes. It was a tough time due to the level of uncertainty, but fortunately, an opportunity presented itself out of nowhere for a database analyst position I had applied for, so I interviewed for it and landed the job. This presented me with local employment with a decent salary that would allow my future wife and I the freedom of living close to family if we chose.
It didn't take long for me to realize after starting my new job that I wouldn't be doing a great deal of programming, as I was going to be doing data catalog work against an old mainframe, something I had never tackled during my college years. Along with this, I was now a part of a seasoned DBA group that was not shy about picking apart developers who performed anything but optimal usage of the database. The group was comprised of a former programmer turned DBA, Kenny, who was very knowledgeable but tended to rip fellow programmers apart when they made mistakes, a fellow named Rod who was older and ran most of the office pools, and a man named Clark who was a little friendlier but kept to himself. Though I was feeling a little down at not being able to write code, I decided that I was going to make the most of my situation and pick up experience and skills in SQL from people who had made their living being experts at it. Since I had also recently decided to start following the Lord's call in my life, I also knew it was my job to bring a positive light to a team that could be less than friendly.
Soon after I decided to take this new approach to work, I started putting up a couple small post-it notes in my section of the team cubicle that contained scriptures that were important to me and talked of humility, working joyfully, and caring for others. This was initially met with some subtle criticisms, but at least started to get everyone talking. I followed this up with compliments to my teammates for their help as well as showing them how their advice was helping me along. I tried to not only give credit where it was due, but to be humble enough to show my deference to them as the experts. I believe this was quite a different approach than they expected a kid fresh from college to take, and we started to bond as a cohesive unit. Shortly after, I was dubbed "The Kid". I was building solid relationships with the guys, even Kenny, who started showing a vested interest in teaching me performance tuning tricks and gave me daily challenges in order to groom me as a future DBA.
A time came a little while later where Clark, who was not a spiritual person, casually mentioned his wife and daughter were taking a missions trip to an orphanage in Russia. He was half-heartedly asking for donations, and didn't seem to expect much of a response. It was then quite a shock to him when I gave him a check for $100, and told him that I hoped his wife and daughter had a safe trip. He was taken aback at this offer, and wasn't sure how to react. I could tell in that moment that he was really touched by this act of unexpected kindness from someone who had nothing to gain from such a gift. He made it a point to share with me pictures from their trip, and his interactions with me dramatically changed. Slowly, the group was not only teaching me things but sharing funny stories, and generally interacting with me in such a way that made work so much more enjoyable. They then started sending me to the local DB2 user's group, where I started gaining additional insight into how databases were used in the real world.
Along with trying to foster an improved team environment, I also used my resources at work to help those in the community. Since I was volunteering at a local cold weather shelter and I was working for a company that sold athletic apparel, I decided to see if I could get them to donate some shoes to those at the shelter. (If you have never been to a shelter before, you'll quickly realize that good shoes are among the most important things to have when you don't have any other means of transportation.) Through some research and after asking the site director for donations, I was ultimately able to get a new pair of shoes for every person at the shelter. Words don't accurately describe the way this brought smiles to so many people when I delivered them to the shelter. I immediately felt humbled at how little I cherish the many comforts I have been afforded and take for granted, when something like a new pair of shoes meant a great deal to someone in this situation. It was a feeling I will always remember. It wasn't long after that when I married and a couple of months later was informed I would be a father. Life had changed from uncertain and stressful to cheerful and rewarding.
Ultimately, I did end up leaving my first job to take on the development position I was initially hoping for, but I took with me great memories and relationships that made an impact on my current team as well. Again I'm the "rookie" on a team of seasoned developers, but my skills are growing, and I've started to make an impact here as well. I started doing ASP.NET 1.1 development when I took the position, and had to learn C# after being a Java programmer in college. I have since worked to hone my skills, and becoming an agent for change.
I have recently started attending the Central Penn .NET user group, and have been going to Code Camp events both in Harrisburg and Philly. I act as a representative for our group, bringing back details and resources to improve not only my skills, but those of the rest of the group. I was also able to successfully lobby for .NET 2.0 training as well as an upgrade from VS2003 to VS2005. All of this worked to break down some barriers that come from having a junior developer on a senior development team, as we all started discussing new things we were learning, and I started to feel like I had something in common to discuss. I have now become a resource for new ideas and concepts as I attempt to take in as much .NET content as I can, but I humbly realize after seeing the abilities of others in the field such as JP that my skills still require a great deal of sharpening. The passion I have for developing .NET code has slowly started motivating the group to investigate things it hasn't tackled before such as TDD, Agile, and XP. In the end, It is exciting to work with a new team, striving to increase my effectiveness as a developer as well as my capabilities as a positive influence. Though I am not sure this story is near amazing enough to warrant the truly awesome prize JP is offering, I hope it at least proves that every day you can make a difference in the lives of those around you, both as professionals and as people. It has been my experience that the differences you make when investing in people are extraordinary and mean just as much if not more than the mastery of our craft.
As you can imagine, the group filtering the entries had a hard task of coming up with the top 5!! All of the entries were truly awesome and I thank everyone for taking the time to enter their submissions!! Please complete the survey below to vote for the entry you like the most.
Develop With Passion!!