Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the post-smtp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/ibcppsicanalise/www/testes/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the happy-elementor-addons domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/ibcppsicanalise/www/testes/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the updraftplus domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/ibcppsicanalise/www/testes/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the rocket domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/ibcppsicanalise/www/testes/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/ibcppsicanalise/www/testes/wp-includes/functions.php on line 6114
Quando falamos pelos olhos - IBCP Psicanálise

Quando falamos pelos olhos

por Adriana Gallo | Psicanalista

A recente pandemia causada pelo novo Coronavírus (SARS-COV-2), que causa a COVID-19, obrigou-nos a aderir a práticas cotidianas determinadas pelos órgãos de saúde mundiais. Passamos a ter mais cuidado com a higiene, posteriormente, aderir ao confinamento social e, outra determinação, a utilização de máscaras, visando proteger a todos de um possível contágio.

Andamos nas ruas com o rosto coberto sendo que a única parte visível nesta situação, são os nossos olhos, estes que desde o início, sempre foram uma conexão fundamental, como por exemplo na relação da mãe com o seu bebê. Pelos olhos, também, saem as mágoas, as nossas “más águas”, na forma de lágrimas que quando esvaziadas e drenadas, aliviam pressões e dores.

Assim, como seria uma sessão psicanalítica “protegida” por máscaras? Os olhos não articulam palavras, mas eles expressam o ser, no mais profundo silêncio e a máscara, dificulta as outras percepções em relação ao rosto e as expressões dos pacientes.

Na clínica Psicanalítica, utilizamos a palavra, a leitura dos gestos e a postura corporal, para “escutar” o paciente, até mesmo através da observação do silêncio que ele nos traz.

Neste novo cenário, nossa compreensão acerca da escuta analítica ganha espaço para se expandir e o olhar passa a ser de fundamental importância para ambos: paciente e psicanalista

Será verdade que os olhos não mentem? Quantas vezes olhamos e não enxergamos?

Hoje, mais do que nunca, faz parte do papel do analista poder mostrar ao paciente, eventuais cegueiras na sua visão sobre seus problemas e os seus potenciais a serem descobertos.

Ultimos Artigos

plugins premium WordPress
Warning: Use of undefined constant LIBXML_HTML_NOIMPLIED - assumed 'LIBXML_HTML_NOIMPLIED' (this will throw an Error in a future version of PHP) in /home/ibcppsicanalise/www/testes/wp-content/plugins/wp-rocket/inc/Engine/Optimization/LazyRenderContent/Frontend/Processor/Dom.php on line 83

Warning: Use of undefined constant LIBXML_HTML_NODEFDTD - assumed 'LIBXML_HTML_NODEFDTD' (this will throw an Error in a future version of PHP) in /home/ibcppsicanalise/www/testes/wp-content/plugins/wp-rocket/inc/Engine/Optimization/LazyRenderContent/Frontend/Processor/Dom.php on line 83

Fatal error: Uncaught TypeError: DOMDocument::loadHTML() expects parameter 2 to be int, string given in /home/ibcppsicanalise/www/testes/wp-content/plugins/wp-rocket/inc/Engine/Optimization/LazyRenderContent/Frontend/Processor/Dom.php:83 Stack trace: #0 /home/ibcppsicanalise/www/testes/wp-content/plugins/wp-rocket/inc/Engine/Optimization/LazyRenderContent/Frontend/Processor/Dom.php(83): DOMDocument->loadHTML('<!doctype html>...', 'LIBXML_HTML_NOM...') #1 /home/ibcppsicanalise/www/testes/wp-content/plugins/wp-rocket/inc/Engine/Optimization/LazyRenderContent/Frontend/Controller.php(150): WP_Rocket\Engine\Optimization\LazyRenderContent\Frontend\Processor\Dom->add_hashes('<!doctype html>...') #2 /home/ibcppsicanalise/www/testes/wp-content/plugins/wp-rocket/inc/Engine/Optimization/LazyRenderContent/Frontend/Controller.php(119): WP_Rocket\Engine\Optimization\LazyRenderContent\Frontend\Controller->add_hashes('<!doctype html>...') #3 /home/ibcppsicanalise/www/testes/wp-content/plugins/wp-rocket/inc/Engine/Optimization/LazyRenderC in /home/ibcppsicanalise/www/testes/wp-content/plugins/wp-rocket/inc/Engine/Optimization/LazyRenderContent/Frontend/Processor/Dom.php on line 83