Deprecated: Function set_magic_quotes_runtime() is deprecated in /homepages/30/d215649942/htdocs/textpattern/lib/txplib_db.php on line 14

Warning: Cannot modify header information - headers already sent by (output started at /homepages/30/d215649942/htdocs/textpattern/lib/txplib_db.php:14) in /homepages/30/d215649942/htdocs/textpattern/lib/txplib_misc.php on line 1621
tag_error <txp:posted format="%a" /> ->  : getdate(): 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%a" /> ->  : 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%a" /> ->  : strftime(): 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%b" /> ->  : getdate(): 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%b" /> ->  : 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%b" /> ->  : strftime(): 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%d" /> ->  : getdate(): 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%d" /> ->  : 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%d" /> ->  : strftime(): 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted format="%Y" /> ->  : getdate(): 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted format="%Y" /> ->  : 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted format="%Y" /> ->  : strftime(): 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:posted/> ->  : getdate(): 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:posted/> ->  : 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:posted/> ->  : strftime(): 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:comment_time/> ->  : getdate(): 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:comment_time/> ->  : 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:comment_time/> ->  : strftime(): 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:comment_time/> ->  : getdate(): 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:comment_time/> ->  : 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:comment_time/> ->  : strftime(): 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177
tag_error <txp:comments_error wraptag="ul" break="li" /> ->  : getdate(): 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1140
tag_error <txp:comments_error wraptag="ul" break="li" /> ->  : 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1141
tag_error <txp:comments_error wraptag="ul" break="li" /> ->  : strftime(): 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 'Europe/Berlin' for 'CET/1,0/no DST' instead  on line 1177

Warning: Cannot modify header information - headers already sent by (output started at /homepages/30/d215649942/htdocs/textpattern/lib/txplib_db.php:14) in /homepages/30/d215649942/htdocs/textpattern/publish.php on line 477
Puntada sin Hilo: Lo que de verdad importa

Ir al contenido

jue
nov
13

2008

Lo que de verdad importa

Releyendo todos los artículos que he escrito hasta el momento, me he dado cuenta de que muy pocas veces trato temas realmente importantes, temas de los que nos afectan a todos y cuestiones que a todos se nos pasan por la cabeza en algún momento. Hoy voy a tratar uno de estos temas. Un tema que afecta a la familia en si misma y, más concretamente, a las abuelas y los nietos.

Me parece admirable y destacable que, en estos tiempos que corren, tener edad haya dejado de ser sinónimo de tener razón. Es por eso que me parece fenomenal que los nietos puedan aconsejar e influir en los actos de las abuelas, pero, no por ello, tales ideas y consejos deben imponerse y acabar suplantando a las ideas originales.

Bien, supongo que la mayoría de vosotros ya sabéis de lo que hablo... efectivamente, hablo de las pizzas de Casa Tarradellas. Está muy bien que le hayan añadido salsa barbacoa a la pizza boloñesa, pero... ¿por qué ya es imposible encontrar la versión antigua, la que venía sin la salsa barbacoa?.. No es que le tenga ningún rencor especial a la salsa barbacoa, pero es que ya hay muchas pizzas que contienen esta salsa (de casi cualquier marca) y todas saben más o menos igual. Sin embargo, la pizza boloñesa de Casa Tarradellas no tiene sustituto, puede que alguna otra marca trate de imitarla, pero, hasta donde he podido probar, ninguna lo ha conseguido. Hemos perdido un gran sabor. ¿Qué sera lo próximo?, ¿deshacerse de la pizza de peperoni?.

Comentarios

  1. Jajaja que bueno, yo empecé leyendo como que ibas a contar una historia interesante sobre el respeto inter_generacional y me encuentro una reflexión culinaria en toda regla juasjuas

    La verdad es que estoy de acuerdo que a veces queriendo innovar nos pasamos, y el caso culunario no iba a ser menos. A mi no me parece mal que se invente una pizza de esas añadiendole la salsa, igual q que se invente la kebab por ejemplo, pero el tema es no dejar de fabricar la antigua sin la salsa porque, lo q esta claro, es que van a vender lo que les de la gana, ya que si dejan de hacer la antigua y se limitan a vender y promocionar la nueva, ésa será la que compraremos (cuestion de marketing), pero si quieres la antigua,…. como decidan retirarla con la otra en sustitucion de ella, ya te veo haciendotela en casa con el picadillo la salsa y el pan de pizza con la harina del eroski que tenemos por un armarín de la cocina.

    Aunque esto es así, tb hay cosas muy sabrosas en innovar, como el arroz con leche con clara de huevo batida y gratinada, el mejor invento que he visto en la cocina, y a tu mami precisamente…. Sencillo, rápido y con un toque de gusto que es un pasada.

    Puede que lo proximo sea la tortilla de patatas de toa la vida, te la imaginas??? Tortilla de patatas a la salsa barbacoa mmmmmm….. que rico!! Jaja pues seguro que como a alguna marca se le ocurra, a partir de ahora, se venderá en los supers.

    — NelePh · nov 13, 18:31 · #

  2. Yo también creí, al principio, que ibas hablar del respeto a los abuelos, y resulta que acabas hablando de pizza :O. Te diré que tienes razón, hay una gran tendencia a mezclar sabores y recetas y a deshacerse de las clásicas, que en la mayoria de los casos son las mejores :), además seguro que esa salsa barbacoa no es más que un montón de productos químicos, que quién sabe lo que llevarán :-&.
    En fin, está bien innovar en la cocina, pero sin olvidar los sabores de todoa la vida, je,je.

    Pd.- ¿ El kebab no estaba ya inventado?

    — Terpsicore · nov 16, 16:40 · #

Ayuda Textile