Skip to main content

Gaslighting & Emotional Manipulation Among Kanyakumari Parents

Lately, I’ve been noticing a curious pattern in the behavior of many parents from Kanyakumari, particularly mothers. There’s a recurring tendency to project emotions—anger, sadness, happiness—onto their children, not because the child is actually feeling that way, but to communicate something about the parent’s own desires or discomforts.

It’s a subtle form of gaslighting. For example, if a mother doesn’t want to accompany her husband on a social visit, she might say, “Our son is in a bad mood today, let’s stay home,” even when the child is perfectly fine. The child becomes an emotional excuse, a buffer used to influence someone else's behavior without direct confrontation.

Sometimes, these projections go deeper. If a mother-in-law dislikes her daughter-in-law, she may subtly portray her own son as short-tempered or unstable. The goal isn't to protect the child, but to create distance between the couple—without ever saying so explicitly.

Why do I frame this as a Kanyakumari-specific pattern? In this region, unlike many other parts of Tamil Nadu, there seems to be a strong social undertone that encourages parents to manage their grown children’s public image—or use them to navigate family dynamics. It's less about nurturing, and more about subtly using the child as an emotional tool in adult relationships.



Disclosure:

The following ChatGPT prompt is used in this blog post:

Please fix the language of the below text and highlight the changes in bold:

Comments

Popular posts from this blog

BehaviorS.js - An alternative to Behaviour.js, event:Selectors and Low Pro libs for unobtrusive JavaScript programming

BehaviorS.js yet another unobtrusive JavaScript library similar to Behaviour.js and event:Selectors but in implementation uses hash based lookup without extending elements; so presumably it should be faster than the rest. The original script and idea was by JLof ; I extended it for DOMContentLoaded support, optimized a bit to avoid scanning of more depths, and added new rules support. I wanted to document the plug a long time and just got time to do it. For the time being BehaviorS.js is available here Update (2006-09-11) : Coralized the link to BehaviorS.js so as to save the load on free brinkster.com webpage Update (2006-09-27) : If the coralized link to BehaviorS.js doesn't work, use http://www21.brinkster.com/guideme/BehaviorS/ Update (2025-06-07) : Now available in https://github.com/rrjanbiah/behaviorsjs

Save American College, Madurai

This post was written in 2008 and outdated now. For update, please check Save American College, Madurai (Update 2011) Update (2011-01-16) : Save American College, Madurai (Update 2011) I'm highly privileged to have 3 degrees (B.Sc. (Spl. Physics), PGDCA and MCA) from The American College, Madurai, South India . Unlike other "commercial" colleges, American College has given room for poor students and uplifted them. And unlike other "elite" colleges who'd give seat only for "intellectuals", American College has produced geniuses. In the recent months, the saddening thing is that the college is under divide (Principal Vs. Bishop). Here is the email I sent to alumnae lately informing about the informations that I received about the developments: Update (2011-01-16) : Save American College, Madurai (Update 2011) All: I was thinking that the " Save American College " campaign was a FUD . But, when I tried to understand the problem through my...

Solved: "Ports" Tab Not Visible in VS Code (WSL2)

None of the solutions I found on Reddit or GitHub worked, and most of the related GitHub issues were locked. So I'm documenting this here for future reference. Problem When using WSL2 in Visual Studio Code, the Ports tab—needed to access your application in Windows browsers like Chrome or Edge—doesn't appear. Even the Ports-related options are missing from the Command Palette. Solution After a lot of trial and error, here's what worked: Run npx serve in the VS Code terminal. It will output a URL such as http://localhost:3000/ . Click the link (or use the Follow Link option). This will open the app in your default browser. You may notice that it opens on a different port (for example, http://localhost:64198 ). At this point, the Ports tab becomes available in VS Code. After this initial trigger, the Ports tab seems to remain available in future VS Code...