Don't be afraid to take unskilled jobs to slow the financial bleed while you continue your search.

The key to finding a Job is absolutely networking. Take a look for local SW groups, defcon groups, hacker spaces, start up scenes, etc.

I've received my last few jobs through networking. I've been fortunate enough to not need to job search in a number of years.

Once your settled in a field, network network network.

But you need to know what field to do it in first.

You should broaden your searches. Both by location and vocation.

By the sounds of it you would be a good fit in any operational, logistical, or managerial role. See what remote opportunities there are Canada wide.

That would also print the colon

Edit: missed the separator token. Sorry guys

A good (technical) interview should feel like a fun conversation with a friend on the topic at hand.

Most people are trying to see if they'll like you, and that you can pull your weight. Assuming you're qualified the second part isn't an issue.

Practice with a friend or family member. Get comfortable talking about yourself, and post experiences. Get comfortable asking follow up questions. That comfort will let you be yourself during the interview so the interviewers can actually gauge your fit.

Try applying to NOCs and SOCs

Here's my testing recommendations

Testing methodology

To get consistant results, use a consistent method of test. If you're downloading a large file, always test by downloading that same file from that same source. If you're using a speed test service, use the same speed test service with the same server. If you're using a tool like iperf3, always use the same tool against the same iperf server.

Potential issues

Networks can fail from hardware issues, software issues and infrastructure issues. Since you don't control 99.9% of the infrastructure if the internet is involved, lets leave that for the last option.

Hardware Issues

The hardware involved you control are mostly your NIC, and your Remote Connection. For wired ethernet at home, this is likely a physical ethernet port on your computer on one end, and another physical ethernet port on a switch/router/ap provided by your ISP.

Testing Wired Hardware Issues

• Using the same switch and cable, run a speed test on another computer. If the issue persists, the problem is not with your computer, if it resolves, its related to your computer.
• Using the same computer and cable, run a speed test on another switch. If the issue persists, its not the switch or cable, its your computer, if it resolves, its not your computer.
• Using the same computer and switch, use a different cable. If the issue persists, it's not the cable and its either your computer or switch, if it resolves, its the cable.

With these three you can figure out what device is causing the problem.

Testing Wireless Hardware Issues

The hardware involved is the wireless NIC in your computer, the environment your wifi signal is in, and the wifi AP. The steps are much the same as testing for a wired issue

• Using the same AP and physical location, run a speed test on another computer. If the issue persists, the problem is with the AP or location, if it doesn't it may be your computer
• Using the same computer and physical location, run a speed test on another AP. if the issue persists, the problem is with your computer or location, if it resolves, it may be the AP
• Using the same computer and AP, run a speed test in another physical location. If the issue persists, the problem is with the computer or AP, if it resolves it may be the environment

Software Issues

The issue could be software related. Something like the drivers running on your laptop or connection point.

Testing Computer Drivers

You've already done this for your computer by dual booting. This proves the issue is not driver related, since the problem persists with two different sets of drivers.

Testing Connection Point Drivers

• You have less control over the drivers on your switch/router/ap. If the hardware tests resolve when using a different AP, then you can attempt a firmware upgrade/downgrade before replacing the physical device. This isn't usually worth the hassle since ISPs are quick to replace them with a service call.

Testing Computer Configuration

Your network settings could be misconfigured.

• If you are using DHCP, turn it off, and enforce a speed negotiation, IP address, subnet mask, and DNS server and try again. If the issue persists, then it's likely not related to your configuration. If it resolves it probably is.
• If you are using a static configuration, turn it off and use DHCP. If the issue persists, it's likely not related to your configuration, if it resolves, it probably is

Infrastructure Issues

If your home network is more sophisticated then an ISP provded router/switch/ap combo connected to everything over wifi and ethernet, theres more devices to troubleshoot. But if you have something like this, you probably already know what you're doing a little bit and wouldn't be making this post. But who knows! Re-run the process isolating each device and replacing it with something known good to identify whats causing the problem.

As for the internet, it's not a stable and safe place. Speeds vary drastically day to day. Internet weather happens and partial outages occur regularly. Don't forget that the service your using to speed test could be the issue itself. It's another component to isolate and test.

Process

Use the above steps to identify what device is causing the problem, and if its a hardware or software issue. Hardware issues are mostly resolved by replacing devices, while software issues are resolved with software updates and configuration changes.

Good luck and god speed!

Nala gang rise up!

That's hilarious

On average it takes 18 months to grieve a loss. Divorces are no exception.

I've gone through 1 divorce and some long term relationship breakups, pretty close to when loved ones die.

Eventually it's replaced by new automated defenses and behaviors. Hopefully not too unhealthy.

I thought the other parties didn't run candidates in pm ridings out of mutual respect

Productivity is a measure of how much you can get done in a block of time. It doesn't have anything to do with end goals.

It's a bit of a silly question like asking what fuel mileage has to do with where you drive to.