August 6, 2006
[Personal] PMC The Next
Well, I've pretty much decided on the iRiver PMC-120. It'll be a couple of weeks before I can get it (have to save up the $200 for it), but I really like the Windows Portable Media Center software, and the iRiver is the closest thing I can find to my Zen PMC that isn't a Zen PMC.
August 5, 2006
[Blog] Moderation Disabled
As promised, I've disabled comment moderation now that the majority of the furor here has died down.
August 4, 2006
[Testing] Reason #∞ To Dislike PC Testing
Okay, I can't share any source code for this one, but you've got to love this one...
Standard do-nothing DirectX application, consisting of basic render loop and DirectInput polling. The only other items hooked up to the computer are a USB keyboard and a USB mouse.
While the application does not have focus, the render loop runs at full speed (~120fps).
Once the application gains focus, the application framerate drops to .2 frames per second.
Because the problem "goes away" when the application has focus, you can't hook it up to the debugger to track it down, so you insert trace statements.
The trace statements indicate that the DirectInput mouse polling call is "timing out," and is the cause of the problem. Changing the mouse to a different mouse or to a PS/2 mouse has no effect.
Unplugging the keyboard and plugging it back in causes the symptoms to go away until the computer is restarted, at which time the symptoms come back. Changing the keyboard out completely for a different USB keyboard causes the symptoms to go away permanently. However, if you swap the keyboard for another from the same brand, the symptoms come back.
In other words, somehow the keyboard is causing a 99.8% framerate decrease by interfering with the mouse.
Let's just say that on a scale from 1 to 10, this hit a 950 on my WTF-o-meter.
Standard do-nothing DirectX application, consisting of basic render loop and DirectInput polling. The only other items hooked up to the computer are a USB keyboard and a USB mouse.
While the application does not have focus, the render loop runs at full speed (~120fps).
Once the application gains focus, the application framerate drops to .2 frames per second.
Because the problem "goes away" when the application has focus, you can't hook it up to the debugger to track it down, so you insert trace statements.
The trace statements indicate that the DirectInput mouse polling call is "timing out," and is the cause of the problem. Changing the mouse to a different mouse or to a PS/2 mouse has no effect.
Unplugging the keyboard and plugging it back in causes the symptoms to go away until the computer is restarted, at which time the symptoms come back. Changing the keyboard out completely for a different USB keyboard causes the symptoms to go away permanently. However, if you swap the keyboard for another from the same brand, the symptoms come back.
In other words, somehow the keyboard is causing a 99.8% framerate decrease by interfering with the mouse.
Let's just say that on a scale from 1 to 10, this hit a 950 on my WTF-o-meter.
[Personal] Woe PMC
My Zen Portable Media Center died in December. I finally got it back from warranty service in March. On my way home, it died in the exact same fashion as last time.
At this point, I really don't want to buy another Creative Labs product again. I really liked my Zen PMC because of how well it worked for what I needed it to do. Unfortunately, it's also really good at breaking on a regular basis for no apparent reason whatsoever.
I don't want an iPod Video. As "nifty" as they may look, I don't like having to double-dip for my content. I've already spent more than enough money "single-dipping" for my content, thank you very much.
So anyway, I'm in the market for a decent portable video player that won't break, works with standard video formats including Windows Media 9 (transcoding okay as long as it's automatable), has a decent video life (loved the 8-10 hour battery on this baby), and a nice size screen.
At this point, I really don't want to buy another Creative Labs product again. I really liked my Zen PMC because of how well it worked for what I needed it to do. Unfortunately, it's also really good at breaking on a regular basis for no apparent reason whatsoever.
I don't want an iPod Video. As "nifty" as they may look, I don't like having to double-dip for my content. I've already spent more than enough money "single-dipping" for my content, thank you very much.
So anyway, I'm in the market for a decent portable video player that won't break, works with standard video formats including Windows Media 9 (transcoding okay as long as it's automatable), has a decent video life (loved the 8-10 hour battery on this baby), and a nice size screen.
[Working] CLM
CLM Acronym, stands for "Career Limiting Move." Originated at Microsoft. Signifies a mistake or decision that eliminates any hope of promotion or advancement within your field.Everyone makes mistakes. It doesn't matter what you do.
Some mistakes only affect yourself. Some mistakes can cost millions of dollars. Some mistakes can lead to lives being lost.
Personally, I believe that almost all mistakes are opportunities in disguise. A person can grow by learning from a mistake, processes can be strengthened as a result of the mistake, and if a mistake is properly handled, a mistake can actually lead to positive PR.
Of course, there are some mistakes that are just too large to be looked past. Sometimes, mistakes like that can lead to termination. Other times, mistakes end up being something that seems worse when you are going through it: the dreaded CLM. A good example would be Gumpei Yokoi from Nintendo. Even though he had guided several successful products to market (including the GameBoy, the Metroid series and others), the Virtual Boy was a large enough disaster that it essentially ended his career at Nintendo.
Nintendo saw the value of having him there, but also did not want to give him an opportunity to fail on that large of a scope again, so he was pulled out of a position of authority and relegated to being a "respected elder." In other words, he was essentially left in the middle of Nintendo with no responsibilities and was essentially useless.
CLM's are a difficult thing to overcome inside a company. Generally, if you are able to overcome the CLM, the people that you worked with in the past will have passed you internally, so any support structure that you may have had is essentially gone. It can be even worse if you decide to jump ship and go to a different company, because you'll be starting from scratch with no support structure.
So what do you do if you believe that you have committed a CLM? The first thing to do is to own up to it. People who take responsibility for their actions are generally able to overcome career obstacles like this easier than people who try to place the blame outside of themselves.
The second thing to do is to sit down with your manager to try to come up with a plan for how to rebuild yourself and move past this problem. "Made a mistake, but learned from it and moved past it" beats "made a mistake and wallowed in it for eons" any day.
The final thing to do is forgive yourself for the mistake. Most people who commit CLM's tend to dwell on them every day, and are constantly blaming themselves for the result. While one should never forget their mistakes, one should we willing and able to let go of any negative emotions surrounding the mistake.
Subscribe to:
Posts (Atom)