HamsterRage

joined 2 years ago
[–] HamsterRage@lemmy.ca 2 points 22 hours ago

"If so why don't people buy more 70's cars?". IMHO, this is actually the whole point of the OP's question.

[–] HamsterRage@lemmy.ca 20 points 1 day ago (2 children)

Everyone is concentrating on the crumple zones and safety at the crash. Remember that modern cars have features that make it easier to avoid the crash in the first place. Antilock brakes. Traction control. Lane assist/warning. Better headlamps, adaptive headlamps. Better suspension and handling. All things to avoid crashes.

All good reasons to avoid the 70's car.

[–] HamsterRage@lemmy.ca 3 points 1 week ago

They explained it more clearly later in the article. 4 weeks for the first year, then 1 week for each additional year of tenure. So a three year employee would get 4+2, which is the same as in Canada. But a 4 year employee would get 4+3 which is less than the statutory (1+1)*4 in Canada.

In Canada, once you get to about 6 years of employment, you can start to expect (1+1+2) * (# years). With a cap of about 80 weeks. You'd bust past the woeful 26 week cap with just 7 years of service.

And, BTW: You would need 23 years of tenure to hit that 26 week cap.

[–] HamsterRage@lemmy.ca 8 points 1 week ago (3 children)

Interesting, that doesn't even meet the statutory requirements in Canada, which is 1 week severence+ 1 week in lieu of notice per year of employment. One top of that civil case law will generally add another 2 weeks per year of employment for employees who have been with a company for more than 5 years. There are other factors involved in this however. The whole thing generally tops out at about 20 months, too.

[–] HamsterRage@lemmy.ca 3 points 2 weeks ago (1 children)

Around our house, it's "Department Store Christmas". I can only take a few hours at a time before I switch it back to "Groove Salad".

[–] HamsterRage@lemmy.ca 3 points 2 weeks ago (1 children)

It used to be much, much tighter, but I'm going back to the 1990's for this. Back then you needed to have a real-life presence across the country to get a top level .CA domain. Otherwise you needed to get one in a provincial subdomain, like .QC.CA or .ON.CA.

Provinces might even demand that you get a municipal level subdomain.

But no more.

I seem to remember needing to show proof, like articles of incorporation...but that might have been for getting a VeriSign certificate.

Last time I registered a . CA domain there was no verification of anything.

[–] HamsterRage@lemmy.ca 5 points 2 weeks ago

I totally agree. It has become second nature now...look on the label and if it says, "Made in USA", then put it back on the shelf.

[–] HamsterRage@lemmy.ca 9 points 3 weeks ago

Your boss's priorities are your priorities.

[–] HamsterRage@lemmy.ca 9 points 4 weeks ago

Beaker. Even has a smiley. *8-0

[–] HamsterRage@lemmy.ca 6 points 4 weeks ago

How to say you come from the States without saying you come from the States.

[–] HamsterRage@lemmy.ca 3 points 1 month ago (1 children)

Pedants, not persnicks.

[–] HamsterRage@lemmy.ca 12 points 1 month ago (1 children)

Then change the hours of the jobs, not the clocks.

 

For the past few years I've been building and maintaining website/blog at www.pragmaticcoding.ca. It's mostly about programming, and more specifically it's ended up having a lot of content about JavaFX with Kotlin.

Lately, I've been spending all of my time building out my own homelab and self-hosting the services that I need. I've got a little stack of M910Q's running in a Proxmox cluster with an HP T740 running OPNSense.

Since I've been spending all - and I do mean all - of my time futzing about with this self-hosted stuff, I thought I'd try to add some content to my website to help people doing the same thing. My idea was to make it more "bloggish", talking about the tricky things I've had to master along the way as I implement various services.

But I feel like there also needs to be some foundational content. Articles that explain concepts that a lot of people, especially people without professional networking experience, find difficult to grasp. So I've started working on those.

While I think of myself as mostly a programmer, my career (now, thankfully over) had me as an "IT Guy" more often than not. I spent 24 years at the same mid-sized company with a tiny IT department and simply had to get involved with infrastructure stuff because there was nobody else to do it. It was very hands-on at first, but as we grew I was able be limit my involvement to planning and technical strategy.

Since the mid 90's, we went from self-hosted physical servers, to colocated servers, to colocated virtual servers to cloud servers and services. So I feel like I have the insight to provide help.

Anyways, this is the first article in this new section. I've seen a lot of people posting questions about how VLAN's work and I know that it's mystifying to many. So I wanted to push it out before I have the supporting framework put together on the website, and it's just sitting there as the first post that's not about programming.

My goal is to provide practical, pragmatic advice. I'm not particularly worried if some particular facet of an article isn't 100% totally correct on some obscure technical level...as long as the article gives solid practical advice that readers can act on.

Anyways, take a look and let me know if you think this kind of article might me of use to yourself or other people getting started on self-hosting.

view more: next ›