FREE counter and Web statistics from sitetracker.com
collision detection
content | discontent
send me yours
July 26, 2003
Tenosynovitis

Sending text messages on phones is now so popular in China that it's given rise to an entirely new form of repetitive stress injury: Sore thumbs. From a story in the China Daily:

Wang Heping, a senior doctor with Renmin Hospital of Northwest China's Gansu Province, said: "I have diagnosed four cases of tenosynovitis this year, and I believe there are more people who haven't seen a doctor."

Thumbs might be hurt by pressing the phone keypad too much, too quickly and in a very small area, Wang said.

"To keep your thumbs healthy, the best way is to write less messages and do more physical exercise," he said.


(Thanks to Techdirt Wireless News for this one!)

Posted by Clive Thompson at July 26, 2003 11:51 PM

Trackback Pings

TrackBack URL for this entry: http://www.collisiondetection.net/mt3/mt-tb.cgi/410

Listed below are links to weblogs that reference Tenosynovitis:

ยป texas hold em from texas hold em
You can also check some information about party poker online poker texas hold em [Read More]

Tracked on March 18, 2005 1:57 AM

Comments

It's true!!! I have what I refer to as Blanckberry thumb. Any overstress on my right thumb results in a jolting pain in the tendon. It's a real pain in the hand.

Posted by: Robert at July 28, 2003 2:33 PM

Really? How many emails a day do you think you send using your Blackberry?

Posted by: Clive at July 28, 2003 2:39 PM

Probably an avergae of about 50 during the course of business day although it can easily be double that on busy days.....it's a real Blackberry culture around here!

Posted by: Robert at July 29, 2003 1:36 PM

same problem - just diagnosed with tenosynovitis in both wrists - only thing i can think of is prolonged blackberry use....robert - did u take the steroid injection or a plastic mold or just rest and time for healing. any changes in your lifestyle (less blackberry??) thx.

Posted by: raul at September 1, 2003 9:48 PM

what does this have to do with tenosynovitis?

Posted by: cynthia at September 23, 2003 3:25 PM

dr
i v tenosynovitis in my finger but i noticed that there is relationship between pain and masturbation i don not know how ?can u ttt it ? i wait

Posted by: essam at October 29, 2003 6:58 AM

I have just been diginosed with Tenosynovitis in my ankle but all I read is in the hands Any suggestion

Posted by: Yolanda at November 20, 2003 5:44 PM

Posted by: dsl tarife at January 2, 2004 4:06 PM

Nice site. thx.

Posted by: Online Casino at January 16, 2004 2:56 AM

When the machine compiles your code, however, it does a little bit of translation. At run time, the computer sees nothing but 1s and 0s, which is all the computer ever sees: a continuous string of binary numbers that it can interpret in various ways.

Posted by: Rees at January 19, 2004 7:06 PM

This back and forth is an important concept to understand in C programming, especially on the Mac's RISC architecture. Almost every variable you work with can be represented in 32 bits of memory: thirty-two 1s and 0s define the data that a simple variable can hold. There are exceptions, like on the new 64-bit G5s and in the 128-bit world of AltiVec

Posted by: Jocosa at January 19, 2004 7:06 PM

These secret identities serve a variety of purposes, and they help us to understand how variables work. In this lesson, we'll be writing a little less code than we've done in previous articles, but we'll be taking a detailed look at how variables live and work.

Posted by: Christopher at January 19, 2004 7:06 PM

To address this issue, we turn to the second place to put variables, which is called the Heap. If you think of the Stack as a high-rise apartment building somewhere, variables as tenets and each level building atop the one before it, then the Heap is the suburban sprawl, every citizen finding a space for herself, each lot a different size and locations that can't be readily predictable. For all the simplicity offered by the Stack, the Heap seems positively chaotic, but the reality is that each just obeys its own rules.

Posted by: Jeremy at January 19, 2004 7:07 PM

This code should compile and run just fine, and you should see no changes in how the program works. So why did we do all of that?

Posted by: Edith at January 19, 2004 7:07 PM

But variables get one benefit people do not

Posted by: Jocatta at January 19, 2004 7:07 PM

Let's take a moment to reexamine that. What we've done here is create two variables. The first variable is in the Heap, and we're storing data in it. That's the obvious one. But the second variable is a pointer to the first one, and it exists on the Stack. This variable is the one that's really called favoriteNumber, and it's the one we're working with. It is important to remember that there are now two parts to our simple variable, one of which exists in each world. This kind of division is common is C, but omnipresent in Cocoa. When you start making objects, Cocoa makes them all in the Heap because the Stack isn't big enough to hold them. In Cocoa, you deal with objects through pointers everywhere and are actually forbidden from dealing with them directly.

Posted by: Abraham at January 19, 2004 7:07 PM

Being able to understand that basic idea opens up a vast amount of power that can be used and abused, and we're going to look at a few of the better ways to deal with it in this article.

Posted by: Grace at January 19, 2004 7:08 PM

Earlier I mentioned that variables can live in two different places. We're going to examine these two places one at a time, and we're going to start on the more familiar ground, which is called the Stack. Understanding the stack helps us understand the way programs run, and also helps us understand scope a little better.

Posted by: Wymond at January 19, 2004 7:09 PM

Since the Heap has no definite rules as to where it will create space for you, there must be some way of figuring out where your new space is. And the answer is, simply enough, addressing. When you create new space in the heap to hold your data, you get back an address that tells you where your new space is, so your bits can move in. This address is called a Pointer, and it's really just a hexadecimal number that points to a location in the heap. Since it's really just a number, it can be stored quite nicely into a variable.

Posted by: Clement at January 19, 2004 7:09 PM

Posted by: Milf at January 20, 2004 6:20 AM

Post a comment

Thanks for signing in, . Now you can comment. (sign out)

NOTE: If you posted a comment and you can't see it -- try refreshing your browser.


Remember me?