Raineer
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.
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.
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.
I think the implication that NIST lacks integrity is unfair.
I don't think he gives a damn about the product or how it functions.
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.
Citation needed.
https://www.denverpost.com/2019/12/30/erie-victim-financial-...
Like - I even agree with most of what was typed, but I don't see it's relevance to anything here.
I just love the delivery on "where did you get that camera??"
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.
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.
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.
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.
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.
Exciting results, all the same.
Mine was built with a much older version of this board - https://store.uputronics.com/index.php?route=product/product.... I like using the HAT as a dedicated solution instead of the USB route.
The temptation will always be present for (some) organizations to use Open Source as a crutch to underfund development and support. I think it is a phenomenal way to grow your product in ways that you initially didn't expect from your customer base, but it cannot be the way in which your main support is bolstered.
Their work on both the firmware front and with Pop!_OS should not be overlooked. And, it should be mentioned, if one is familiar with their whole product line - they now go far beyond just laptops for the open source community. And their powerhouses are absolutely not from some other OEM.
No judgment, just bemusement. I will always choose the freedom to configure over a set-in-stone approach.