Skip to main content

Cabals and cynic bossism -- destroy team

Like I mentioned before, I often used to say that "trust is the binding force and hope is the driving force".

The things that destroy the team I have noted are:

Cabals


They are always opinionated, push themselves, bypass their reporting people/hierarchy, look for other cabals to understand the "shortcuts", etc. I find these people are quite damaging, they can never trust their reporting people--even though the reporting person is quite rational.

Cynic bossism


These people will never trust their immediate subordinates. They'll constantly spy their subordinates as they're panic and will try to see if they have better subordinate below their immediate subordinates. By doing so, they always damage morale of their subordinates, their spirit for the team, etc. Often these people will have their enemy within their own / peer level than from sub-levels.

Though many times I have noted that these people are quite damaging, till now, I have no experience in "handling" them. Now, I have started understanding how to fix them.

Comments

Popular posts from this blog

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...

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

Mrs. Sujatha, Marriage, and Misunderstandings

I recently watched an interview featuring Mrs. Sujatha on the Aval Vikatan YouTube channel, and I couldn’t help but write this post in response. In the video, she indirectly expresses regret about her relationship with the late writer Sujatha, implying that they lacked the kind of emotional bonding that today’s couples supposedly enjoy (?!). She also mentions that he would get angry at home, in contrast to his calm public persona. She suggests that they didn’t talk much—ironically, I vividly remember Sujatha’s own writing about the relationship between actress Shobha and Balu Mahendra, in which he quoted something his wife had said! Toward the end of the interview, she talks about the wealth and royalties he left behind, suggesting that material things don’t matter. ( It’s ironic—men spend their entire lives working to build wealth and security for their wives and families. ) What struck me even more was the comment section. Most of the viewers seemed critical of writer Sujatha, e...