I'm more concerned that at some point, the defense will be "after all of the identity theft, news about hacking, and stories like this one, you just should have expected this". And that defense might just win, without a specific law. A clear, well written one. Which seems unlikely under Profit First TrumpTato.
If you have a terrible manager, you don't want that reference. That reference is not predictable. Do not list it, and explain in your next interview that your manager was an idiot, which is part of the reason you left. Not immediately, but find a subtle way to compliment the chance to work for new management with some sort of understanding of what you do, as opposed to the arsehole you used to work for.
You're leaving for a reason, and you don't want that reason to be something you enter into day 1. If necessary, give those details during the interview. If they balk, YOU DO NOT WANT THAT JORB.
"Easily" and "Millennium Prize Problem level difficulty" are apparently the same thing in your language...
What I think you meant to say, however, is that with a hardware debugger, we can record and the underlying processor instruction pointer and see where in the decision tree something went wrong. Not something I'd like to have to debug due to the likely crazy amount of data and decision points involved, but technically possible.
That's very different from being able to assert that we use computer vision to identify walls and guard rails and vehicles, and include logic to avoid them. No such rule was ever introduced, except by omission.
And, as such, there is no good way to predict what the AI will do given specific input. A "classical" program would be highly predictable based on its accuracy rate in identifying known objects, the number of unusual objects, and the image quality (visibility, contrast, or glare based on the environment). This thing on the other hand may not have a threshold for admitting it shouldn't be driving.
Without the training data set and software being used, it is possible that I have missed something vital. But what you missed is simple. Is it good enough that a car drives itself successfully? Or should we be able to make certain guarantees, or assertions, about its behavior?
Should the NTSB be able to review what caused a 10 car pile up, or church bus head on everyone died collison, and be confident of coming to a conclusion in a human lifetime? Because right now with this technology, we can't do root cause analysis. We can build experiments like Deep Dream to understand how decisions are made, but there's no guarantee of finding the answer.
No. Quit, and give no hint until the exit interview as to why. Frequently you will not have an exit interview. So call your boss's boss on the way out.
You don't have any other power. This psychobabble bullshit might work if you already knew it, but it won't help anyone who needs to read it and finds it insightful. Actually quit, and name names.
I work on a team. With a high functioning team, the ability to ask and clarify a question, while typing the code, is amazing.
And no, despite your best efforts to describe the effects of interruption, there was none. We were working to the same sprint.
I now work on a different team. Lord, don't interrupt a single one of them. It's almost like circumstances play a role. But if that were true, Slashdot would cease to exist.
Correlation and causation are science. Law is about tying actual loss to an action. Sometimes there are experts, but they are opinions based on reputation or experience, not scientists.
Your reply is irrelevant, and displays ignorance and idealism. Sure it would be great if things worked that way. Start a revolution and begin your own country, then you can tell us how it should work.
Sigh. Where do the prisoners go? Not USA, because of Congress. To another Gitmo? Hardly an answer. Go free? That gets way complicated.
Congress blocked the obvious path to closing Gitmo. Remember, Congress can override a veto with enough votes, so the President can't just thwart the lawmakers. He only enforces the laws within the legal framework, and your objections are addressed here.
I agree but your post is off topic. Indiana seems to be trying to avoid using this as a service, and using it more for pacification. Other states have implemented the service model, but I see no indication here.
I would support Indiana and encourage them away from fees, rather than attacking a problem that exists elsewhere.
Is OCR that good yet? I understand that PDF can store the image, along with the text metadata for searching. So the text can be improved while retaining visual fidelity for when OCR improves. Or when an intern deciphers the handwriting.
But as you say, I would want to do a lot of cleanup that relies on local availability, not cloud nonsense.
And mid trial when AWS dies due to a typo, I'm going to go apeshit and your design is defective. So they have piles of disclaimers which automatically make this a suboptimal solution.
I interviewed with this guy (diff language but same interview). Failed the trivia game, got the job anyway. Now people think he is an ineffectual dick, and I get stuff done.
Obviously my perspective has bias, but you can include the trivia bits to gauge formal learning from experience. A good formal education, complete with real world examples, can make a good interview, and an employee just good enough to be hard to fire. So you really should include some trivia.
Even if your sole purpose is to avoid the guy whose code reviews reject things on academic grounds, and allow system file exposure.
Remove the lines and the graph is still chaotic. I didn't see a methodology on there either.
I don't doubt it is horrible, but remember that confirmation bias exists. Sharing an image without methodology is irresponsible. Even if it ultimately is legit.
And the objection is basically that simulating our universe is hard, or at least enough paragraphs in a row that I stopped reading.
Discontinuity between quantum and classical effects makes more sense on a simulated plane than a real one. The ability of an AI to notice such things seems like a quirk of the AI framework, and believable. So the argument here actually supports the simulation more than hurts it. Making a simulation and this is how it turned out, in other words, is easier than getting everything working as intended.
The argument that things are slightly possible, and our universe so big, that those things are inevitably true, is gargage. But so is this argument.
It's almost like people believe things, then look for evidence or reasoning that supports them, instead of putting the conclusion at the end of the process.
It's not free speech because the ADA did not exclude creative content.
Now it's your fault.
You have standing to sue, alleging that free speech exceptions for creative works outweigh the ADA requirements, and that you were harmed, and get that enshrined in case law.
You haven't yet, so blame yourself. I personally cannot claim standing, so it ain't my fault this time.
Your experience with other ides means Visual Studio should be 64 bit? Nope, sorry, try again. Everything else is 64 bit? Not a good justification.
Your scenario of lots of stuff doesn't make sense for VS. You would have a current config and target for each project, but that info is mostly for the build chain. The IDE loads some metadata, but you're more likely to run out of memory due to larger pointers than anything else.
There are good ones out there, but you haven't really made an effort here.
No, they chose not to have a recurring cost year on year if $150k plus overhead, or roughly $300k. Plus a manager and likely a few coworkers, for maybe $1M per year.
Would have been worth it still, but you are ignorant of exactly what would be involved. Hiring one guy for all of yahoo would hardly be effective.
Add in third party teams providing support and access, and you have a huge cost center for no observable gain. Unless the CIO can sell the plan. And that's the CIO's job. Why don't we see that head rolling?
I have a brainless mouse age 10, that randomly right clicks because the driver is reinstalled every few seconds. Generic HID, no special features, worked fine just before the reboot.
No, because they are defragmenting the fragmented install base to eliminate as much bug hunting rework as possible.
QA suffered, with the hope that they would have to test and retest less due to a relatively monolithic base. Premature optimization. But the attempt continues, to address one platform instead of any combination of existing patches.
Huge difference between being aware of morally questionable behavior and being asked to participate. I would have kept my mouth shut and looked for a new job, but that can take time to find a good fit. But the moment I have to do something I fundamentally disagree with, I stand my ground and risk termination.
Being fired for standing up for the Constitution sends a stronger message than just quitting and turning the job over to someone who needs the job and would roll over. Multiple terms creates the elephant in the room.
Walking away is not the best solution if you're not directly involved, in every case. Take your nonsense somewhere with fewer logical thinkers.
Exposing kids who otherwise would not try coding is a good thing.
This effort won't make coders, and certainly not developers, unless the kids take it up as a hobby. Cheap coders is the goal, but you will get the kind you can automate out of a job.
Overall, I support exposure to any use of cold, hard logic that won't let you get close enough. It works or it doesn't, use your brain.
Also, selling self driving cars to people is the end game. Getting them on the road as taxis is a stepping point to get public trust. Volvo might be selling Uber on a plan that exists briefly between public mistrust of the tech, and cities using self driving cars the way bike sharing works now.
Uber is planning on selling its platform as the road tested solution to hailing digitally, regardless of who owns the cars. So at worst it advertises the product, for which uber provides the service. If they own a fleet in some markets, that is a bonus.
And, owning cars early means a better chance of vendor lock in and standardization on Uber. Increase the ride sharing, increase profits.
Slashdot Mirror
I'm more concerned that at some point, the defense will be "after all of the identity theft, news about hacking, and stories like this one, you just should have expected this". And that defense might just win, without a specific law. A clear, well written one. Which seems unlikely under Profit First TrumpTato.
If you have a terrible manager, you don't want that reference. That reference is not predictable. Do not list it, and explain in your next interview that your manager was an idiot, which is part of the reason you left. Not immediately, but find a subtle way to compliment the chance to work for new management with some sort of understanding of what you do, as opposed to the arsehole you used to work for.
You're leaving for a reason, and you don't want that reason to be something you enter into day 1. If necessary, give those details during the interview. If they balk, YOU DO NOT WANT THAT JORB.
"Easily" and "Millennium Prize Problem level difficulty" are apparently the same thing in your language...
What I think you meant to say, however, is that with a hardware debugger, we can record and the underlying processor instruction pointer and see where in the decision tree something went wrong. Not something I'd like to have to debug due to the likely crazy amount of data and decision points involved, but technically possible.
That's very different from being able to assert that we use computer vision to identify walls and guard rails and vehicles, and include logic to avoid them. No such rule was ever introduced, except by omission.
And, as such, there is no good way to predict what the AI will do given specific input. A "classical" program would be highly predictable based on its accuracy rate in identifying known objects, the number of unusual objects, and the image quality (visibility, contrast, or glare based on the environment). This thing on the other hand may not have a threshold for admitting it shouldn't be driving.
Without the training data set and software being used, it is possible that I have missed something vital. But what you missed is simple. Is it good enough that a car drives itself successfully? Or should we be able to make certain guarantees, or assertions, about its behavior?
Should the NTSB be able to review what caused a 10 car pile up, or church bus head on everyone died collison, and be confident of coming to a conclusion in a human lifetime? Because right now with this technology, we can't do root cause analysis. We can build experiments like Deep Dream to understand how decisions are made, but there's no guarantee of finding the answer.
No. Quit, and give no hint until the exit interview as to why. Frequently you will not have an exit interview. So call your boss's boss on the way out.
You don't have any other power. This psychobabble bullshit might work if you already knew it, but it won't help anyone who needs to read it and finds it insightful. Actually quit, and name names.
Ergo, excessive regulation that must be repealed immediately, preferably by a large handed adult. But a tiny fingered child will do.
I work on a team. With a high functioning team, the ability to ask and clarify a question, while typing the code, is amazing.
And no, despite your best efforts to describe the effects of interruption, there was none. We were working to the same sprint.
I now work on a different team. Lord, don't interrupt a single one of them. It's almost like circumstances play a role. But if that were true, Slashdot would cease to exist.
Correlation and causation are science. Law is about tying actual loss to an action. Sometimes there are experts, but they are opinions based on reputation or experience, not scientists.
Your reply is irrelevant, and displays ignorance and idealism. Sure it would be great if things worked that way. Start a revolution and begin your own country, then you can tell us how it should work.
Accessible Arsehole
Sigh. Where do the prisoners go? Not USA, because of Congress. To another Gitmo? Hardly an answer. Go free? That gets way complicated.
Congress blocked the obvious path to closing Gitmo. Remember, Congress can override a veto with enough votes, so the President can't just thwart the lawmakers. He only enforces the laws within the legal framework, and your objections are addressed here.
http://time.com/4178779/obama-...
I agree but your post is off topic. Indiana seems to be trying to avoid using this as a service, and using it more for pacification. Other states have implemented the service model, but I see no indication here.
I would support Indiana and encourage them away from fees, rather than attacking a problem that exists elsewhere.
That's not Indiana, and the vendor mentioned is only one of many being considered. So that info is ancillary at best.
Is OCR that good yet? I understand that PDF can store the image, along with the text metadata for searching. So the text can be improved while retaining visual fidelity for when OCR improves. Or when an intern deciphers the handwriting.
But as you say, I would want to do a lot of cleanup that relies on local availability, not cloud nonsense.
And mid trial when AWS dies due to a typo, I'm going to go apeshit and your design is defective. So they have piles of disclaimers which automatically make this a suboptimal solution.
I interviewed with this guy (diff language but same interview). Failed the trivia game, got the job anyway. Now people think he is an ineffectual dick, and I get stuff done.
Obviously my perspective has bias, but you can include the trivia bits to gauge formal learning from experience. A good formal education, complete with real world examples, can make a good interview, and an employee just good enough to be hard to fire. So you really should include some trivia.
Even if your sole purpose is to avoid the guy whose code reviews reject things on academic grounds, and allow system file exposure.
Remove the lines and the graph is still chaotic. I didn't see a methodology on there either.
I don't doubt it is horrible, but remember that confirmation bias exists. Sharing an image without methodology is irresponsible. Even if it ultimately is legit.
And the objection is basically that simulating our universe is hard, or at least enough paragraphs in a row that I stopped reading.
Discontinuity between quantum and classical effects makes more sense on a simulated plane than a real one. The ability of an AI to notice such things seems like a quirk of the AI framework, and believable. So the argument here actually supports the simulation more than hurts it. Making a simulation and this is how it turned out, in other words, is easier than getting everything working as intended.
The argument that things are slightly possible, and our universe so big, that those things are inevitably true, is gargage. But so is this argument.
It's almost like people believe things, then look for evidence or reasoning that supports them, instead of putting the conclusion at the end of the process.
It's not free speech because the ADA did not exclude creative content.
Now it's your fault.
You have standing to sue, alleging that free speech exceptions for creative works outweigh the ADA requirements, and that you were harmed, and get that enshrined in case law.
You haven't yet, so blame yourself. I personally cannot claim standing, so it ain't my fault this time.
That should answer all of your questions.
Most coders will read more than they write, especially if they forget their own code.
I learned a lot from MESS/MAME code, and I do almost 0 C today. But I remember how to write. Write, read someone else, and give feedback.
Clever one liners are neat, but almost always compile the same as using intermediate variables. One is easier to read and debug.
Your experience with other ides means Visual Studio should be 64 bit? Nope, sorry, try again. Everything else is 64 bit? Not a good justification.
Your scenario of lots of stuff doesn't make sense for VS. You would have a current config and target for each project, but that info is mostly for the build chain. The IDE loads some metadata, but you're more likely to run out of memory due to larger pointers than anything else.
There are good ones out there, but you haven't really made an effort here.
You are the definition of "A little knowledge is a dangerous thing."
Smart enough to be cynical, but not smart enough to offer any evidence. If you worked in silicon, I'd like to hear your story.
Otherwise, shut your piehole and let the adults talk. Want to blame it on the illuminati or aliens? Stuff it up your arse.
No, they chose not to have a recurring cost year on year if $150k plus overhead, or roughly $300k. Plus a manager and likely a few coworkers, for maybe $1M per year.
Would have been worth it still, but you are ignorant of exactly what would be involved. Hiring one guy for all of yahoo would hardly be effective.
Add in third party teams providing support and access, and you have a huge cost center for no observable gain. Unless the CIO can sell the plan. And that's the CIO's job. Why don't we see that head rolling?
I have a brainless mouse age 10, that randomly right clicks because the driver is reinstalled every few seconds. Generic HID, no special features, worked fine just before the reboot.
No excuse.
No, because they are defragmenting the fragmented install base to eliminate as much bug hunting rework as possible.
QA suffered, with the hope that they would have to test and retest less due to a relatively monolithic base. Premature optimization. But the attempt continues, to address one platform instead of any combination of existing patches.
Wise move, poorly executed, poorly communicated.
Huge difference between being aware of morally questionable behavior and being asked to participate. I would have kept my mouth shut and looked for a new job, but that can take time to find a good fit. But the moment I have to do something I fundamentally disagree with, I stand my ground and risk termination.
Being fired for standing up for the Constitution sends a stronger message than just quitting and turning the job over to someone who needs the job and would roll over. Multiple terms creates the elephant in the room.
Walking away is not the best solution if you're not directly involved, in every case. Take your nonsense somewhere with fewer logical thinkers.
Exposing kids who otherwise would not try coding is a good thing.
This effort won't make coders, and certainly not developers, unless the kids take it up as a hobby. Cheap coders is the goal, but you will get the kind you can automate out of a job.
Overall, I support exposure to any use of cold, hard logic that won't let you get close enough. It works or it doesn't, use your brain.
Also, selling self driving cars to people is the end game. Getting them on the road as taxis is a stepping point to get public trust. Volvo might be selling Uber on a plan that exists briefly between public mistrust of the tech, and cities using self driving cars the way bike sharing works now.
Uber is planning on selling its platform as the road tested solution to hailing digitally, regardless of who owns the cars. So at worst it advertises the product, for which uber provides the service. If they own a fleet in some markets, that is a bonus.
And, owning cars early means a better chance of vendor lock in and standardization on Uber. Increase the ride sharing, increase profits.