Since so much enterprise software development is brain dead, this seems like no great loss. I feel no obligation to be present for employers that mindlessly demand productivity. If they want lines of code, then lines of code they shall have.
I hope this leads to a renaissance of writing computer programs as a hobby and a craft. I also hope that it helps some entrepreneurs get started and actually build a software company they want to work in.
"You can't control X" is not the same as "X is your fault". Earthquakes, for example, aren't your fault. I notice that people infer blame quite easily in response to statements such as these. I know I had to train myself out of this and in moments of stress, I fall back into it.
"Only you can choose to ignore what they say about you" is not the same as "It's your fault that you care about what they say about you". It's true it's up to you to learn how to ignore others' opinions of you, but that doesn't mean you deserve blame for the patterns in your mind. Maybe you are and maybe you aren't. Maybe it doesn't matter. Maybe it only matters what you learn to do from here, which probably depends on finding adequate support. I hope you find it.
Your thoughts and feelings are not wrong by definition. Unhelpful, maybe. An obstacle, perhaps. But not wrong. They can't be wrong. They just are. They simply exist. The question becomes how to find the tools to make sense of your thoughts and feelings, as well as to let go of the unhelpful and pick up the helpful. That's what I'd expect from your therapist: to help you do that. I'm sorry that you haven't had that experience.
"You just have to deal with it" seems utterly unhelpful to me, but "You're ultimately the one who needs to find ways to deal with it" seems undeniably true to me. It's not easy, but nobody else can do it for you. And you're ultimately responsible for the determination it might take to get there.
Those are my thoughts. I hope you find something helpful in there somewhere. Best wishes. Peace.
If "close enough" works, then it's nice to have the skill. Having the skill requires occasionally using it.
Where accuracy is important, since we almost always have a calculator with us now, that's a no-brainer.
Maybe more to the point, though, understanding how percentages work is wise. It's one of the few arithmetic topics that we encounter regularly in life.
In this case, 23% of 53 and 53% of 23 each have their own little trick, depending whether you'd rather overestimate a little with 1/4 of 52 or underestimate a little with half of 24. I find it handy to be able to think that way, especially for example when trying to get out of a taxi and paying cash.
I learned that when rest no longer leads to recovery, that is burnout and maybe even depression. Pay attention to this feeling and take it seriously. Good luck.
If you're thinking about what you could be doing, you might have some unhelpful conditioning related to "being productive" and other such myths of how to live "correctly". You might be able to think your way out of that way of being and you might need to talk to someone to do this, such as a therapist.
If you're worried about forgetting something that you need to do later or about some deadline sneaking up on you, then writing things down and setting reminders could help. I did a lot of this and it trained me to literally forget things that I didn't yet need to start working on without risking missing deadlines. I found it very freeing. Something like that might help you.
I hope you find some peace from something in these replies.
I like our local shared ownership model: neighborhood cat visits, we chill on the deck, I offer him water, he doesn't seem to need it, he wanders off. Every so often, there's just this cat at the back door checking in.
Name expands as I understand better the structural role of a thing. Duplication in names begins to become easier to spot.
Removing duplication in names means introducing helpful structures, resulting in shortening names again, particularly as the intent/purpose of thing becomes clearer.
Long names stay unnecessarily long when we don't notice the patterns that suggest the missing structures.
The more examples of this kind of thing, the better!
(And my preferred name for that is rolesByEmployee. In general, "values by key".)
Since so much enterprise software development is brain dead, this seems like no great loss. I feel no obligation to be present for employers that mindlessly demand productivity. If they want lines of code, then lines of code they shall have.
I hope this leads to a renaissance of writing computer programs as a hobby and a craft. I also hope that it helps some entrepreneurs get started and actually build a software company they want to work in.