Is There Food?

by Daniel Woolstencroft

Ear Wick

Yes, “Ear Wick”.

Doesn’t sound nice, does it?

That’s what I’m currently enjoying - a wick, in my ear, to do some “wicking”.

Over the past couple of weeks, I’ve had quite a nasty ear infection. Strictly speaking, I’ve had two nasty ears infections: one in each ear. Actually, if I’m to be 100% accurate, I’ve probably had about five ear infections as they’ve been bouncing back and forth. Regardless, it’s been unpleasant.

Thanks to a doctor who appears to enjoy a “hands off” approach to curing ear infections - and by this I don’t mean he amputates the bits at the ends of people’s arms - I ended up visiting the local hospital today so that the experts could have a look. The wonderful woman at the Ear, Nose, and Throat clinic at the Royal Infirmary has taken some steps to sort me out.

By which, I mean she inflicted quite a lot of pain on me, and has left me in more discomfort than I was prior to visiting her. But, as they say, no pain; no gain. After inserting some sort of ear-widening device, she proceeded to hoover all the nasty, infection-debris from my ears. This is a weird sensation

  • you can hear, and more alarmingly feel - bits of icky gubbins being forcibly extracted from your ears. She did this on both ears, using increasingly wider widening tools each time.

But I’d had this done before. It was fine: I knew what was coming, and in all honesty looked forward to it; once they’d been hoovered, I’d feel better, right?

Sadly, this time the infection was sufficiently nasty as to close up my left ear. This explained why I couldn’t hear very well. In order to combat this unhelpful closure, a wick was inserted into my ear. And by inserted, I mean rammed. Hard. And, as I said in an email to my boss following the experience, it hurt like a very hurty thing.

And there’s nothing like applying the prescribed drops into the ear, placing cotton wool neatly inside - as advised by the nice woman at the hospital: this would absorb the drops that I’d put in - and discovering that your ear is now bleeding, thanks to the forced insertion of said wick. Blood from the ears - particularly my blood, from my ears - is something I’m not particularly fond of.

Hopefully, thanks to the power of the wick, ear drops, and the human body’s ability to heal, I’m on the mend. An ear infection is a pretty minor thing to contend with in comparison to more dramatic and life-threatening ailments, but I thought I’d share my current predicament in the hope that someone finds it entertaining. And I’m sure some people will - you sick, sick individuals.

Statamic Debug Panel

You’re seeing this panel because _display_debug_panel is true in your site settings.

Page rendered in: 0.208241s

values: 
  template: post
  layout: default
  statamic_version: 1.8.1
  php_version: 5.5.16
  theme: foundation-4
  environment: live

counts: 
  files: 
    opened: 26
    written: 1

  parses: 
    yaml: 13
    markdown: 2
    smartypants: 9
    statamic_tmpl: 11

  plugins: 
    theme: 24
    current_date: 1
activity: 
  debug (16ms): 
    0.0104s: timing
    0.0044s: counting
    0.0010s: timelining

  parsing (112ms): 
    0.0599s: statamic_tmpl
    0.0372s: yaml
    0.0101s: smartypants
    0.0053s: markdown

  config (19ms): 
    0.0191s: finding

  caching (38ms): 
    0.0293s: content
    0.0082s: settings
    0.0005s: member

  hooks (7ms): 
    0.0037s: running
    0.0034s: finding

  math (0ms): 
    0.0002s: hashing

  content (39ms): 
    0.0283s: getting
    0.0098s: preparing
    0.0008s: supplementing

  plugins (64ms): 
    0.0518s: theme:partial
    0.0106s: theme:js
    0.0009s: current_date:index
    0.0006s: theme:css
timeline: 
  0.0000s: --------- start
  0.0048s:     ~5ms  autoloaders ready
  0.0446s:    ~40ms  bootstrapped
  0.0463s:     ~2ms  app created
  0.0465s:     ~0ms  app configured
  0.0468s:     ~0ms  localization ready
  0.0483s:     ~1ms  app defaults set
  0.0819s:    ~34ms  caches updated
  0.0833s:     ~1ms  routes started
  0.0904s:     ~7ms  hooks initialized
  0.0905s:     ~0ms  segments determined
  0.0908s:     ~0ms  routes determined
  0.1153s:    ~25ms  content found
  0.1228s:     ~7ms  status determined
  0.1278s:     ~5ms  template picked
  0.1279s:     ~0ms  layout picked
  0.1408s:    ~13ms  template rendered
  0.2057s:    ~65ms  layout rendered
  0.2078s:     ~2ms  page ready
  0.2082s: --------- end