I use it as my main visual plain text editor, but use vi on the CLI and JetBrains stuff for coding. The use cases I like it for:
- copy/paste ANYTHING, every tried to copy something from the browser and paste it to the CLI and nothing happens? Anytime I have difficulty pasting text, I paste into BBEdit first and then copy it again to paste into its destination. BBEdit eats any kind of text, it's amazing.
- Large files, I've found nothing is faster for opening and editing large file >1G
- Note taking - Has a few advantages over other options (Bear, Notes, Evernote) here that I don't miss the rich text features of those others. 1) No automatic autocorrect for spelling but the manual autocorrect is still there which means I can write tech jargon without getting frustrated 2) Autosave without having to think of a title or folder 3) Immediate start up time, no waiting for the doc to load even if I have >100 open docs
- batch text processing - if I need to do find/replace I tend to go with BBEdit over CLI, I can build up the regex pattern and have undo capability. Use it a lot for making SQL statements from lists of ids and the like.
We are doing distance learning in a small pod with a caregiver with our elementary schooler. We are rotating houses. The most difficult part, surprisingly, is finding other families with the same needs as you (age, cost, siblings, distancing level).
I chose to go pod since it adds a little more socialization without nearly as much risk as a larger group.
A fourth: have a specialization either in a technology, part of the stack, or in an industry. That allows you to stand out for roles that really need someone with experience in that area, right now.
That said, I think your 3 recommendations lean more to a "how to play the interview game on easy mode" than every developer should to do this. I feel like I may be exaggerating your intent a little, but it did read a little like "Go to MIT, work at Google, write a famous blog" :)