Ten components of being compassionate to yourself:

1. Self-friendship: treat yourself at least as well as you would treat a friend who is going through the same situation

[thread]

2. Worthiness: remember that you have value (as all people do), and that your happiness and preferences matter.

3. Self-talk: notice when you are saying something mean to yourself (aloud, or in your head), and rephrase it in a gentler, kinder, more considerate way.
4. Connectedness: reflect on the fact that, whatever challenge you are facing, there are others who are also facing a similar challenge. You are not alone in your pain.
5. Change: note that everything changes with time. If you are dealing with feelings that are difficult to stand at this moment, they will subside. This too shall pass. Things are usually not as important or permanent as they seem to us in the moment that we are focused on them.
6. Self-empathy: orient towards yourself with tenderness, understanding and compassion, especially when you are suffering. Take on the perspective that you would towards a child or loved one that was hurting.
7. Self-acceptance: remember that you, like all people, will always have flaws, and that’s okay. Being imperfect is just part of being human. You can fully accept yourself, flaws and all, and still aim to continuously improve.
8. Self-patience: note that everyone has their off days, including you. You’ll have times when you mess things up, don’t get anything done, act in ways you regret, and so on. Be patient with yourself, as that usually works out better than being angry at yourself.
9. Self-like: remember all the good things about you. Remember your greatest strengths. Remember why other people like and love you. There are good reasons to like yourself, but you may need to actively work to remember them.
10. Self-observation: notice how you are actually doing. Carefully observe the difficult thoughts and feelings that you are having. Note what they are, without trying to escape them. What words run through your mind? How exactly do you feel, in your mind and in your body?
Heavily inspired by Kristin Neff (@self_compassion)

See her website, book: https://t.co/Brk3BQfBSX
And her scale:
https://t.co/VAQnMvNx9d

More from Life

“We don’t negotiate salaries” is a negotiation tactic.

Always. No, your company is not an exception.

A tactic I don’t appreciate at all because of how unfairly it penalizes low-leverage, junior employees, and those loyal enough not to question it, but that’s negotiation for you after all. Weaponized information asymmetry.

Listen to Aditya


And by the way, you should never be worried that an offer would be withdrawn if you politely negotiate.

I have seen this happen *extremely* rarely, mostly to women, and anyway is a giant red flag. It suggests you probably didn’t want to work there.

You wish there was no negotiating so it would all be more fair? I feel you, but it’s not happening.

Instead, negotiate hard, use your privilege, and then go and share numbers with your underrepresented and underpaid colleagues. […]

You May Also Like

A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.

Legacy site *downloads* ~630 KB CSS per theme and writing direction.

6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices

https://t.co/qyl4Bt1i5x


PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.

735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices

https://t.co/w7oNG5KUkJ


The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.

The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.