I hate that so much. It's everywhere. An example is a bug with discord. They wanted me to restart my phone, reinstall the app, what are my versions, what phone am I on, what settings, etc. After all of that they go "oh that's a known issue." Whyyyyyyyyyyy. I get that multiple things can have the same symptom, but maybe start with that. Not like I signed any NDA so they aren't hiding it's an issue from the public.
Maybe I shouldn't have said cluttered. More like programs mess with things and don't always put them back. There are a lot of Microsoft support forum posts that had to reinstall Windows to fix weird issues that only started after the install
In my case it's not about performance, it's about usability and disk space. And again, that time I somehow started a WiFi access point and couldn't find anything online to turn it off. That laptop also at some point had the new folder option get removed from the right click menu. I had to copy/paste one. There are a lot of weird things that can happen over the years.
Honestly I should. Registry and stuff gets cluttered. Programs don't uninstall cleanly, or they change settings I can't find. On one machine I somehow set it up as a wifi print server or something and for the life of me couldn't find a way to turn it off. But it's such a hassle to setup a computer.
When I was in uni I would repeatedly get told that such issues with their software were fine because the lowest N quizzes/homeworks/etc wouldn't get counted. So instead of spending that leeway on a bad day I had to use it on their servers being down or whatever.
This is great and I'll try out pyright ASAP on my current codebase. The people who wrote it evidently didn't have any type checking running (despite I think 3+ linters??) so it's a nightmare of
> "well the checker accurately reports it will be type X in an error case not Y"
> "but we never get type X"
> "Then we don't have good enough coverage"
It's so easy in vscode, but it isn't on by default like the c/c++ one I guess because too much legacy code would cause infinite errors. And the age old problem of .pyi files lying about types.
Good to recognize stupid questions do exist but so does anxiety around asking necessary questions. The engineer I'm mentoring said they'd ask lot of stupid questions. But we're working through them. A lot of them were things I wondered too, like "this current reading doesn't make sense because the upstream supply is saying it's taking less current" but it was a nonlinear buck regulator. I offered to explain more but they just sat with it a minute, I offered again, but they said they were ok. My viewpoint is to give just a hint and then offer more so they can still go through the thought process on their own, which is really what I'm trying to teach.
Well no, your comment answered that we need training because the dies are made cheaply. But no amount of money would prevent the need to train out static and dynamic delays. If it wasn't in the controller it'd be in the memory and the question of why it's needed would still be relevant.
It's so weird to focus on the hypothetical scenario of this impacting corporate environments? This is the first good feature Windows has announced (at least on paper for desktop) in recent history and the author is concerned that what, people will play video games at work because of it? As if Minesweeper and Solitaire and people saying "can you repeat that I was multitasking" don't exist already?
And as per usual with journalism I disagree on the set of information provided. They mention the Ally as having received this feature. But they don't say how well it did or didn't do on there. The link if basically just another press release about this feature from back even it was announced, so there should be either benchmarks or a note that 9 months later they still haven't released the feature.
Can't comment on the wire bonding quality but yes you're not supposed to sonic wash anything with an oscillator. This includes ultra and mega sonic. I had always thought it was because you could damage the crystal or mems structures, so color me surprised to see this failure mode, though there still could be a shift in frequency that the scoping wasn't able to see.
I tried looking at an exemplar ECS tcxo datasheet and didn't see anything in there about washing which is surprising but it also doesn't say not to crush it with a hammer so maybe it was assumed. That's bad on them.
As for SMA to 0.1" headers: yes these are very cursed. But RF designers love putting SMAs for every connector on an eval board (power, enable, whatever) and those come in handy.
I think the difference, though maybe I'm incorrect, is that when we have interns on our codebase they get restricted permissions. Can't push to prod, need pull requests with approvals and reviews, etc. Certainly can't delete backups. Whoever setup the robot's permissions did it wrong. Which is interesting because early on there were people complaining that these AIs refused to push to main, but now this stuff keeps happening.
I just want to be very clear in understanding you: are you saying that these women (who are known and named) who were victims when underage (factually, not ""), should not be viewed as victims because it's a way/fact of life that powerful people will abuse girls?
I thought security chips put (extra?) metallization over top the logic to prevent the microscope problem. Do they not or can that still be defeated? I guess if you're careful enough you can strip off that extra layer
I guess we only see the ones that don't in the news. Makes sense. I have yet to see one of these where the data is encrypted and they M'dITM to get it, but I'm sure it's happened.
I've thought about it but haven't checked too hard: can they not do a key exchange? In my existing research I've found no reason they can't, just that they don't.
I'm pretty sure the last time I flew spirit I saw a handler protecting the suitcases. Either that or another airline, but even then Southwest or United, nothing fancy.
It is indeed. And that sucks but that's what it is. Product design is about calculated risks and trades. It's a good thing regulators are here to help because companies won't do it on their own and the general public doesn't care enough.
I'll answer your question with a question: how often do you see people complaining about needing setup processes vs the old way of just plug and play? There's no perfect answer that placates all sides. Things can certainly be better, but when those people win and you no longer need to have a setup process, then what?
While true that in $current_year it would be nice if things were more secure, the sad truth is that most people don't care.
Surprisingly it's not everywhere. I'm very in embedded development and cannot count the amount of time I look for "unique" "id" etc in a reference manual and come up short. It's certainly more common than not, but you often have to design systems for the lowest common denominator.