Readit NewsI am not affiliated, but I recommend checking out https://www.forecastadvisor.com/ to see what forecasts are best for your city. I totally changed weather providers and it seems much better now.
'The Secret World of Weather: How to Read Signs in Every Cloud, Breeze, Hill, Street, Plant, Animal, and Dewdrop' by Gooley is a fun read for anyone interested in figuring out weather without a forecast (or to supplement).
- Get a dog! Seriously, going to dog bars, dog parks, and even walking the dog are all great opportunities for spontaneous social interactions.
- Group fitness classes can be good, even if you just chat with the instructor before or after class. Going regularly you're bound to talk with some of the other members.
- Arts classes (i.e., pottery) can be good, as it's usually a small group setting and you can chitchat while you're working.
Not the question, but another thing to consider is your body language when you're in those spaces. Try to be cognizant of it and present yourself to being "open" to conversation (especially in a bar setting). By that I mean, looking around, make eye contact, smile at people, don't be on your phone, and don't be afraid to say hi.
[edit: formatting]
“The Handbook of Self-Regulation”, Baumeister and Vohs
http://ndl.ethernet.edu.et/bitstream/123456789/28342/1/162.p...
OP may also want to explore mindfulness/meditation, which has been a huge QoL improvement for me.
Some resources I’ve found helpful: - Book: Adult children of emotionally immature parents - Book: How to meditate by Pema Chodron - Website on DBT: https://dbtselfhelp.com/ - Book: The Antidote: Happiness for people who can’t stand positive thinking - Meditation Apps: Waking Up, Headspace, Ten Percent. Also, if you don’t like one, try another. They all have distinct styles.
Seriously though, do therapy and hop therapists until one clicks. I read on here once “you can’t read the label from inside the bottle.” This type of work significantly benefits from a good outside perspective.
Also, OP, be kind to yourself and, as another poster said, allow yourself to just exist for a bit
1) With respect to not having whitespace: "Not everyone is as smart as you, and you need to ask yourself, do you want junior engineers working on your code to keep bothering you asking how things work, or would you rather your code by easy to read (and commented) so that they can pick things up on their own?"
2) With respect to complexity: "We are expected to build products that align with business objectives. New and experimental code belongs in your home lab and on your GitHub, not in a production environment."
Depending on how things go with #2, maybe offer to let the engineers spend 20% of their time working on lab projects to improve their product, with the understanding being that the rest of the time they are expected to build products with a minimum of complexity.
I think overall it comes down to trying to help them build empathy by showing them that they aren't the only one that will have to interact with what they build, as they are a part of a team.
An easy way to start is, like the parent suggests, with showing "How does making it easier to read or reason about ultimately benefit you?" (e.g., not having to be asked for help by junior engineers). The downside of this is it's kind of abstract, and ultimately a selfish motivator ("what benefits me?" over "what benefits the team?"), as another commenter mentioned.
One option that might be more tangible and team-oriented is to discuss design options as a team. Hopefully in doing so they can understand the complexity in their approach as other people ask questions. If you're able to structure in such a way, one trick here is to separate the design phase from the actual implementation phase. So, whoever designs the approach isn't the one that implements it (within reason -- you could also pair program here, with the whoever designed it as a reviewer and not the primary).
Some of this is also about them realizing what is obvious to them is not obvious to others. One tell here is if they use "why don't you just..." a lot when asked questions.
One phrase I use a lot on my team is "don't be a hero". Heroics in a team setting (willingness to write overly complex features, take on indefinite maintenance of code they wrote so others don't have to reason with it, etc.) are generally detrimental to the team overall. If they find themselves having the need to "carry the team" a lot, you could direct some of their energy/problem solving towards how they could help up-level the team overall or fix team processes.
Anyway, a bit of a ramble, but that's my 2 cents. YMMV.
Paper's never going to be replaced but I have definitely wished countless times for something that could copy a paper for storage instantaneously.
(Given Wacom's technology with cintiqs, I'm actually surprised this isn't a thing already.)
I assume you are referring to roe v wade, which is a case of where the precedent was wrong ín the first place (Abortion was pretty much banned everywhere in common law, so there was no precedent of it being an unenumerated right, for example) and was kept as a precedent because it was a precedent (ignoring the lack of underlying constitutionality)