So, on one hand we have that "Tech Talent Strategy", which I assume comes from the demand for more IT workers globally. On the other, we have Canadians such as yours truly who would like to upgrade from a Helpdesk position sooner rather than later. I realize that sample size=1, but why don't we properly train permanent residents instead?
(Also don't forget the IT job market which has slowed practically to a halt, as a direct opposite of that Strategy)
Email: hn@ (domain name mentioned just a line above ^^)
New job planned date: Soon (Valve Time)
------
Hello there! I have 15 years of experience in Level 1 Tech Support/Junior Sysadmin roles with a bit of scattered programming here and there, and I would like to jump ships and land a role as a Junior DevOps/SRE. To skill up on that matter and get on-par with the market, I am currently following a DevOps course online (Nana's DevOps course to mention it) as well as a few other primers courses in the pipeline such as AWS Fundamentals, Python, Golang, etc on LinkedIn Learning. If you are from a company who cares about your employees skill progression (where learning is expected and encouraged), I think I may be a good fit- hit me up! As for a date for a job change, there is an ongoing migration at my current workplace I wanted to complete before jumping ships. Mostly new AD Domain and new fleet of PCs to deploy, then I should be good for a switch. No clue for a date at the time of writing my post, however. Thanks!
Email: hn@ (domain name mentioned just a line above ^^)
New job planned date: Soon (Valve Time)
------
Hello there! I have 15 years of experience in Level 1 Tech Support/Junior Sysadmin roles with a bit of scattered programming here and there, and I would like to jump ships and land a role as a Junior DevOps/SRE. To skill up on that matter and get on-par with the market, I am currently following a DevOps course online (Nana's DevOps course to mention it) as well as a few other primers courses in the pipeline such as AWS Fundamentals, Python, Golang, etc. If you are from a company who cares about your employees skill progression (where learning is expected and encouraged), I think I may be a good fit- hit me up! As for a date for a job change, there is an ongoing migration at my current workplace I wanted to complete before jumping ships. Mostly new AD Domain and new fleet of PCs to deploy, then I should be good for a switch. No clue for a date at the time of writing my post, however. Thanks!
> IT distributed sticker packs with all the french chars on them after the inspection
They had to. It's either "Product maker has to provide you the French labels, or if they don't, print your own". Literally. I remember a certain VoIP desk phone company shipping us "universal" labels with graphic symbols, that was considered acceptable by the OQLF since there were no english words.
IT has generally a bad opinion on OQLF precisely because of these kind of ridiculous requests they have to comply to.
I would love the OQLF to try. On my main PC, I use an Ergodox clone, basically a kind of split keyboard. Keycaps for said keyboard are tricky to find in sets that fits for every key (unless I buy them per piece I suppose), and that's for a basic English-US keyboard. Anything else is virtually unheard of- let me know if I am wrong. Anyway, using English keycaps is a big no-no from the OQLF and would require me to switch, but to what?! Here's the kicker: I am typing that with the Bépo keyboard layout, basically a French Dvorak. This would require me to make a special request to a keycap maker, as anything non-alphabetic is really different. So installing a blank keycap set with unmarked keys would be the cheapest way to go about this problem, but I don't think this would pass the OQLF requirements neither.
OQLF suggests but in no way requires the Canadian Multilingual keyboard. Typing in French, with associated keys properly marked, is what matters to them.
The companies I worked for are headquartered in Quebec (with the exception of my current job), so I can only confidently comment for the "internal to Quebec" situations. I recently joined a company that was acquired by a bigger US company, and now all company wide communications are bilingual since then. ERP was already bilingual since the 90s as my direct employer is basically Canadian-wide.
I know the basis of these regulations is to give Quebec employees not fluent enough in English the power to ask/require a fully French environment. I BELIEVE this can escalate up to the OQLF being able to fine companies not being able to provide a French environment to their employees, but don't quote me on that.
As far as english language software is concerned, most Quebec employees have a varying degree of "letting go" on this matter when confronted to English messages, as long as their internal documentation/knowledge let them know what messages are considered normal in their work process, even if they don't understand fully what that means. The OQLF, however, believe this is a major problem to be dealt with yesterday: IT HAS to make available said software in their French version, if the software publisher actually publish a French version. If not, I believe you are encouraged (forced? not fully sure) to ask the software developer about availability.
Even if the software developper released a broken (or even partial!) French version using Google Translator, it becomes THE version to deploy, no buts.
> Quebec can zing you if you hire a Quebec resident and aren't prepared to allow them to work in French, even if they don't speak French themself.
For the uninitiated, this means having all UI elements in French, (OS, software, ...) as well as all things physical like keyboards signs, everything.
Even if for example I am perfectly capable (and actually prefer, to lookup errors messages online for example) of working in English, the OQLF still requires Quebec employees to be exposed to French language first and foremost, regardless of users preferences.
Source: IT Guy being on the receiving end of said directives.
I *had* to get myself out of lurking mode to reply specifically to you; this issue seems widespread for 1st-gens Ryzen. I see your chipset also is close enough to mine (X370), and I felt a strong "déjà vu" by reading your freezing symptoms.
I reused my now old X370 Ryzen build to run TrueNAS Scale (Based on Debian), and have hard lockups like yours.
My personal notes on the subject seems to stabilize things a bit but not completely, and it's a mixture of BIOS Settings Tweaks and Kernel boot parameters that seems to help partially. Things I tried/applied with varying degree of success:
- Disabling Cool&Quiet
- Disabling C-States
- Gear Down Mode: Disabled
- Power Down Mode: Disabled
- VDDSCR_SOC: Offset by +0.00625v (seemed to stabilize things on Windows)
- Someone in the kernel bugreport mentionned the need to power off (as opposed to just reset) so all the BIOS Settings are applied correctly (didn't try it myself yet)
Long ago, I wanted to make a microservice that uses choon.to as the domain, pointing to popular shoutcast streams. The goal was to have a regular HTML webpages with the stream info served when using a browser, but send HTTP redirects to the actual Shoutcast stream source when media players being used to open the same URL. I thought having to paste into Winamp/Foobar2000 "http://choon.to/difm-trance" * was more user-friendly (or marketable?) than a bunch of numbers like "http://12.34.56.78:8888".
*: Although I was more of a di.fm Trance listener back then, another Trance channel, Afterhours.fm, still uses choon.in today as their shortcut domain.
(Also don't forget the IT job market which has slowed practically to a halt, as a direct opposite of that Strategy)