I have the role of "chief troubleshooter" in my engineering group. I have a bit of a nervous tic that forms when I hear absolutes like this.
Don't assume the customer is always an idiot. Don't assume ANYONE is always an idiot. It limits you as an engineer.
Listen to everything. You don't have any need to abide any of it, but listen to it all.
I've had some of the least-qualified people throw out something which absolutely ended up being insightful, although sometimes in a way they didn't expect.
I was commenting on this just last week. Gaming on Linux has exploded since the Steam Deck was released (just as all Linux users were hoping it would).
All the effort which went into Proton to get games working on Steam Deck has done wonders for the desktop.
It used to be that you could play AAA games up to about 2 years prior (same story like macOS today), but now you can play almost anything on desktop Linux. I even run HiDPI / 5K monitor and it all works now, at least on Arch.
The only notable exception (truly, a surprise), at the moment, is Starfield not working on day 1. This was surprising, but the reasons net down to GPU drivers - and progress is already being made.
I have loved programming (literally) my entire life. Some of the books I learned to read on was TS-2068 BASIC program listings in kindergarten.
Luckily for me, before I got too far down the road into choosing a major, it became clear to me that I would never love getting paid to program. Writing code as a career was not going to appeal to me. Being able to keep it as a hobby, where I can choose how much time I put into it, has kept me happy.
I will always wonder about "the road not taken", but I do think others are coming to that realization.
If you're going to blame NIST for what NSA did in this case - you might as well say "don't even trust anyone for digital privacy" since the NSA already collects literally everything from everyone.
I think the implication that NIST lacks integrity is unfair.
And the cost of the material has nothing to do with the argument. I don't know why you'd imply that it "costs precisely the same", as no two materials would ever be exactly the same. But you don't adjust your pricing 39 cents either direction - you decide on a price based on what people will pay.
"This is why things like 'evidence based' medicine is so dangerous -- we don't have evidence for the vast majority of impactful conditions, simply ignoring patients with these conditions is not a workable solution."
Yeah this was my thought, too. I was using PowerDNS to do this sort of thing within a basic home environment. But I have no idea if it has the necessary features to keep a production environment happy. It was fun to play with.
The fact that previous salary has anything to do with future salary comes from the same swamp of misinformation like "it's illegal to discuss your salary with your peers."
My approach when dealing with future salary is to tell them my previous job paid me ((what I want from next job) - X %). Previous salary doesn't appear in the equation.
I know it's not truly this simple, but if the file extension is ".ino", I feel like your detection algorithm should be free to use that as a massive indication it is Arduino code.
The boot-up time is really a killer. I also just can not get used to the input/keyboard of the nSpire.
My actual workflow is to use DM42/HP-35s for anything I can do with those, and if it's more complicated, I'd rather launch Octave or MATLAB. I just can't make my nSpire work for me.
Yeah I pay the same. Sure I hate Google and yada yada... But if the call for money is "we will show you no ads, and your money will go to creators", and it is a realistic amount, yes I will pay it.
I run ad-blockers everywhere (and I know there are ways to block YT ads), but will still pay if you give me this reasonable option.
When I encounter it, I feel it's often a hatred of the "doers vs the thinkers"
My career path was 25 years engineering, before migrating into a hybrid EE/PM role as sort of a natural progression from being "the engineer who knew how to run the project". Once I started learning the more formal approaches to PM, it uncovered an entire world of engineers who have an incredible hatred of any sort of planning of any kind, because all planning time is wasted and we should all just be doing.
The parent comment here feels the same way. Hatred towards research because it's all theoretical (I guess?). It seems clear as day that the best approach is a marriage between the two.
I feel this is an overly optimistic view. There's not many situations in the last 50 years where "businesses being able to charge less" have led to them actually charging less. It reeks of Telcos telling congress how much new laws will drop their prices, then they fire half their employees and raise prices anyways.
This is a microcosm of most of my issues with crypto discussions. In a (quite naive) vacuum, the arguments sound great. If you wanted to run Earth 2.0 with crypto, have at it. It doesn't fit in alongside the existing systems and, by the time it becomes "the main system", you can be certain that those in power have modified it to have the same issues as the original system we all hated.
I have the role of "chief troubleshooter" in my engineering group. I have a bit of a nervous tic that forms when I hear absolutes like this.
Don't assume the customer is always an idiot. Don't assume ANYONE is always an idiot. It limits you as an engineer.
Listen to everything. You don't have any need to abide any of it, but listen to it all.
I've had some of the least-qualified people throw out something which absolutely ended up being insightful, although sometimes in a way they didn't expect.