I worked at a company that used Teams for video conferencing and Slack for chat. The fact that they specifically said "Teams for video conferencing" reminded me of that.
To be honest, it's not awful if you're only using it for that.
I think people not confined to a wheelchair have more options for physical training. You could say that's an unfair advantage to people actually requiring the chair.
My dad worked on one of the radar stations on the dew line in Canada. He's got some cool photos. Like photos of a Polar Bear looking in the windows of his cabin.
I had an alarm clock for a long time. My alarm set for 6:00am and I would wake up and look at the clock at 5:59. So, I would actually just wake up just before the alarm.
I don't use Ruby, and don't do OOP either, but my favourite talk is still Sandi Metz's "All The Little Things" and I think that's where she says "prefer duplication over the wrong abstraction." That's really changed me. I've since been seeing DRY and other misapplied dogma in a new light and have grown much over the years since.
I use both command line and GUI as part of my workflow.
I use GUI mainly for doing "visual" stuff like looking at diffs, and commit and merge history (especially across branches), etc. In my opinion, this stuff is quicker and easier and looks better on a GUI.
I also use GUI if I have several changes and I only want to stage some of them (or partials). It's easy to go through and stage/unstage things on a good GUI.
For everything else I use the command line. Almost any time I want to actually DO something (like commit, push, pull, etc), I do this through command line.