Wednesday, June 27, 2012


A sold-out crowd of more than 17,000 watched from the risers of the Wells Fargo Center in Philadelphia on March 19, 2011 at Arizona State University senior Anthony Robles emerged from the locker room on crutches.  After handing them to ASU assistant coach Brian Stith, he hopped to the corner of the mat, crouched down on one knee, and waited for the whistle that would signal the start of his final wrestling match.

"I told myself I was unstoppable," says Robles of that moment.  "I had put way too much into it to go in there and not come out with a national title."

That day, Robles, who was born without a right leg and permanently traded in a prosthetic one for crutches at the age of 3, defeated defending national champ Matt McConough 7-1 to become the first disabled wrestler in history to win a national college title.

By Alison Miller of Spirit Magazine

Wednesday, June 20, 2012


“The people at the Thunder repeatedly tell me that to this day, Kevin (Durant) practices like a rookie on a 10-day contract.”

-Alan Stein, founder of Stronger Team

Sunday, June 17, 2012


I take great pride in my blog posts of giving credit when possible to any information I pass along to you.  I think it's very important -- just like a score acknowledging a pass or a screen.  So many people have reached out and giving me information to share with others.  Unfortunately I have not idea where the information in this particular post originated.  Moving from one location to another, I am going through a lot of boxed and information and filing them away in my new office here at Texas A&M.  I came across this and read it not only once, but twice.  I think it's incredibly well-thought out and well-written.  It's good stuff and something I think you might want to share with your staff, your team and/or your family.  I just wished I could give the proper credit.

Being a Good Teammate

If you’re like most people, much of your professional life will be spent working on teams. Why? Because most projects that are economically interesting are too large and complex for individuals to do alone. Teams of talented people can accomplish great things that seem almost impossible, such as sending a man to the Moon. Such objectives would obviously be impossible if we had to work alone. Therefore, it is important that you learn to work effectively as a team member.

While teams allow us to accomplish far more than we could alone, there are also significant downsides to teamwork. As the number of people on a team increases, so does the amount of communication and coordination required to keep the team organized and moving in the same direction. Meetings, emails, phone calls, etc. increase, and these things take time. Also, the more people you add to a team, the more likely it is that at least one of them will be unreliable, antisocial, cranky, lazy, distracted, uncommitted, or otherwise difficult to work with. Such people take more energy from a team than they contribute, and often the team would be better off without them. You should try very hard to not be one of these people. There are specific things you can do to make yourself easy and enjoyable to work with. In the context of this class, here are some important things you can do.

Be reliable. Be someone your teammates can count on. Do what you say you will do. Attend team meetings. Complete the deliverables you’ve committed to produce (design documents, source code, etc.). Don’t be the one your teammates talk about behind your back as the one who just isn’t getting the job done.

Be early. Be on time to meetings. Get your part of the design document done early so your teammates will have time to review it and give you feedback. Get your code written and checked into Subversion early so your teammates will have time to see what you’ve done and integrate their code with it well before the deadline. If you get things done at the last minute, it will be very hard on your teammates, and your reputation will suffer. Part of getting your piece done is getting it done early.

Be prepared. Prepare well for team meetings. Read the specs before the meeting. Think about how you would solve the problem before the meeting. Have your part of the document done before the meeting. Whatever the purpose of the meeting is, make sure you are prepared for it. Such preparation will allow you to be a productive contributor rather than a drag on the meeting. If you show up unprepared, meetings will be longer because your teammates will have to bring you up to speed before the productive part of the meeting can begin.

Be responsive. Communicate with your teammates. Send frequent emails letting them know the status of your work. Send them your documents so they can review them. Check your code into Subversion early and often (every day or two) so they can see your progress and integrate with your work. It will make them feel a lot better if they can see evidence that you are making progress and getting the job done.

Don’t disappear for extended periods of time without explaining to your teammates what happened to you. If your wife is going to have a baby, tell them. If you get sick, tell them. If you have to focus on another class for a few days, tell them. Don’t just disappear for a week without explaining to your teammates what is happening. If you tell them what is going on, they will understand completely. If you just disappear, they will see you as unresponsive and unreliable.

If one of your teammates disappears without explanation, talk to your instructor quickly before the situation gets out of control.

Be careful. As stated above, check your code into Subversion early and often. However, don’t check in code that doesn’t compile. That will just make your teammates mad. Before checking in new code, do an “update” first to make sure you have all code that has been previously checked in by others. After doing an “update”, do a clean build to ensure that everything still compiles successfully. Once you know everything compiles, run all of the unit test cases to ensure that your new code hasn’t broken the unit tests. Once you know that everything still compiles and that all unit tests still work, then you are ready to “commit” your changes to the repository.

Be willing. Be eager in accepting assignments. Do your fair share of the work. Don’t always be


“The number one thing that I like about football. You need to have the whole team buying into that team concept. The part I like the most about it is when the whole team kind of loses itself for one common goal to win a championship. There is not a better feeling for me, especially after a Super Bowl, that you are the best in the world at least for that year and how collectively the team was able to accomplish that.”
3 year record at Penn State: 29-3
NFL: 4 Super Bowl Championships

Thursday, June 7, 2012


The following is conversation between Coach Roy Williams, then an assistant at the University of North Carolina and a young freshman named Michael Jordan:

When Michael Jordan first got to UNC, we were sitting at the track one day after conditioning. It was just the two of us. “Coach,” he said. “I want to be the best player to every play here.”

“You’ll have to work much harder than you did in high school,” Williams said.

“But, Coach. I worked as hard as everybody else.”

“Oh, excuse me. I thought you just said you wanted to be the best player to ever play here. Working as hard as everybody else is not even going to come close, son.”

That was the end of the conversation.

Two days later, after the next conditioning session, Michael comes up to me and we were sitting there alone again. He said, “Coach, I’ve been thinking about what you said. I’m going to show you. There will never be anyone who will outwork me.”

He did that. From that day on, Michael tried to kick everybody’s rear end in every drill.

From "Hard Work: A Life On and Off the Court" by Roy Williams