No, that's not what it assumes at all. For example, another objective would be avoiding the situation described in the article the rest of us are commenting on.
2,345 karma · joined August 29, 2019
No, it doesn't, that's absurd. Does wearing a seatbelt assume that you're going to crash every single time you drive?
The problem is that, in your own words, they took days to fail to solve the problem. If they Googled the solution, and so it took them 30 or even 60 minutes to solve it, we wouldn't be having this conversation. If they asked their colleagues for help right away, we wouldn't be having this conversation.
Unless this particular role is going to be predominantly circuit design -- in which case I do have to wonder how this person got hired in the first place -- this is simply a stupid criterion to select on.
I would rather pay the engineer who knows how to solve problems even when they don't already know the answer, first and foremost. Beyond that, I would much rather pay the engineer who has practical, hands-on knowledge, that they don't teach in school. How to use git effectively, as already mentioned. How to debug production issues. What actions are and aren't safe to perform on a production server. What facilities the OS offers to get information about one's own process and the system itself. How different valid-on-paper approaches might actually play out in real life. When it's worth pursuing an exciting new technology, and when it probably won't be. Oh and of course, what new and updated technologies exist since your guy graduated Electronics 101 a decade or two ago in the first place.
I don't know how to do that either, but "winging it" is not something that would occur to me. First I'd Google it and try to figure it out. If it turns out to be nontrivial, I would just ask for help.
And I wouldn't feel the least bit bad about it. After all, those same highly educated folks need my help with e.g. git a lot more often than most software needs serious math :)
Those requirements were never real, anyway. I don't have any degree. The last time I was seriously questioned about it during an interview was 2004.
Dating the police is just such an astoundingly egregious violation of this principle that I can only wonder what, if anything, those people are thinking.
Anyway, the key takeaway seems to don't date anyone who dates the police. Firstly, because it directly puts your own safety at risk, as this article exemplifies. Secondly, because it demonstrates terrible judgment; it seems reasonable to assume they are likely to make other terrible decisions in the future.
There is indeed plenty murky here, and it is mostly coming from you in an attempt to incorrectly use an emotionally-loaded word in order to deceive people into supporting your position.
Or -- and I know this is crazy but hear me out here -- if you don't like it, and it brings nothing but problems to the table, just don't use it at all.
For example, if you log out of a secondary profile and log back in, all your widgets will be gone. I don't have the bug link handy but IIRC, it's been open since 2021.
Given the apparent simplicity of the app I don't see any other conclusion than this is a pure and shameless gimmick to collect this information from people.
As far as I can tell this can be replaced by a plain text file of suggestions and a random number generator. Of course I'm not sure about this since I am never going to never going to submit to the requirements to find out.
If you need to sue me for dumping chemicals, you can pretty well be bothered to go down to the clerk and show your own ID. It's not a problem. There is no need for my home address to be searchable by the whole Internet
In my city, you can go to a website, type the first three characters of a name, and instantly get the full names and addresses of anyone who matches and owns a home.
To my mind, this is beyond absurd. This is a major safety risk with no benefits whatsoever. It's also the #1 reason I continue to rent.
Took them like 6 months to fix that.