CrazedLumberjack

In Canada employees may have a limited expectation of privacy on work computers.

Quoting from this article, which references the same supreme court case as the above article:

Mr. Justice Fish, writing for the majority of the Supreme Court, delineated the following instructive principles:

• Whether at home or in the workplace, computers are reasonably used for personal purpose and contain information that is meaningful, intimate and touching on the user’s biographical core;
• The user may reasonably expect privacy in the information contained on their computer particularly where personal use is permitted or reasonably expected;
• While ownership of the computer and workplace policies are relevant considerations, neither is determinative of a person’s reasonable expectation of privacy;
• The totality of all the circumstances will need to be considered to determine whether privacy is a reasonable expectation in any particular case;
• Workplace policies and practices may diminish an individual’s expectation of privacy in a work computer; however they may not in themselves remove the expectation entirely;
• A reasonable, though diminished expectation of privacy, is nonetheless a reasonable expectation of privacy, protected by s. 8 of the Charter and subject only to state intrusion under the authority of a reasonable law.

If the domain registration lapses and a malicious actor was to pick it up it could cause issues potentially.

She totally hand-crafts (mouth-crafts?) her cardboard boxes to be comfortable hideouts for her.

Being a long term patient of neurologists (migraines, seizures) and having a wife who works in neurology I tend to believe the doctor she worked with who stated that once you have migraines, all headaches are a migraine clinically. They’re just more or lwwa debilitating based on severity.

Interesting, I've always categorized them by whether they go away from standard painkillers or if I need to use rizatriptan. Migraines are much more frequent for me than normal headaches but I still do have ones that go away when I take some tylenol or ibuprofen. I've been lucky so far that my migraines almost always go away after 1 rizatriptan, and I've never had one make it past a second one.

While it was awesome experience but man, it ate huge chunk of my time.

So much this. I spent so many hours between 2010-2014ish in fleets and on jabber/irc/vent but I just can't devote that much time to a game these days. Tons of great memories and no regrets.

Your user image shows up fine for me, but OP's doesn't.

The concepts you should know/are expected to know are really going to depend on the company you're working for and even the team within it. In general as a new grad you're expected to be learning, and you will slow down the dev that's assigned to be your mentor. That's 100% okay, it's part of their role as a mentor to be interrupted by you and help answer your questions so don't feel bad about asking for help when you need it.

One useful skill you can start to pick up immediately is learning how to discover things within the company. If you ask your mentor a question and they just give you the answer, don't hesitate to ask them to show you how they got to that answer. Whether it's debugging, navigating documentation, etc, the most successful new hires I've seen have been ones who have showed that curiosity and used it to learn how to navigate within the company's codebase/systems.

Another big change when you've only done internships in the past is to remember that your career is now a marathon, not a sprint. During an internship you often have a fixed amount of time to achieve a set goal so you can push hard and get there, knowing you're done at that point and can take a break. Now that you're working full time there will be more work waiting for you so if you keep pushing too hard you will burn out. Through trial and error you'll need to find a pace that you can work at sustainably over an extended period of time. Yes, there will be times when you have to push hard for an important deadline or if things are on fire, but hopefully that will be the exception and not the rule. I don't have any good advice for proactively avoiding burnout though. It's something that you have to learn by experiencing it and trying to reflect and see if you can identify any early warning signs. I'm almost 20 years into my career now and it's only in the past 4-5 years that I've started to be able to catch burnout before it happens and flag it to my manager.

I'm super lucky to have a couple of close friends who I know I can call on. When my dad was dying of cancer at the end of last year, they both took turns coming over so I had company as a distraction 3-4 nights a week. After he passed they even took time off from their jobs and traveled out of town to his funeral while refusing my attempts to pay for their hotel rooms. I'm eternally grateful for them and I don't know how I would've made it through that without them.

Keep fighting the good fight. In my experience with SRE/automation work, people tend to fight change just because it's change and not realize just how much time they're spending on toil and similar tasks.