Hardware info (hwinfo) or similar. Be able to check all voltages, speed and temps while testing new hardware. For example my ARC A770 has little to no info, and shows running at pcie x1.
Edit: mistakingly thought link width was x4, but looking at it again shows x1
This is my take on this. People blaming the software but the truth is that no software can be trusted. Make backups. Make mistakes and learn. Sometimes it will be painful, but those are the most valuable lessons
Well, it was addressing the pay issue, and it is the most secure path to higher paid position fast. Moving on to new stuff comes naturally and the industry will push you to their next hotness, so not really a problem.
If your goal is to make yourself more valuable to employers/clients the best path is to specialize in some critical and niche enterprise tech. People that are good at stuff businesses were lured into using get paid very well. In my case it was SharePoint, but that’s just an example.
Knowing your way around the OS is taken for granted in these positions, so you have one piece of the puzzle, which is great, but you need the other pieces.
But be careful, if I have to choose between two experts, one with basic win+linux and the other only linux, I’m choosing the former.
I recall Louis Rossmann saying something along those lines, and sounded perfectly reasonable to me.
Technicalities aside, TS is being pushed by MSFT in their SaaS custom components, and that right there will keep it relevant a while. MSFT is known for changing names a lot, but not for killing technologies.
After over 5 years of writing TS, I have had to do plain JS sometimes, and it is scary. It feels like walking blindfold. I’m spoiled.
Nothing wrong with it if you just ignore the spam and karmawhore social feed. I use it for visibility, so employers can find me if they wish. My current job was from a LinkedIn search from my employer. I get around 2 or 3 legit offers a month.
deleted by creator
I recall having the image not found error last time. A mix of creating the USB with another program and tinkering with bios solved the issue. Sorry can’t be more specific, but Linux is all about tinkering, so have fun :)
Doesn’t happen as much, but family and non tech friends would present me to other people that “worked with computers” thinking I could take new job opportunities. They were always wildly unrelated to my field.
I know I know,… they acted in good faith, and probably could have adapted a bit, but like 30 years ago there was a lot of overlap and systems where somewhat similar, but now somebody trained in Linux kernel maintenance isn’t going to learn how to create SharePoint SPFx webparts. Development is very specific now!
One line is fine if used wisely, everybody does it for readability. The issue is when you need more than one.
Myth: code can be ugly as long as it works, don’t spend company time on making it look good or on minor optimizations.
The truth is that you can tell when effort has been put into a job. Even if it just works, the lack of discipline means that in the end it will be difficult to maintain and probably will fail in unexpected situations.
Every language has its conventions, but if I spot more than a line of separation between blocks of code, that is a common telltale sign of noob. Run from that shit.
I only use 2 PCs with windows. An old laptop with XP I use for vehicle diagnostics and repair manuals, and a Win10 laptop my employer lent me for work. Option number 1 for both.
Yeah, monitors were somewhat dumb, just received and did what the vga output asked to do.
The noise most likely came from the semiconductors that controlled the magnet field that directed the rays onto the screen. These components are selected for a specific speed that the monitor can handle. So going under or over it’s spec can make something resonate in the audible range, and could even destroy the components if stressed too much.
The thing is that for each resolution and refresh rate you had two values to configure, one for the vertical speed in Hz, and horizontal speed in kHz. These values were usually specified in the owners manual. Typos can happen, and this was quite a risky operation.
A 19" monitor was quite big for the day, and expensive! I hope your gf didn’t beat you up too much for that :)
Not the installation strictly speaking, but my most “funny” fuckup was setting up xfree86. There was a configuration for crt monitor scan frequency that you had to setup. I messed up something and the monitor started to squeel like crazy and quickly hit hard reset in panic.
The monitor didn’t die, but it had a slight high pitch noise to it after.
In this situation the magnets act much like a spring, so imagine changing the magnets on the stick and the car for a simple spring. That is much more easier to visualize.
Not sure in Linux, could be a driver or kernel configuration. I don’t know a way to double check it. When booting into windows it’s at x16. So not a hardware or bios issue.