Thanks, Guys!

Within the past year, I’ve become part of a fairly technical leadership team.  This team is mostly made up of males, as the teams we leaders lead are mostly males.  While talking with one of the other team members, I got an interesting perspective.  The guys’ body language can definitely send all sorts of messages, and while some positions – like resting their arms on the back of their heads – can be intimidating to some, I remain unfazed.  While they may be positions of power or dominance, I’ve run with guys enough and have seen them do this and still challenged them anyhow.

This is one of many things I’ve learned from dealing with guys in the industry.  I am very thankful to have guy friends who have taken me under their wing and taught me tricks of the trade that I can use to get ahead.  I like that they will sometimes challenge me – be it with a puzzle or a “you can’t do that” remark – and then I’ll show them why they were wrong for challenging me in the first place.  When I have a problem, I know that I can go to them to get an honest point of view, without the gender factor getting in the way.

My recent experiences and discussions with people make me more appreciative of the community that I’ve worked with and that has shown me how I can continue to strive to be towards the top of the pack in our industry.  So to all of you out there who’ve been there for me and helping me grow in my career, I just wanted to say thanks!

The Lucky Charms Analogy

Yesterday, I mentioned how excited I was that I could use a cereal reference to describe programming. I am lucky to be working with a dev who’s learning ASP.NET, and there are times where things that come easily for me don’t necessarily come easier for her.  The reason why I say I’m lucky in that case is because I love being able to show people new things, especially when it comes to code.  I also have realized over the years that I have a special skill of being able to explain code in simple terms.

So this week’s conversation was about using an ASP.NET repeater and accessing controls within the ItemTemplate during ItemDataBound.  It can be a tough concept to understand, so I had to find a good analogy to get the short point across.  Sure, she could’ve followed the code I had for other pages, but I’d rather have her understand why rather than blindly copy-paste-and-adapt. So here’s how our conversation went…

Her: Why can’t I access these controls?

Me: Which?  <looks at her screen> Oh… these controls in the repeater ItemTemplate?

Her: Yeah.  I know I need to do this at ItemDataBound, but I can’t see the control.

Me: Think of it like a box of Lucky Charms. Those controls are like marshmallows.

Her: <puzzled look>

Me: As a developer, we can physically see the controls in the code.  Just like when we open a box of Lucky Charms – you can see the marshmallows in the bag of cereal.

However, you can’t just take the marshmallows out of the box.  There’s the cereal bag that holds them.

Her: <following what I’m saying so far>

Me: The ItemTemplate is like that cereal bag.  Those controls are in a container and you can’t just take them out.  You need to get to them by going through the container.

So e.Item is your container.  And to find that control that you need to populate, you’d tell the container e.Item.FindControl(“name of control”).

Her: <nods, understanding my random cereal analogy>

While the cereal box analogy can’t be used for everything, it helped in this case.