Team Culture

This past summer I was lucky enough to be witness to 2 really great teams. These teams were not both in sports, nor did they achieve any special recognition or accolades. One team was a group of girls looking to play softball over the summer. The other was a cohort of apprentices that really knew how to work together and bring each other up. In both cases I felt like the luckiest spectator to watch these teams do their thing and have so much fun doing it.

The Softball Team

So I will start with the softball team I coached this year. The team was made up of 14 girls of ages 10-14 (by the time games started) and we are stretching at least 4 different grade levels. In all accounts a recipe for chaos, cliques and players seeking individual glory, right? WRONG! DEAD WRONG in fact… I’d swear an outsider might think these girls were all sisters or something. They played as a team, they all seemed to get along and most of all they all had fun playing the game together win or lose. Alright maybe not sisters with how close they appeared without fighting, but you know what I mean.

In one specific instance the girls had just been rain delayed as the umpires saw lightning but it was not raining overhead. Where the other team scattered to the stands, dugout and surrounding area, my team was sitting in the right field grass in a circle playing a game together and enjoying the time away from the game as a team. They were laughing and playing and although they wanted to get back to the game they were happy to be with each other and having a change to have fun.

In another instance the girls were in the playoffs and playing their best. The game came down to a heartbreaking finish to where the girls lost the game and the right to play further for a championship. In one moment those tears of sadness turned to joy as one of the moms said, “Well, since we aren’t playing tomorrow how about a pool party”. Out of a possible 11 girls, 10 showed up the next day and stayed way longer than anticipated and had the time of their lives as a team. Even weeks later after the season had ended and was long gone, the girls got together again for a Lake Erie Crushers game and captured that same energy.

The Apprentices

My second story of culture is work related. I work as an instructor where I am leading apprentices through a difficult and challenging bootcamp to become Web Developers. This can be a very stressful time and can take anyone to the edge. There are many different personalities, backgrounds, ages, etc. coming together and really being forced together for 12 weeks. Under these circumstances you can’t expect that everyone will get along and you can’t ask them to. You can only hope that everyone can learn to be respectful and mindful of the others in the room. In most cases this works a lot like any office. You have the people you work with and then you go home and you don’t see them and are generally ok with that. This last cohort was a bit different…

Starting almost from the getgo, this cohort really communicated with each other. They would generally be quiet in the mornings but right around or after lunch you could hear the conversations on projects, ideas, and just general conversation. I have been very blessed in that each cohort has some level of collaboration. In this one it really started when one person went to the whiteboard during a work session and was like “OK, were going to design this application”. and then started to rally others to help with the design. I counted 5 people actively participating in the design, 3-5 more listening in and all the rest at least peeking to see what was going on from time to time. This style of collaboration where class discussions would drive productivity continued.

By the end of the cohort my .NET room and the JAVA room even fed off each other and just brought the whole place to a different level. It was amazing to watch. 12 weeks went by like 12 days. Today I am in my second day since they graduated and can’t believe it is over and they have become alumni. Many of them with jobs, many others with offers imminent. All will be missed.


I don’t know what I am doing to be around such great groups. This is just 2 instances. I could talk about many others from teams I have played on, places I have worked, even teams I have built. The one key to the success and the strong desire to not want to see those teams end is the culture of the team. Not only bringing different people together but bringing them together in such a way that they respect each others, learn from their differences and ultimately make life that much more fun.

How do you teach a group of people to be a team?

How do you convince them that life is much more enjoyable when you are part of the team and not out for individual gain?

How do you cultivate the culture that I have witnessed?

In talking with one of my coaches on the softball team he credited me with the culture and saying I created this. I did this… I didn’t do anything but take 14 girls, teach them softball and set a few rules at practices and games. If that somehow caused culture that I witness than by all means,

My rules:

1. You got to have fun… Softball by nature is a game. Games are meant to be fun. If you are not having fun you are doing it wrong…

In coding the same is true. Every application is a puzzle, puzzles are found near the games, games are fun therefore by virtue of proximity puzzles are fun and therefore so is coding…

2. Be safe… I told the girls I need them to understand the rules and why we have them so no one on our team or on another team gets hurt. No one is having fun when someone is hurt.

In work, being safe is the same. Why go out of your way to hurt someone. Be safe, follow the rules and contribute to everyone’s understanding.

3. Give it your all. Win or lose you have to try your best. If you give anything less why even try. Give it everything you have at that time.

With the cohorts the same is true. The apprentices pay to be there. Why wouldn’t you give it your all and do everything you could to succeed.

I really find it hard to believe I build these cultures. I am just the lucky guy that gets to be a part of them and see others flourish from them. Thanks to my experiences with the girls this year it sounds like I will be back to 2 teams next year for coaching and my next cohort is just weeks away.

I can’t wait…

Impostor Syndrome, my dealings…

I think the best way to start this is to define impostor syndrome. Impostor syndrome is the feeling of not belonging or feeling as though you are a fraud among others within a group, team or community. For me this is directly applied to my chosen career path in software development and more recently in the teaching and mentoring space. This is a feeling that I know all too well and for years have tried to hide and ignore these feelings. Here in this post I just want to talk about this a little and hopefully give someone reading this post a few ideas about how to deal.

So impostor syndrome, am I an impostor? I have felt this way from the start of my career. The first days being in a software development company I felt like I had no business in the building and especially no business working with developers, quality assurance or any other department. I was severely intimidate by the developers, even those just starting on the job. I always felt my skills were inferior and I would never be as smart, as good as them. I continuously felt like I was always trying to catch up and was just falling behind. Now as my career progressed this feeling didn’t really get better, I still felt the intimidation and the feeling of being inferior. The difference is that I didn’t give up trying and knew that even if I felt I wasn’t as good as them I could still contribute to the team in some way.

This is the first piece of advice I have: Find a way to feel like you are contributing

When you are contributing to the cause and you feel accomplished at the end of the day it is a little easier to get through each day and not worry about any feeling of being an impostor. In the course of my career I have always found those tasks and things that other developers didn’t want to do and did those. This would include things like resizing dialogs, creating sales demonstration forms, and writing preprocessors. Starting here allowed me to not only contribute but earn better tasks as time passed.

Next I would tell someone Never give up learning

If you are forever a student, whether you are at someone else’s level or not, you are willing to put in the time and effort to learn you belong. I am a firm believer that you are never done learning. Anyone willing to learn and continue to grow has a place on a team somewhere.

The surprising thing is that Others feel the same way

I am currently working with some of the top people in the field, mentoring and training developers. I was SHOCKED to learn that some of them have this same feeling. I was especially taken back when a coworker admitted to this feeling when I felt it around them. Although never directly working with them before I never would have guessed they felt this way. The more I am around my coworkers the more I am trying to find ways to impress and just meet their level of knowledge. I constantly feel like I am going to be found out to be fraud. Knowing they feel it too I think this has given a level of acceptance of this feeling and knowing that this feeling is not unique to me.

Feeling like an impostor doesn’t make you any less worthy of the title you have or the right to do what it is you do. Feeling like an impostor may even help you stay humble and hungry for more knowledge. I currently use this feeling to learn everything I can and at least stay in the conversations around me. I try to learn a little of everything and dive deeper where I can to really make a good contribution.

This probably leads to my last piece of advice Find your niche

Finding something to specialize in is always a good idea. Also don’t be intimidated when someone else has the same knowledge. Instead use them to bounce ideas off of and figure out how you can further the knowledge even further. Even then, they probably know some things where you know something else in the topic and together you have a more well rounded knowledge.

Hosting ASP.NET on Shared Hosting Site

Within the last few weeks I decided to take the venture of moving my host provider from one web hosting company to another. At the same time I decided that I wanted to do Windows hosting going forward so that I could host ASP.NET applications. I figured this would be easier since I know more of C# and .NET than I do PHP and the linux web hosting technologies. Boy, was I wrong…

So the first issue was with the domains. Normally when you transfer domains from one provider to another it can take up to 7 days. For some reason one of my domains transferred in what felt like hours. Instead of a week I received the email that the domain transferred in a day or two. Although I received an email that the domain transferred and it showed on the new provider, the old provider also still displayed the domain. Thus when I deployed my new website and all the files to the new provider it would sometimes display the old provider. Awesome times…

Once that was straightened out my new site starting throwing a 403 – Forbidden error anytime that I browsed to the page. The 403 error seemed consistent but then when I deployed my solution would work and I could browse to the pages without issue for a few minutes until the 403 error would resurface. Contacting the host provider the 403 error appeared to be caused by settings on the server. This lead the provider to ask me to change several things in my web.config file as well. This included code to add the following:

<modules runAllManagedModulesForAllRequests="true"></modules>

This seemed like a bit of overkill. This also did not fix the issue either. Instead the error continued and given that this didn’t seem to work, I reviewed other solutions and suggestions made online and replaced the above with:

<remove name="UrlRoutingModule~4.0" />
<add name="UrlRoutingModule~4.0" type="System.Web.Routing.UrlRoutingModule" preCondition=""/>

Although this code seemed to directly address the issue, it didn’t work either.

The issue at this point was diagnosed to be with ASP.NET and more specifically the MVC routing within. None of the views were being properly executed and the controllers were never being reached. No matter what I did the error would not cease as every time I deployed it worked for a while and then around 30 minutes later it would go back to 403 – Forbidden.

The issue turned out to be an issue with the precompile setting on the publish settings dialog. Below is the settings dialog.

Visual Studio 2015 Publish Settings Dialog
Visual Studio 2015 Publish Settings Dialog

The second checkbox was causing the issue. For some reason checking this box would cause a security issue that would prevent the MVC Routing for executing properly.

Maybe next time I will realize the shortcut isn’t worth it…

Paying It Forward

I have to admit that the following was not a planned encounter, the intention was not to use or teach the things of this course to anyone initially. Instead I was asked by someone for some advice specifically in regards to organizing one’s thoughts, managing tasks and time management. Without even realizing it I started reflecting on this course and the portion where we learned about Nozbe and keeping task lists and getting organized. My first reaction in the case where someone asked me how to get focused on the task at hand was the exercise we did where we wrote down everything we were thinking about at the time. I can remember getting in front my whiteboard and later a piece of paper and just writing everything I was currently thinking about down. I told them to try this. The result for me was a sense of relief since I no longer had to think about everything and could refer back to the list.

This technique alone is one that I plan to use with many people who constantly ask me how I am able to manage my daily tasks and make time for extra curricular activities. It is very neat trick that really did free my mind to focus on what I needed to. Once written I could review the list, organize the list and even prioritize the list. This made it easy to see what really mattered and what I could put off or what I really didn’t need to worry about.

Given my current position teaching in a bootcamp and the amount of tasks we throw at each apprentice I see this as a great way to pay it forward. I can help those apprentices that ask by sitting through this exercise with them, getting them started down the path and then I plan to follow up with them from time to time to see how things are going. For those that I have already started I plan to look in on them this coming week and see how things are going.

Thanks unstoppable for a great tool in my arsenal…

My Final Set Point

So this weekend marks the end of the Unstoppable Journey for me. I have been working to try and get caught up with a few of the blog posts and what not and really reflect on what this journey has meant. In this post I am going to rehash some of the previous points and see how things have changed over just these 12 weeks or so.

My Stand
My stand is really about being a positive force in this world. I want to avoid the unnecessary drama that surrounds matters, focus on what does matter and try and help those struggling overcome challenges and obstacles. I want to provide the advice and experience I can to those willing to listen and help shape the world for the next generation.

My Passion
My passion is really about programming, sports and mentoring. I love exercising my mind with learning more and more about the craft I have chosen for my life. I love picking up new programming languages, frameworks and bring ideas to reality through code. I also still love my baseball and being able to play each year. I look forward to taking that mound every opportunity I get. In both of these I love sharing my experiences and helping others learn what it is that I love so much. It brings me great joy to share this.

My Purpose
Change the world one line of code at a time sharing my journey and experiences along the way.

My Values

  • Continue to learn with each day
  • Always will myself to succeed
  • Mentor and be Mentored at every opportunity
  • Reach others through empathy and compassion
  • Be creative
  • Be passionate
  • Be Positive
  • Put my whole self into each task
  • Enjoy each day striving to make a difference

Short Term Goals
In the short term I hope to reshape how I spend my days and especially my free time. It is my goal to start focusing on my passions more and not be so easily distracted. Giving more time for the things I really enjoy doing should result in greater results than if I continue to go in multiple directions. Here are a few of the short term goals.

  • Write code 10 hours a week
  • Post one technical blog post each week
  • Run more miles than days in a given month
  • Play all 9 positions in a baseball game this year
  • Start Drawing one hour a week, every week

Dream Goals
Dream goals of mine would be things such as traveling and doing things I didn’t think I could still do. For instance on traveling, I would love to see the BaseBall Hall of Fame, Fenway Park, Wrigley Field and not related to baseball I would love to travel to Ireland and see the old castles there. I would love to walkrun the long endless fields that I see in pictures and not have to worry about work or deadlines or anything but the cool breeze off the ocean.

Overall, I have seen more of an evolution of the different aspects of this course. I always knew many of these things but the ideals are becoming much clearer. I can’t wait to see how this comes with me passed this course.