We Are At The Beginning Of Change…
Friday February 22nd 2019

Archives

Lulay, Lulay, Goodbye and Lulay

Post Published: 15 March 2010
Author:
Category: Dear Thyroid Letters
This post currently has 7 responses. Leave a comment

(Written by Mike Wilson, Thyroid Patient)

O Thyroid Cancer
We fight you. Some do not win.
Your toll far too high.

For those you did slay
Fare thee well, to them we say
Goodbye and lulay

Remember this day
Those who were lost on the way
Gone from us today

O Thyroid Cancer
We fight you still, and we win
For your end is nigh.

Be Sociable, Share!

Tags: , , , , , , , , , , ,

Follow Dear Thyroid on Twitter/@DearThyroid | See our Facebook Page | Become a Fan on Facebook | Join our Facebook Group

You Can Create a Dear Thyroid Profile and share with friends!

Reader Feedback

7 Responses to “Lulay, Lulay, Goodbye and Lulay”

  1. Joanna says:

    Mike, this might be my favorite thyku yet! We will fight this dirty disease till death.

  2. Dear Thyroid says:

    Indeed, Joanna, Indeed!

  3. HD inOregon says:

    Hi(Ku) Mike,

    Super job dear friend!
    We thank you much indeed, Sir
    Our spirits ascend!

    HD in Oregon

  4. Dear Thyroid says:

    HD – Hi(Ku) – Nicely done!

    What would we do without you, my dear?! You are a peach.

  5. Elaine says:

    Very good. Would like to see more

    Thank You

  6. Dear Thyroid says:

    Oh, Elaine, Mike is our Thyku thydaddy of doom. Here are links to his previous posts: http://dearthyroid.org/page/2/?s=+haiku

  7. Lolly says:

    Great Thyku Mike I miss your thyku’s.

Leave a Reply

Comments are moderated in an effort to control spam. If you have a previously approved Comment, this one should go right through. Thanks for your patience!

 

200 OK

OK

The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [no address given] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.