Skip to main content

Don't remove the wisdom tooth

The inspiration for this post is a post by Peter Claridge

You're nearing 25 years, you've got painful wisdom tooth growth, you're even getting high fever due the pain, your dentist is asking Rs.15,000/- plus for removal/extraction and showing scientific papers claiming that wisdom tooth is unnecessary growth... First of all don't pluck it--unless you hit very very very serious problem.

I was also about fell prey for one dentist whom tried to convince me a lot for the extraction surgery. With some sort of hesitation, I had to inform it to my Mom that time. She immediately suggested me to rinse with salt water and take mild foods for about 1-week. She strongly insisted that the pain will definitely go in 1-week time. To my surprise, that did really work for me. So, far I have suggested that to many people and all of them were about to have the surgery scheduled.

Are you still going to pluck the wisdom tooth or just treating it with salt water rinsing?

Comments

Popular posts from this blog

Interview question #2

This is related to PHP's array . An array has number of elements. All elements are integers and unique, which means there is no repetitive integers. (e.g.) $foo = array(7, 5, 9, 13, 2, 8); You have to sort the array, provided: You should scan the elements only once. You're not allowed to compare the elements when sorting. (i.e., you're not supposed to use any comparison operators) Sorted resultant array may not be the source array. How will you do that?

Open source PHP frameworks and problems

I was using CakePHP for sometime and proposed CakePlus , another UIMS toolkit on the top of CakePHP but also altering some problematic core of it. The thread should explain the outcome of the post. And, then I noted Akelos framework has most of the things built in. Issues with frameworks esp. CakePHP Scalability not a priority - Developers aren't aware that we can't throw more and more hardware Excessive use of regular expressions Evangelist isn't aware that the framework throws many queries unnecessarily More memory consumption - 100M would never be enough for a simple project Poor coding standards and practices - Prolong use of extract() often leads to more memory consumption Can't use the native approaches or baked codes. The override approach always lead to hard to debug codes Poor architected codes and no clear defined approaches. People belong to the cult drives the direction and often throws unprofiled codes. No native provision to share codes between M-V-C and...

What's wrong with delicious.com?

The recent UI changes of delicious.com is quite confusing and smells suicidal phase. I have noted that, after Joshua Schachter sold it to Yahoo!, it's going crazy changes. Probably, it's because a Yahoo! company now or Engineers don't get the real idea? Some crazy moves: del.icio.us to delicious.com change; probably to reach countries that censor .us TLD? delicious.com to www.delicious.com; unjustified Perl to PHP switch; why? for:handle geekish way to share to separate box; crazy but ok. Looks like, the new Yahoo! guys don't know how to make it a cult following like how twitter popularized @handle Recent broken UI