Fluff

Believe in Yourself

Believe in YourselfI often have no shortage of belief in myself and my abilities. When in doubt, I will always “bet on myself” when the chips are down to get things done. That confidence has allowed me to be very fortunate in professional settings. At times it can be misconstrued and at times I know that people can think that I don’t have any right to be as confident as I am. However, earlier this year, I read Ball Four by Jim Bouton and was really struck by this passage.

I’ve had some thoughts on what separates a professional athlete from other mortals. In a tight situation the amateur says, “I’ve failed in this situation many times. I’ll probably do so again.” In a tight situation the professional says (and means it), “I’ve failed in this situation and I’ve succeeded. Since each situation is a separate test of my abilities, there’s no reason why I shouldn’t succeed this time.”

Then there is also the case of the professional player who is not professional enough. He goes on a fifteen-game hitting streak and says, “Nobody can keep this up.” And as the streak progresses, his belief in his ability to keep it alive decreases to the point where it’s almost impossible for him to get a hit.

The real professional – and by that I suppose I mean the exceptional professional – can convince himself that each time at bat is an individual performance and that there is no reason he can’t go on hitting forever.

He is 100% saying how I feel about my potential for success in any given situation. Why not me? Why not now? Why can’t I do this thing? Why can’t I continue to succeed, or rally to success after a failure?

More importantly, why not you? Why not now? Why can’t *YOU* do the thing you want to do? Why can’t you continue to succeed, or snatch victory from the jaws of defeat?

You can.

Go do it!

Podcasts

Podcast Survey Results

Podcast SurveyLast time, I blogged about a survey I was running to collect information to help me craft the podcast that I want to start. The responses seem to have tapered off, so I closed the survey and I’m going to consider this data final.

In the interest of giving back, I’m going to publish the results here to help anyone else who might be interested in the information. I got 28 participants and here were their responses.

Do you listen to podcasts regularly? (Once a month or more)
Yes – 53.57% (15)
No – 46.43% (13)

How did you discover the podcast(s) you listen to?
More than one answer allowed
I don’t listen to podcasts – 25% (7)
Blogs – 32.14% (9)
Other podcasts – 21.43% (6)
Recommendation from friends – 46.43% (13)
Reddit/Hacker News/Similar Site – 25% (7)
Twitter – 14.29% (4)
Other – 17.86% (5)
(Included “Other” Responses: iTunes – 2 votes, radio/internet, search engines, Interests: Sci-Fi/Star Trek/Walking Dead/Tv & Movie Reviews)

How many different podcasts do you listen to?(Only 27 responses because I added this question after the first person took my survey)
0 – 33.33% (9)
1 – 7.41% (2)
2-5 – 37.04% (10)
5-10 – 18.52% (5)
10+ – 3.7% (1)

What is an ideal length for a podcast?
Less than 15 minutes – 35.71% (10)
15-30 minutes – 35.71% (10)
30-60 minutes – 17.86% (5)
Over 60 minutes – 10.71% (3)

What format/segments would be in your ideal podcast?
More than one answer allowed
Current Tech News Discussion – 39.29% (11)
Guest co-hosts – 39.29% (11)
Interviews – 39.29% (11)
Opinions – 46.43% (13)
Recommendations / Interesting Things Found Online – 67.86% (19)
Technology review (one topic per podcast) – 57.14% (16)
Technology reviews (varied) – 32.14% (9)
Other – 7.14% (2)
(Included “Other” Responses: religious topics, philosophical ramblings)

How frequently would an ideal podcast publish?
More than once a week – 3.57% (1)
Once a week – 50% (14)
Once every two weeks – 14.29% (4)
Monthly – 3.57% (1)
Whenever the muse strikes – 14.29% (4)
I don’t care – 14.29% (4)

So, to me, I do consider this survey a success. Even with only 28 participants, there are some decisions that I feel that I can make about the podcast.

First, I should aim to publish weekly (50%). Secondly, I should aim to keep it under a half hour (71.42% combined). One thing that I found surprising was that 67.86% of people said they would like a segment with interesting things that I’d found online. I really didn’t expect that option to come in that high.

The one thing that the survey confirmed for me is that I really need to try to encourage word of mouth support for the podcast to get it going. Over 46% of people found a podcast because of friends and over 32% found them from blogs (very similar – still a personal recommendation).

I’m going to take all of this information to the lab and hopefully I will start publishing a podcast next month. A huge thanks to everyone who helped or participated!

Goals

Starting a Podcast – Phase 0

PodcastI’ve toyed around with the idea to start a podcast for quite some time. I think the time for me to get started has arrived. I’ve created a survey to try to do a little market research that you can find here. If you would please take a minute to take the survey (it is only 6 quick questions), I would really appreciate it.

My goal is to narrow down a format and get 4-5 shows in the can and then publish them at whatever pace gets decided (one of the survey questions!) while making more.

I’m not looking to be “Hansel-famous”, I just want to put myself out there in the community another way and try to continue to grow as a technologist, a communicator, and a person. I’m taking Scott Hanselman’s advice (found here) and going to give this a go.

I would really appreciate if you would take the survey and help me make a podcast that people might want to tune in to. Thanks!

Business of Software

Decision by Procrastination

Decisions, DecisionsToo many times I see indecisive people put off making a determination because they are too scared to make the call. However, as the Rush song goes, “If you choose not to decide, you still have made a choice”. If you put off making a decision long enough, you end up with the status quo or the decision of least resistance.

I do know someone who uses that to their advantage and allows certain decisions to be delayed, knowing that they will ultimately not get made, and that the hare-brained plan will end up never taking off.

Don’t let that be you. Don’t live your life on the path of least resistance.

There is something to be said for making sure you have enough information to judge wisely, but more often than not indecision is about fear. Consider the data, think about the options and tradeoffs, include your experience and the experience of those on your team, and “shoot the three”.

Business of Software

Programming is Not a Zero Sum Game

Zero Sum GameSimply put, a Zero Sum Game is a situation where in order for one person to win, another person has to lose. Or, in order for someone to gain something, someone has to lose that thing. Think about poker. In order for you to increase your chips, you have to win them from the other players, decreasing their earnings. At the tournament level, the game ends when one player has everything and everyone else has nothing.

It seems that a lot of people try to treat programming/technology like that. I know the counter argument to that is that I’m blind and crazy. Haven’t I seen blogs and been to conferences and user groups? People are sharing knowledge all of the time. That is true and that is great. Unfortunately, those people aren’t even close to the majority of developers. The majority are the Dark Matter Developers, and they are what is out there*. Additionally, this kind of selfish behavior I’m describing has shown itself to be human nature in all areas of the workplace.

No matter what the industry, people are often reluctant to share knowledge with others. Sometimes they are afraid that if someone else knows how to do “their thing”, that they will be easily replaced by someone else – probably someone else making less. The key is that if you can be replaced over one or two things, you have larger issues. If someone else knows how to do the thing that you are holding on to, that frees you up to learn something else and grow your skills and your worth to the organization. If nothing else, the act of teaching something to another person will build your own “instruction skill”. Being willing to always teach others also makes you more valuable to your employer because it shows that you are a team player.

Besides job insecurities, another thing that will keep developers from sharing their knowledge is that they like being the only one to know things. I’ve met several people that fit this bill and I’m ashamed to admit that 15 years ago, I fit this bill. This one is pure ego and sadly, our community is known for some very big egos. If you are holding on to knowledge because you like being the keeper of that knowledge, you need to let that go.

When you were first learning, someone had to teach you. Even if you were “self taught”, you most likely read manuals/documentation, books, blog posts, Stack Overflow, attended conferences, user groups, etc. Most people did not gain their entire technology education by hacking around and figuring out 100% of things for themselves and never learning from anyone. I would wager money that if such a person existed, their code would be full of bugs, security holes, and performance issues because they’ve never learned what hundreds of thousands of “thought hours” have worked through.

If you learned from someone, teach someone else. Pay it forward. Pass it on. Give back. Mentor someone. Whatever you need to hear to get you motivated, hear it and act. Helping others ultimately helps you. If you’ll allow me one last cliche, “a rising tide lifts all boats”.

* Incidentally, I realize that this post may very well be preaching to the choir, since these Dark Matter Developers would probably not be reading this. My hope is that this post can be instructive, or at least serve as a reminder as you are out in the world to help recognize your own bias as well as the biases of those around you.