Nerd Guru

Because technical people need good soft skills to get ahead.

Thursday, February 07, 2008

Just when you think you're getting good . . .

There have been times in my career when I think I'm getting pretty good at what I'm doing for a living and then . . . I find somebody that is way, way better. Sometimes it is somebody that is a lot better in a totally unrelated field, but either way, I tend to have one of two reactions to this realization: give up or get inspired.

On a much, much less important scale I experienced this sensation recently while tinkering with one of my Christmas presents from my wife: a Rubik's cube. As a child of the 80s, I had one during my Junior High School years when they were first popular and got pretty decent at it. With my new present in hand this past December, I found I remembered the basic moves for solving the first three layers (a top face and the first two rows of the faces perpendicular to that top face), but that I needed some help with the last two layers.

During my recent travel from hell, I worked quite a bit with my cube and ultimately did it once in 2 minutes and 30 seconds, a good minute and a half better than my best time as a twelve year old. I was feeling pretty good about myself until I saw this:



I will never, ever, ever be as good as this. Two opposite thoughts immediately crossed my mind when this became clear:

1) Quit cubing because if I can't be the best, I might as well not try.
2) Learn as much about this guy's techniques so I can be the best cubist I can be.

The first impulse is the easier one to follow, but also the least satisfying. The second requires work but helps my own personal achievement which perhaps I shouldn't always measure against others. The first idea leaves me in awe of someone else to the point where it paralyzes my own journey while the second inspires me to try harder even if I never reach the level of expertise of Jean Pons.

More times than not, choose the second path.

There are certainly times where it makes sense to quit something (I doubt my wife would want me to devote my life to speedcubing), but choosing to become inspired and finding how you might mimic techniques to at least improve your current standing is a whole lot more productive. Finding a way to improve, even if your example comes from a completely unrelated field, benefits you in the long term.

For my little cubing hobby, I'm already learning that some cube solution theories require fewer turns than others and that if you can lubricate your cube enough so that turns can be made on the strength of your fingers, as opposed to your whole hand, you can speed up your times significantly. Those optimizations weren't obvious to me at first and I'm taking a step backwards to learn these things before I get the anticipated benefits of beating my best time. I'll never solve a Rubik's cube in 12 seconds, but I'll do better than 2 minutes some day and appreciate the different approach to solving the problem that I discovered in the process,.

On a good day, I bringsuch thinking to my daily activities too.

Labels:

 Was that interesting or helpful? Consider subscribing:  by reader  or   by Email

posted by Pete Johnson @ 10:01 AM   2 comments

2 Comments:

At 12:11 PM, Anonymous Anonymous said...

Funny, this is the second Rubik Cube related article I come across this week.

Here's a guy documenting his algorithm:

Instructables

 
At 6:44 PM, Blogger Pete Johnson said...

That's actually the same technique I use, which anybody into speed cubing would tell you takes too many moves. Still, its requires the least amount of memorization. Nice video link Esmit, thanks.

 

Post a Comment

   Subscribe to comments in a reader

   Subscribe to comments by Email

<< Home

Thursday, February 22, 2007

Random Thought: Calendaring 101

It’s pretty common these days, especially in larger corporate settings, for some online calendaring tool to be used to help people in all kinds of jobs manage their schedules. This used to be a complete nightmare when everybody kept their own schedules in some paper-based date book (or, for the big wigs driving company cars, their administrative assistants). You had to call everybody who you wanted in a meeting and ask them for times that worked for them. Then you’d have to collate the responses you got back and send out a memo, electronically if you were lucky. The more people you had, the task became exponentially more difficult.

Through the magic of software like Microsoft Exchange and Outlook or something similar, you can see the busy and free time of any body’s calendar you want with a few mouse clicks. Typically you can’t actually see what they have booked, but you can see if their time for a particular block is available or not. For example:


Click on the picture above for more detail on the "Scheduling" tab for this fictional proposed meeting. The time being suggested (from 8 to 9 am on Wednesday, December 27) does not work or all three people who this invitation has yet to be set out to yet. Specifically, Al Czervik is already booked for this time.

Despite these advances, not everybody has mastered the use of this tool. These might seem obvious, but when scheduling a meeting keep a few of these things in mind:

  • Actually check everybody’s schedule before sending out a meeting request. You might be thinking, “duh, why wouldn’t you do that?” but keep count in the next three months of how many times somebody schedules a meeting on top of a time that you already have blocked out and is surprised when you decline the invitation. It happens to me weekly.

    If you cannot find a time that works for everybody you need, try the time that works best for the most number of people. Then, in the meeting invitation explicitly state something like, “I know this time doesn’t work well for Anakin and Padme, but this was the best fit for everyone else.” Then ask if the people who are booked can either reschedule their other commitment or send a designate in their place. This way, everyone knows you at least tried to accommodate everybody and people are left feeling better about you than if you say nothing, leaving the impression you intentionally excluded some people.


  • Be sensitive to time zone where you can. A 9:00 am, Pacific meeting is right at lunch time for someone in Eastern. Similarly, nobody from the west coast will look forward to a meeting that starts at 8:00 am, Eastern. Most of Europe is on Central European time and 7:00 am to 9:00 am Pacific still works for people there most of the time. Asia and Australia can be tough given that in some places there can be a 12 hour time difference, which means somebody is getting up early or staying late. You can’t always accommodate everyone, but at least keep it in mind. There's a good online time zone converter here.


  • Be sure to send on any meeting logistics with the invitation. This might be the location of the meeting room, conference call dial in number for people attending remotely, or desktop sharing information. Arranging for this later might cause for someone to miss the information and not be able to attend.


  • If you find yourself in constant meetings and don’t have enough time to complete your “normal” tasks, a good trick is to take some free time on your calendar a week or two in advance and block it out for use on your tasks. Anyone who tries to schedule a meeting with you will see the time as busy and pick another time. If they then ask you if you can be flexible, you get to choose whether or not you are.


All of these things contribute to demonstrating to others that you are considerate of their needs, which can be a big help come performance evaluation time when your manager starts asking around about what you are like to work with. Follow these guidelines and you make it easier for your coworkers to provide a positive response instead of giving them ammunition to complain about you when that time comes.

Labels:

 Was that interesting or helpful? Consider subscribing:  by reader  or   by Email

posted by Pete Johnson @ 11:43 PM   2 comments

2 Comments:

At 10:16 AM, Anonymous Anonymous said...

A couple of related comments....

Intelligently choosing to Tentatively accept an invite can go a long way to helping others find a time to book a meeting that includes you. If you know your attendence is a pretty low priority, or it's a recurring meeting that really only occurs when necessary, or a company presentation that will be recorded for later reply, etc., etc., etc. choosing to Tentatively Accept it works well.

Also, on many of these invites, it's possible to include some people as "required" and others as "optional". Using "optional" for people like manager's or others that should be aware that the meeting is occurring, but don't need to attend is a nice way to keep them informed.

 
At 11:38 AM, Blogger Pete Johnson said...

Great point on tentative acceptance. I agree, that can help quite a bit.

I like using optional vs required too, but sometimes find that people don't look carefully enough at which list they are on inside the invitation. I wish Outlook would have a slightly different icon (color difference maybe) when an invitation shows up in your inbox to distinguish between those two states.

 

Post a Comment

   Subscribe to comments in a reader

   Subscribe to comments by Email

<< Home

Tuesday, February 20, 2007

Random Thought: The evils of slang in an international work force

As I've mentioned before, the organization my boss runs has about 100 people in it. What I haven't mentioned before is that those people are spread across the US, France, UK, India, Mexico, Canada, and Costa Rica. Needless to say, it is a real life example that more than ever before, work forces are becoming globally mixed. This can create some awkward situations when it comes to word choice. For Americans in particular, since we tend to use a lot of slang in our everyday speech, it can lead to sometimes unwanted results.

Even though English is often a de facto standard language in international business situations like the one I work in every day, in many cases you have to be prepared to deal with variations on language and catch-phrases. For example, in reference to a particular aspect of a project someone in some parts of India may say, “I have a doubt about the Ataru focusing crystal lens assembly you sent me.” To an American, that may sound like the person in India thinks that it is a bad idea because of the way the word “doubt” is used. To the contrary, what that phrase means in India is that the person is having trouble getting the equipment to work in their local environment correctly.

Similarly, use of slang terms can easily confuse others with different cultural backgrounds. When in a long meeting, an American might suggest a “seventh inning stretch”, which would mean absolutely nothing to someone in a country where baseball is not played. Most of these interactions are innocent and can lead to a good laugh, but be careful. What is humorous in one culture may be offensive in another.

Famous slang gaffes from my career:

  • When a colleague who was raised outside the US was describing to me a case where a coworker was trying to get him into trouble with upper management, I said, "That guy is such a tattler." It took me nearly 30 minutes to come up with a better explanation than, "A tattle tale is someone who tells tattles."
  • During a design review teleconference for a new website, I was struggling to comprehend a key point that one of the engineers who works under me was trying to make. After a third explanation, I realized that I had missed a very simple point he had made at the beginning of his argument that was the basis for everything else. I apologized for "being a Bozo". He acted like he knew what I meant by the comment, but was secretly looking it up on Wikipedia as we continued our discussion.
  • While discussing a technical point with someone once, I dismissed a particular programming choice by saying, "I know some people like it, but I think it's BS." The guy I was talking to understandably thought that BS was an acronym for a web site technology.
This one didn't happen to me, but was told to me by the gentleman who was the victim of my Bozo comment above. He had just moved to Texas and coworkers in the general vicinity of his cube at midday often say, "I'm fixin' to go to lunch." Needless to say, it took him months to figure out that there was nothing broken about lunch to begin with.

All these examples are harmless, but the point is that it isn't difficult to make a culturally ambiguous mistake and really annoy somebody by accident. Be sure to define terms clearly, avoid slang where possible (something I have trouble holding myself to), and try to put things in a couple different ways to make sure your intent is being received the way you think it is. If you work with people from all over the globe, those same people will likely have input on that all-important performance evaluation and, as such, communication points outside the country you live in deserve careful attention.

Labels:

 Was that interesting or helpful? Consider subscribing:  by reader  or   by Email

posted by Pete Johnson @ 8:03 AM   0 comments

Tuesday, February 13, 2007

Random Thoughts: Restrictions breed creativity

Ever feel like you could do more if only you had a higher budget?


Think things would be better if management or prior work hadn't shackled how you really wanted to do things?


Wish you could take advantage of that cool new technology, only it's not approved for use by your company yet?


We all run into restrictions during the course of a project and they are usually the source of a lot of frustration. Limiting factors can make things more complicated than they otherwise would be, but they also breed creativity. Such was the case in the 1960s when Disney Imagineers began to expand Disneyland.


Most people have been to a version of the Haunted Mansion at a Disney park somewhere in the world. You are led into a dark, creepy room. The Disney cast member closes the door and a recorded spiel begins to tell you that the parlor you just entered is inhabited by 999 happy haunts (there's room for 1,000, any volunteers?). The walls of the room depict previous guests in paintings. The lights get dark, there are scary noises, and then the room appears to stretch.


It's a cool effect that sets the scene nicely before you proceed onto your "doom buggy" for the remainder of your ride, but did you ever wonder why the room stretches? It isn't for the sake of the effect, as you might expect. A key restriction in the original version of the ride at Disneyland in California is why. Disney Imagineers used a physical limitation they could not change to come up with an effect that turned out to be a trademark of the ride and duplicated in other versions despite the absence of the same pre-existing problem.

From an early age, Walt Disney was fascinated with trains. So much so, he had a well-known and very elaborate scale model train in his back yard for many years before Disneyland's opening in 1955. When the plans for a theme park were being created, among the things that Walt insisted upon was that their be a train route that encircled the park.



The effect of this is that the train track, which can be seen in Figure 1 as the inner circuit that encompasses park (the outer one was a service road that no longer exists in its entirety), restricts the amount of real estate available for attractions. As Disneyland began to expand, this space limitation became a problem.

For the Haunted Mansion, the stretching room provides the solution. The room doesn't stretch up as the visual illusion would have you believe. Instead, the entire room is great big elevator that takes guests below the elevation of the train tracks. As you enter or exit that room (in the California version), look down and you should be able to see a noticeable elevator threshold.

The hallway that connects the stretching rooms (there are two of them) to the doom buggy loading area runs directly beneath the railroad tracks. Once you are loaded into your buggy, you are in a structure that is outside the bounds of the railroad tracks for a majority of the ride. This approach is used in several places throughout Disneyland to maximize space inside the tracks without limiting the size of the attractions.

The stretching room effect proved to be so popular with guests, it was replicated in all other versions of the attractions despite the absence of the train tracks limitation. At Walt Disney World's Magic Kingdom in Florida, for example, the room really does stretch up to achieve the same effect.

When you have unlimited resources, you can afford to be sloppy with your designs. Restrictions introduce a set of rules that you cannot change and are forced to be creative in order to come up with a solution. In many cases, as what happened to Disney Imagineers when designing the Haunted Mansion, this forces you to come up with a better solution despite the limitations being placed upon you.

Labels:

 Was that interesting or helpful? Consider subscribing:  by reader  or   by Email

posted by Pete Johnson @ 8:53 PM   0 comments

Sunday, February 11, 2007

Random Thought: Eddie Murphy on taking advice

A recurring theme in this space is to observe and analyze successful people. Because Biography rarely delves into the stories of people like the guy who invented the sliding glass door, we're exposed to entertainers more than anything else.

By anybody's measure, Eddie Murphy is a successful entertainer. A huge hit on Saturday Night Live before his 20th birthday and a crossover to movies shortly thereafter, he's been a prominent figure in the entertainment business for 25 years. During his promotional tour for Dreamgirls in December, 2006 he made a visit to Inside the Actor's Studio.

Usually when you see Eddie Murphy on a talk show, like with Leno or Dave, he's playful with a hint of cockiness. Like a lot of people who sit opposite James Lipton, he was almost all business during this particular interview. Stoic much of the time and, as the environment tends to foster, very reflective of what he's done with his career, Eddie was very different than every other time I've seen him plug a movie. Throughout the main part of the show with Lipton, he made multiple references to studying the successful aspects of those who had come before him. He made the expected references to people like Richard Pryor and Bill Cosby, but it is clear he does his homework based on his other comments. For example, he went as far as to admit stealing aspects of certain performances for his own such as Charles Laughton's Hunchback of Notre Dame and its influence on Eddie's version of The Nutty Professor.

During the student question section, though, he said something very interesting about advice. He was asked a variant of the typical question, "What advice would you give to an up and coming actor?" Here was his answer:

"The advice I would give an actor is not to take any advice from anyone. . . When you make that choice [to be an actor], you know it and you know what's in your heart and you know what you want to do and you know what your abilities are deep down inside and lots of times advice can screw you up."

Now, it might seem a bit strange for someone running a blog on engineering career advice to quote someone recommending you ignore career advice, but he then told a story that gave some more depth to what he was trying to say.

He said that as a 16-year old on the stand up comic circuit, Rodney Dangerfield saw Eddie do his act. Many people reading this have no idea who that is, but do yourself a favor and follow the link to find out. Suffice it to say, Rodney Dangerfield was a comedy king in the late 70s and early 80s (best known by general audiencces for his role in Caddyshack) when this incident took place, so naturally Eddie sought guidance from him. Dangerfield advised Eddie to cut down on his use of profanity. He told Eddie he was funny, but was going too far with his use of expletives.

Ultimately, Eddie decided that his use of language was a fundamental part of who he was as an entertainer and he ignored the advice. Years later, after Eddie had achieved fame, he next saw Dangerfield when they happened to be using adjacent urinals at a bathroom in Caesar's Palace in Las Vegas. When Rodney noticed who it was next to him, he simply shrugged his shoulders and said, "Who knew?"

To me, the point of the story isn't that you simply ignore advice out of hand, as the original quote implies. Instead, it shows that you have to know who you are and what you want to achieve in order to put whatever suggestions you might get to their best use. Ultimately, your day to day decisions are nobody else's but yours. You have to decide what advice is good or bad given the situation. The important part is that you be open to ideas in the first place and know enough about what you are trying to achieve, both in the short term and the long term, in order to make an informed choice when advice comes your way.

Labels:

 Was that interesting or helpful? Consider subscribing:  by reader  or   by Email

posted by Pete Johnson @ 7:42 PM   2 comments

2 Comments:

At 9:21 PM, Blogger Elton said...

How can someone not know who Rodney Dangerfield is?! That would be a travesty.

Nice random thought!

 
At 11:26 PM, Blogger Pete Johnson said...

Elton, my lead commenter, thanks for dropping by again.

Given that I'm old enough to have seen Caddyshack in theaters when it came out, I didn't want to assume there wasn't an age gap there. You score big points with me for knowing, though. If you can quote any of Bill Murray's monologue on caddying the Dali Lama, you get even more points (big hitter, the Lama).

Also, some readers are non-US and I'm not sure Rodney got much play in Europe. Next week, I've got a post brewing on the use of slang in an international work force that focuses on that sort of thing.

Thanks again for stopping by. Keep 'em coming and tell a friend (or 3).

 

Post a Comment

   Subscribe to comments in a reader

   Subscribe to comments by Email

<< Home

Saturday, February 03, 2007

Random Thought: The 1994 San Francisco 49ers

The NFL Network is running this great documentary series of the top 20 Super Bowl teams called America's Game. I'm a huge NFL nut, so this has been great viewing for me, mostly while on the treadmill (I'm multi-tasker, what can I say). I still have a few to catch up on off my Tivo, but my favorite so far has been #17 on that list, the 1994 San Francisco 49ers.

I started my IT career in the Bay Area in June of 1993. Prior to that, I had never left Southern California for more than 7 days in my whole life and was conditioned to dislike all NoCal teams as a result of the various sports rivalries. The America's Game episode on that 1994 49er team starts at about this same time. Legend Joe Montana was traded to the Kansas City Chiefs that off season, leaving Steve Young as the starting quarterback trying to make fans forget the guy who led the team to 4 Super Bowls. At the time, because I wasn't a huge fan of the team and didn't have an allegiance to either guy, I felt like I had a less biased opinion of the situation than the people around me in Silicon Valley. It was odd to me that they hated their own quarterback so much despite the fact he already had a league MVP trophy. Because of all that, I felt like I had some insight to this particular team on the countdown.

The best part about the episode is Steve Young's surprising candor and passion. He tackles "the Joe topic" head on in the interview portions of the show that are inter cut with highlights of that season (and voiced over by Bruce Willis). I remember pretty vividly how the local media reacted to Joe being shown the door and their immense dislike of Young as a statistical machine who couldn't win the big one (very similar to how Peyton Manning is portrayed nationally, we'll see how things play out tomorrow, though). In hindsight, Young goes into detail about how he understood the criticism and the comparisons. The 49ers had lost two straight NFC Championship games to the Dallas Cowboys under Young's leadership, so the pressure was really on for that 1994 team, especially given the defense they assembled that year through the new free agency system that still exists in the NFL today.

Early in the season, the 49ers won a couple of games but were being blown out at home by the Philadelphia Eagles. In the middle of an offensive series, head coach George Seifert pulled Young from the game to save him from injury. That act would change their whole season in unanticipated ways.

Young explains in detail that, to him, it was as if Seifert were pointing the finger directly at him and saying, "You, you're the reason we're losing." While that was not Seifert's intent, it is an important lesson in perception. Seifert really was trying to save his star from injury, but the way he chose to do it embarrassed Young.

Fortunately for Seifert, this provided an inadvertent spark. Young became livid on the sideline after being benched, which can be clearly seen from the footage of the game. In his interview segment, Young explained that he was fired up so much he was looking for a fistfight. He was humiliated to the point where he wanted to punch his boss and didn't care if anybody knew about it. It was a side to Youngs competitiveness that his teammates had never seen before and after that incident, they followed him with a dedication they hadn't before.

Young says that at first, that puzzled and irritated him that it took something like that for his teammates to believe in him. But, he said he realized that perception is reality and before he showed them that side to him, the perception was that he wasn't fierce enough to come through when it counted. Once he showed them that, they supported him enthusiastically throughout the rest of the season. That 49er team went on to win the Super Bowl, in which Steve Young broke Joe Montana's Super Bowl record for TD passes in a single game and was named MVP.

There are two important lessons from this documentary. Seifert failed to realize how his actions would be taken by his star player in that game against the Eagles. He didn't appreciate what it would be like to be Steve Young and be benched in that situation and because he didn't think that through, their relationship suffered. This can happen to you and has happened to me.

George got lucky, though, because his mistake helped Young's leadership grow. The other lesson is exactly what Young said, perception is reality. It doesn't matter how you really are, it matters how people perceive you. Unless you give them data that suggests that perception is wrong, it won't change and others actions towards you won't change either. Think about that when it is time for your performance evaluation.

Incidentally, although the panel that came up with these rankings forgot more about football while you read this than I'll ever know, I find it criminal that the 1972 Miami Dolphins and not the 1985 Chicago Bears were named the #1 team in this countdown. That Dolphin team went undefeated, but had the easiest schedule of any team that has ever appeared in a Super Bowl. That Bear team struck fear in the hearts of their opponents. They lost only 1 game that year, a late season Monday Night Football loss at Miami with every member of the 1972 team in attendance. That 1985 Dolphin team would go onto the AFC Championship game, so they were no slouch, and playing at home in a nationally televised game with franchise pride on the line. Needless to say, that loss is forgivable to that '85 Bears team.

And I'm a New Orleans Saints fan saying that (my wife grew up in Leesville, Louisiana) whose still bitter over the recent NFC Championship game.

Labels:

 Was that interesting or helpful? Consider subscribing:  by reader  or   by Email

posted by Pete Johnson @ 7:14 PM   2 comments

2 Comments:

At 8:36 PM, Blogger Elton said...

I just wanted to stop by and thank you for your comment. It was probably the most insightful comment I've ever received!

Is it just me, or is it curious that Java is perceived as so much more secure than PHP? Granted, Java goes to great lengths to make sure you can't get away with stupid stuff like going out of an array's bounds, but I can't help but wonder why it is that there are more popular hacks for PHP than for Java? Hackers tend to flock to the most popular technologies, and I always thought that Java was bigger than PHP.

I joined up with a web team that's building a site from the bottom up in Ruby, should be fun (I hope!).

 
At 9:44 PM, Blogger Pete Johnson said...

Hey Elton, thanks for the very kind words. I hope Super Bowl Sunday treated you well in Austin. I'm not sure if you'll see this here or not, so I'll post a reference to this back at your blog. For anybody else reading this, see Elton's recent entry that includes a PHP vs Java vs Ruby snippet.

You could probably find plenty of people to passionately debate the security issue of PHP on Slashdot or any number of other places, but to me it comes down to how they chose to build in the dynamic loading structures into PHP. Java took great care in what you do with the classloader, but in PHP things are a bit looser and easier to hack as a result.

You are correct, though, hackers tend to flock to the most popular technologies. They also tend to flock to technologies that are easy to hack (see: any Windows operating system ever).

I'd be interested to hear your experiences with Ruby. Drop me an email when you have something to tell and I hope you become a regular watcher of my space here.

---Pete

 

Post a Comment

   Subscribe to comments in a reader

   Subscribe to comments by Email

<< Home

Tuesday, January 23, 2007

Random Thought: Word Tactics

Similar to tips on PowerPoint tactics, Word documentation also has to be nicely organized and quickly tell readers why they are investing their time. Although the format changes slightly, the intent and organization are basically the same for both Word and PowerPoint.




For documents, the “What is this and why should I care?” topic is typically combined with an “Agenda” section. Simply entitled “Introduction”, this section should literally answer for readers why they are spending their time on you and present an organization for your arguments to come.

Unlike presentations, many people will see a document and completely ignore its contents after the first page. Others whom you want to reach realistically will not have the time to digest your 15+ page masterpiece on average doughnut consumption rates for suburban nuclear power plant safety inspectors. You want to get your point across but you will lose a lot of your audience quickly. What do you do?

An “Executive Summary” is really just a fancily worded way of putting your conclusions directly following your introduction. If a large percentage of you audience will not be interested in your argument, a lot of them may still be interested in your conclusions. Placate them by getting to the bottom line up front.

For your audience that is interested in your detailed arguments, structure your thoughts similarly to how you would in the slide set media. Here, you do not have to play tricks like reminding your reader where you are in your outline since they know how much they have read already, but you still want to make it easy to follow along. The best way to do that is to use font sizes and embellishments consistently, as shown in the figure.

By default, Microsoft Word will use a bold Arial size 16 font for a “Heading 1” style, which is great for titles (“The Wyoming Incident”). “Heading 2”, bold italic Arial size 14 font, looks good as a section title (“Introduction”, “Executive Summary”, etc.). “Heading 3”, bold Arial size 13 font, works as a subsection title (“Uncovering the Contact Location”), and that is about as far as you will want to go with your organization. Organizing your thoughts any deeper than a subsection becomes difficult to follow for readers. Not surprisingly, these three Word defaults work well with the Times New Roman size 12 default font for “Normal” text. Your organization may have standards in this area that you will need to follow, but absent that these four font styles are a good guideline.

Where slide sets have backup slides, documentation has appendices. Not everyone will care about the exact formula you used to compute valid hyperspace vectors, but you do not want to leave out those who might. Putting this information in the back under a section name that most readers will know contains optional material solves this organizational problem nicely.

Finally, the writing style for your documentation is just as important as its organization. Do not confuse this form with a letter to a friend or family member. Use of a first person perspective (“I find your lack of faith disturbing.”) brings informality to a document, which lessens its impact. Also, it gives the appearance that the author is the sole participant in its creation, a topic covered in the previous section on slide set author credits. A better approach is to use an objective voice (“The lack of faith is disturbing.”). This makes the words sound more authoritative and formal, attaching more importance to them. Avoid contractions as much as possible for the same reason.

Labels:

 Was that interesting or helpful? Consider subscribing:  by reader  or   by Email

posted by Pete Johnson @ 7:16 PM   0 comments

Tuesday, January 16, 2007

Random Thought: Bridge burning starring Isiah Thomas

At 6’1”, Isiah Thomas is generally considered to be one of the top two or three “undersized” players in the history of the NBA. He also happens to be at the center of the most famous bridge burning incident in professional basketball history. Although he is generally acknowledged to be a horrible coach and bad GM, his accomplishments as a player by few people who have ever played the game.



Check out his NBA.com biography if you don't believe me.

In addition to his professional accomplishments, Thomas was the leader of the Indiana University team that won the 1981 NCAA tournament. He went on to earn almost every significant achievement a basketball player can earn, but one in particular eluded him: an Olympic gold medal.

Thomas was to be a key figure on the 1980 U.S. Olympic basketball team. The U.S. boycott of the Moscow-hosted games, in protest to the Soviet Union’s 1979 invasion of Afghanistan, kept Thomas and many other athletes from pursuing their Olympic dreams. For most of his professional career, Olympic basketball was reserved for players with amateur status and he was therefore not eligible to play.

For the 1992 Barcelona games, however, basketball’s international governing body altered the rules to allow professionals to participate. As a highly decorated player who had missed his previous chance for reasons beyond his control, Thomas was an early favorite to be named to what came to be known as the U.S. “Dream Team”. Despite his overwhelming body of work, he was not. Why?

To answer that, you have to go back to the 1985 NBA All-Star Game. Allegedly, Thomas convinced his teammates on the Eastern Conference All-Stars to pass the ball as little as possible to the lone rookie to make the team that year. The attempt was sort of a hazing ritual, but it was not forgotten by the player who was targeted: Michael Jordan. This began a longstanding embittered relationship between the two players, which continued when Thomas’ Detroit Pistons used rough defensive tactics against Jordan in the four consecutive seasons they met in the play-offs during the late 1980’s and early 90’s. Detroit won the first three of those post-season meetings, capturing two NBA Championships in the process, before the Chicago Bulls finally prevailed in 1991 in route to their first title. During that last encounter, Thomas encouraged teammates to avoid shaking hands with the victorious Bulls in a show of poor sportsmanship that escalated the dispute between the two players even more.

Reportedly, when the 1992 U.S. Olympic basketball team was being assembled, Jordan told the selection committee that his only condition for participating on the team was that Thomas would not be on the roster. With leverage as the world’s most talented and popular player, Jordan got what he wanted and Thomas was left off the team despite having a more impressive resume than many of the players who were named to the team.

What Thomas failed to see was how his interactions with Jordan might affect his future goals. Upon Jordan’s arrival in the league for the 1984-85 season, Thomas was a veteran who had already been named Most Valuable Player of the All-Star Game and clearly had more authority. As time went on, any NBA fan can tell you how that power shifted, resulting in Jordan being one of the most recognizable athletes in the world.

Why is this important? This same scenario can happen to anybody in any career. Today’s peer can easily become tomorrow’s executive vice president. Do you want an ally or an enemy to be the person in power?

You never know where that person is going to come from, so the best approach is to leave everyone with as positive impression of you as possible, even if they are a jerk to you. If you return the favor and treat them just as poorly, you potentially set yourself up for career problems later on. Treat others the way that you want to be treated, regardless of how they treat you, so that your options are open at all times.

Labels:

 Was that interesting or helpful? Consider subscribing:  by reader  or   by Email

posted by Pete Johnson @ 1:30 PM   0 comments

Technology Blogs - Blog Top Sites