Deprecated: Assigning the return value of new by reference is deprecated in /homepages/38/d93874830/htdocs/var/www/wp-includes/cache.php on line 33

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32
San Diego Serenade » Let’s let the professionals do what they do best

San Diego Serenade



Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32

Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32

Let’s let the professionals do what they do best

Posted in Street Scene promoter Joe Callahan by Conor on the
Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32
January 13th, 2007

Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions-formatting.php on line 83

Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::the_content() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 1252

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 250

Strict Standards: Non-static method GA_Filter::ga_parse_article_link() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 250

Strict Standards: Non-static method GA_Filter::ga_parse_link() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 241

Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 232

While it is certainly noble of FM 94.9 to start paying its fan club members to start DJing for them, I think we can all agree that there are some things that are best left to the professionals. Nobody wants to hear your voice or my voice on the radio; it takes a certain type of butter smooth voice to say, “Does it get any better than the Chili Peppers? We’ll be getting the Led out, and playing the brand new Shins (Phantom Limb) in just a minute, but now here’s Pauly to hit you up with the traffic.”

And if we can just peer into the future, for a minute, and observe the obvious next dominoes to fall if the fans are allowed to take over the airwaves, I think that it’s safe to say that the potential alternative worlds are chilling at best.

Joe Callahan

Are we just gonna let any man off the street peer over their shades for press shots a la Street Scene promoter Joe Callahan? Are we? Let’s draw the line somewhere. Sanity must carry the day at some point in time, people. Let’s just reign it in before things get too crazy.

2 Responses to 'Let’s let the professionals do what they do best'

Subscribe to comments with RSS or TrackBack to 'Let’s let the professionals do what they do best'.


  1. Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::comment_author_link() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 1252

    Deprecated: Function ereg() is deprecated in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 263

    Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 266

    Strict Standards: Non-static method GA_Filter::ga_get_domain() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 268
    Rosemary said,

    on
    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32
    January 15th, 2007 at
    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32
    11:23 am


    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions-formatting.php on line 83

    Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::comment_text() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 1252

    Strict Standards: Non-static method GA_Filter::ga_parse_comment_link() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 256

    As far as I understand, the insider DJs will be more of a focus group and steering the playlists of the on-air personalities, not replacing them.


  2. Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::comment_author_link() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 1252

    Deprecated: Function ereg() is deprecated in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 263
    cdw said,

    on
    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32
    January 19th, 2007 at
    Strict Standards: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 24

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 30

    Strict Standards: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 32
    1:28 pm


    Deprecated: preg_replace(): The /e modifier is deprecated, use preg_replace_callback instead in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions-formatting.php on line 83

    Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::comment_text() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 1252

    Strict Standards: Non-static method GA_Filter::ga_parse_comment_link() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 256

    this picture creeps me out worse than la lohan in her fleshtini

Leave a Reply



Strict Standards: call_user_func_array() expects parameter 1 to be a valid callback, non-static method GA_Filter::spool_analytics() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-includes/functions.php on line 1329

Strict Standards: Non-static method GA_Filter::spool_this() should not be called statically in /homepages/38/d93874830/htdocs/var/www/wp-content/plugins/googleanalytics.php on line 180