I had a cavity kind of close to the nerve that caused my tooth to crack and get wedged between two teeth.
Printable View
I had a cavity kind of close to the nerve that caused my tooth to crack and get wedged between two teeth.
I had decided to dig out part of my cavity with a sharp pointy stick looking thing, but the tooth was still wedge and hurt.
The dentist saw it and I swear he almost fainted, he asked me why the hell my teeth are in such bad condition. So I told him:
- I smoked menthols from the time I was 12 until 20
- I smoked cigars up until a few months ago
- I drank a 24 pack of cokes every 3-4 days up until about a year ago
- I still drink about 3 cokes a day
I should've told him "mais it's Louisiana!"
Technically, nearly all of my teeth are wedged between two other teeth. Only the last molar on each side is not.Quote:
Originally Posted by dday9
Technically, nearly all of my teeth are wedged between two other teeth. Only the last molar on each side is not.Quote:
Originally Posted by dday9
A flat coke is exceedingly acidic, which will destroy teeth over time.
Flat Coke? Standard Coke, No Fizz Coke or the container is Flat somehow? (Not cylindrical.)
I spent the entire day trying to narrow down a crash in our Android application. I found lots of oddball lines that seemed to cause the crash, and they all had enough in common to make me believe I was making progress. Eventually I figured out removing one particular control seemed to stabilize it. So I went to go note this in the ticket system, and then it crashed without that control
It turns out there's an issue with the Xamarin Android debugger with very similar symptoms. If I run without the debugger attached, everything works fine. (Well, with the layout bugs I'm trying to fix. But no crashes.)
I just wasted a day because the debugger was crashing my app.
I'm glad I'm using eclipse :)
VB6 had (probably still has) an issue with the debugger, as well. If you put a breakpoint in the code, it would take a different branch than it did without the breakpoint, so the code that ran with the breakpoint was not the code that ran without the breakpoint. Bugs would mysteriously vanish.
I broke that down to a simple example and submitted it to MS. Their response was basically: Live with it, this is a side effect of how we wrote the debugger.
I went camping this past weekend!
My son absolutely had a blast too! We flew a "Minion" kite and you'd've thought he was flying his own airplane, that's how much fun he was having.
It was rainy and cold this past weekend. That's bizarre. We are generally approaching the 80s by now (though whether that is from above or below, depends on the year). I darn near had to turn the heat back on.
In Bristol it was rainy and cold and hot a sunny. It was very confusing and left me unable to plan much of anything but I did get to spend a half hour reading in the back garden... then a horde of slugs hove into view and drove me off. At one point I swear they were mounting a flank attack.
I assume that you were able to get in some nice long naps as they maneuvered for the flank attack.
Besides, a flank attack by slugs wouldn't worry me much. I'd take 'em with a grain of salt.
Now that I think about it, assault by slugs is bound to fail.
I thought that if you salted a slug you were bound for success - not so much the slug...
Right, so a salt by a slug is a form of slug suicide.
Sounds like a slug-fest to me. :)