Taught my first karate class all by myself

I’m getting ready to test for 1st kyu, again, for the third attempt (first two attempts failed due to injury).  Yep, the rib has healed, and I’m back to running 3 miles 2-3 times a week.  I started going back to karate last month, only attending once a week, and this past month has been twice a week, so I’m definitely taking it slow.  I feel really good about Wed’s night’s exam.  Warm weather is always a friend of mine.

I show up for one of the classes usually intended for lower rank this week, because I couldn’t stay for the later advanced class.  And the sempai (teacher) doesn’t show up.  So, I gave the prof the 10 minute rule, and started class.  It was the first time I had ever taught a class all by myself.  I focused on the beginning katas, pointing out things that separate a good kata from a great kata.  For example, I had them practice looking and then doing the next move, something you really have to get students used to doing as early as possible in their kata training.  Since it has been so warm out here (notice I say warm – in Mississippi right now, it is hot, so I dare only say it is warm out here), I did a lot of talking. 

Everyone said they enjoyed the class.  I’m sure it was a lot different than the regular class, just because it was someone different with a different view / interpretation on things.  What stressed me out was when the advanced class students and teachers started arriving and watching me teach class (these are folks who out rank me).  I kept looking at the teachers thinking, “When are they going to realize I’m not a black belt and take over for me?” but they never stepped in.  After the class was over, I explained why I was teaching class, and they said, “oh, we thought you were assigned to teach class tonight.”  I took it as a nice compliment.  I love teaching, but next time I want advance notice so I can put together a lesson plan =)

How le Tour de France works – everything beginners want to know

I’ve been asked this question so many times this week, and now I just heard it asked by the guest on tonight’s The Daily Show.  Why didn’t you school him Jon, why?  But I have to give the daily show credit for Monday night’s episode about Lance.  It was pretty funny, the epitome of “tongue in cheek” humor.  I’d love to see Lance as a guest on the show.

If you wonder why I care about le tour so much, I was an exchange student in France when Lance won his first tour stage (the year before he found out he had cancer).  I’d collected many newspaper and magazine articles about him while I was over there.  When I got home, I put his first stage win photo up on my wall in my bedroom (I was 16), knowing one day he would be my hero.  So, that’s why I wear the yellow armband – because Lance is my hero.

Questing: “How can Lance not win everyday or most days, but win le Tour overall?”

Answer: Because le Tour is based on overall time.

Wikipedia Answer: http://en.wikipedia.org/wiki/Tour_de_France

My Long Answer:  There are usually 180 riders participating in the tour each year.  Maybe 150 of them cross the finish line in Paris – I’m too lazy to look up the actual numbers.  But people usually drop out of the race because they get hurt or exhausted and have to abandon the race – you try riding 100 miles at one time, much less 100 miles a day for 20 days.   There may even be a time you have to finish each stage by; otherwise, you get dropped.  But if there is such a rule, you don’t hear about it often because none of the top riders are in this risk – unless there’s a crash and they get hurt.

These athletics are in such top condition that whenever the race is flat, the top 80% (once again I’m making up numbers) finish at the same time.  But introduce the mountains, the different categories (lower numbers mean more difficulty, until it is beyond category, meaning I would have a hard time trying just to walk up that hill), and the day after day battles of trying to get up those hills, the race becomes interesting.  Only your top 5-10% will be able to stay together, and even after a while, they’ll fall away from one another.  This is where Lance excels.  “The Look” picture from Stage 10 of the 2001 tour says it all, where he sees everyone behind him in agony, stares them down for a good several seconds, and then just explodes away.

Just because a cyclist wins a stage one day, or even a mountain stage, by a large amount of time, doesn’t mean that he’ll be able to produce the same amount of energy the next day.  Teams pick their battles very, very well in deciding which day their primary rider will go all out to win a stage.  What causes Lance to always finish in first place day after day is that he always sticks with his rivals on Overall Classification (GC).  And if someone starts winning stage after stage, he’ll most likely become a “threat” to Lance, and he’ll get marked by Discovery as someone Lance needs to stay with.  And if this threat were to breakaway, Lance would chase him down.

For some teams, their entire job is to just win one stage.  Or maybe it is to do an effective breakaway such that their sponsor gets as much air time as possible.

Each team has a primary rider whose job it is to achieve whatever the team’s goal is; whether it is to win the stage or win the tour.  All other team members (7 or 8 – I’m so lazy not looking up numbers) do whatever it takes to help the primary rider achieve the goal.  These guys will go back to the team car to get food, water, etc.  They will also draft in front of the primary rider for as long as they can and provide whatever assistance.  Consider what happened to Lance in 2004 tour.  He’s handlebar got caught on a spectator’s bag and he crashed.  His teammate immediately jumped off of his bike and ran over to help Lance get back up and going.

Drafting – another concept people don’t realize has a major role in cycling.  Drafting is when you get so close behind the person in front of you that you get pulled along in their air.  We’re talking about being an inch away from the person’s rear wheel.  You can feel the same effect in a car drafting behind an 18-wheeler, although I do not recommend you practice this.  But using this scenario, you would experience better gas mileage.  Drafting in cycling: good.  Drafting in sailing: bad (you don’t want to get bad air, or you won’t have enough air in your sails, and you’ll slow down).  The role of the team member is to allow their primary rider to draft behind them, so they can conserve their energy for the very end.

You’ll notice on time trials how the race car and motorcycles have to stay very far in front of the cyclist; otherwise, drafting may occur, providing an unfair advantage to that cyclist.  Each rider must face the wind; no drafting allowed on time trials.

And lastly, what the jerseys mean:

White – this is a new jersey introduced in the past several years.  It is awarded to the fastest overall rider under the age of 25.

Green – best sprinter.  Throughout the tour, there are different “checkpoints” that the first person to get past wins a certain number of points.  The person with the most points throughout the tour wears the green jersey.

Polka Dot – King of the Mountain – best climber.  Usually based on a points system like the Green jersey.

Yellow Jersey – see Lance.  Overall leader in the tour.  If the overall leader is a young rider, he’s awarded both jerseys, but he wears the yellow on the road

View original comments

Did you know… How to modify what gets saved before building?

Go to Tools – Options – Projects and Solutions – Build and Run page.  The first combo box is Before building: with the options to

  • Save all changes
  • Save changes to open documents only
  • Prompt to save all changes
  • Don’t save any changes

I’ll follow up with another tip of the day on how to use pre and post build events.

Happy Visual Studio’ing!

Looking for Visual Studio .NET 2003 Tips and Tricks? – here’s a book for you

Minh Nguyen wrote a collection of Tips and Tricks for 2002 and 2003, with some 2005 Beta 1 tips too.   The book’s called Visual Studio .NET Tips and Tricks.

The book covers

  • Editor and other IDE tips
  • Compiling and Debugging tips
  • Miscellaneous .NET tips and tricks

Many of the generic tips (like Editor and other IDE tips) apply to 2005.  I’m always collecting tips and tricks for this feed from my team and what other bloggers (both MS and customers) are offering as tips, so this book would be a good supplement if you enjoy reading this feed.

Happy Visual Studio’ing!

Accessibility and Interviewing

Gretchen is curious what your experiences have been like, either as the interviewer or interviewee.  It makes me wonder how I would give a coding problem to someone who is blind, because I’m extremely visual and like looking at code on the whiteboard.  I’m not the best at recording everything down verbatim as I hear it, mostly because of my learning style.  Don’t get me started about the time I attempted to take drive-food orders at the Taco Bell in my youth.  I was talking to someone the other day about coding problems given over the phone in a phone screen, and we discussed how difficult that would be for both the interviewer and interviewee.  This phone screen example reminds me of how I think of accessibility and usability as two sides of the same coin.

Anyone have any experiences along these lines, blind or not?  I’m sure Gretchen would love to hear.

View original comments

Did you know… How to optimize your Tool Window Debugging layout

If you’re dealing with callstacks only 5 lines deep, you’ll probably like the current layout – docked to the bottom.  However, if you’re dealing with callstacks 20 lines deep, you probably want to be able to see more lines without wasting your Editor real estate.  I’ve seen most of our devs, okay, maybe all of them, tab-dock the Callstack Window with the Solution Explorer.  (that’s tab-dock: where only one tool window in a group can be shown together versus side by side).   Now you’ll be able to see many more lines in your callstack window without losing your Editor window.

Another tip I got from one of our devs is to have the following layout on the bottom of the IDE:
Local + Watch + Breakpoints + Immediate

Let me know if you have a favorite tool window docking position you want me to call out as a Tip of the Day!

Happy Visual Studio’ing!

Did you know… How to have fun with MSO Command Bar Customizations you didn’t know existed

Well, maybe you knew these existed, but I didn’t =)

Double-clicking the Move Control
On the left-hand side of the toolbars, there’s a resize / move control.  When there are two or more toolbars together on the same row, you can use this control to resize the toolbar.  You can also double-click the control to show the entire length of the toolbar.

Making Multiple Copies of the same button or menu
While you have Tools – Customize showing, you can do a Control+Drag to make multiple copies of the same toolbar control or menu item.

Resizing Edit Fields
While you have Tools – Customize showing, you can resize the edit controls on any toolbar.  First click on the toolbar to get the black box drawn around it.  Then, mouse over the left or right side of the box, and the mouse pointer turns into a resize pointer.

Happy Visual Studio’ing!

Did you know… How to optimize Visual Studio for Multi-Monitor setups

Update 7/20 @ 11:53pm: We have a bug:  Please vote and leave your suggestions / feedback at http://lab.msdn.microsoft.com/ProductFeedback/viewFeedback.aspx?FeedbackId=cf3597fc-2acf-43c7-b09f-a7e1dd7474f5  Many thanks ShadowChaser!

Update 7/20 @ 9:20pm:  As i mentioned below in the comments, i think the best course of action is to have one of y’all (our customers) report a suggestion via MSDN Product Feedback and let me know what the bug ID is, so everyone can vote.  (if i were to raid it, you wouldn’t be able to see it to vote on it).  Please either email me and/or leave a comment below with the Bug ID, so i can let everyone know how and where to vote.  A big thank you from us multi-mon users!

Last year, I did a very informal survey on how many people out there use Visual Studio on Multi-Monitor displays.  Now that we, the blog authors, have control again over how long comments are open, I’ve reopened the comments so you can still leave your feedback.  But for now, here are some tips on how we use VS on multi-mon setups in house.

Stretching the VS across dual monitors

Go to a restore state, and stretch VS across dual monitors.

One of the benefits of doing this is to be able to view code in each monitor.  You can do a vertical split (Window – New Vertical Tab Group) down the center of the dual monitors.  Now you can have code windows on each monitor.

You can also customize the toolbars to place them on which ever monitor you prefer as your primary.  Just grab the grip control for the toolbars and drag them over to whichever monitor.

Viewing Debugging Tool Windows on secondary monitor

Whenever I’m debugging, I prefer to have the following tool windows like the Watch Window and Output Window on the secondary monitor, with VS occupying the primary monitor.  These tool windows have to be either dockable or floating (floating is what you probably want).  Resize these windows to occupy half of the screen.  Remember, you can use Tools – Import / Export Settings to save your favorite window layouts.  And since these windows only appear during debugging, you don’t have to worry about them occupying your secondary monitor when not in use.

Place External Help on secondary monitor

Dexplore, the Help Viewer, can be placed on the second monitor for a pleasurable help experience.

What other tips should I include in this entry?

Leave a tip as a comment and I’ll update this entry.

Happy Visual Studio’ing!