Forgot your password?
typodupeerror

Comment How do they go about solving a problem... (Score 1) 29

The thing to look for is how they go about solving a problem. That's the key. Coding is easy. Figuring out what the problem is and how to go about solving it, that's the hard part. Especially given that the problem the user says they need solved is often not the problem they actually have.

Comment Re:It's complexity related (Score 1) 172

> You cannot sit down and ask an AI to write you anything long and complex and expect it to do so successfully without ... ... a lot of debugging. With practice, it can do long and complex and succcessful, and do so in less time than it would take to write it yourself.

It will still take a *lot* of debugging. It will be at least an order of magnitude longer than the time it took to write it, and the last 10% of production ready will take 90% of your time. But, it can still be significantly faster than writing it yourself.

Comment In-class tests (Score 3, Insightful) 150

Grade homework on completion and be done with it. Then schedule in-class quizzes and exams, where students are expected to show their work as well as the results and do it hand-written. That makes it hard to access chatbots, and even if students do the drudgery of transcribing the chatbot's output will discourage them (if they were willing to do that much work, they wouldn't be trying to skip the work using a chatbot). They may skate by on the homework, but the exam scores will show whether they actually learned the material or not.

Comment only one? (Score 4, Insightful) 30

imagine how flock personnel uses flock network every day...AI allows drawing conclusions from mass movement information that can provide information far beyond just someone's location. It is probably possible even to figure out market moves based on movement of groups of people.

This is not just about following any one person, this is about information movement, following a group of people who work on the same project for example to undersrand when they are going towards the same site / goal. This is beyond dangerous.

Comment Fuck him (Score 1) 58

Fuck him and the horse he rode on. Fuck his business. Fuck his technology. Fuck his company. Fuck his employees. Fuck his investors. Fuck his government ties. Fuck him defending this shit. Fuck everyone who wants this. Fuck the government for buying into it. Fuck the laws that allow this if they do.

Comment Re:So what exactly was wrong with GIT? (Score 1) 107

Volume over time. Git is designed to allow offline work, so each working copy has it's own repository you commit to. With a monorepo that's a lot of history that isn't being used by any one agent working in only part of the code. So they uninvented Git, removing the "enable off-line work without a connection to a master repository" requirement. Which put them back at the requirements that spawned Subversion. And proceeded to re-implement Subversion. Badly.

Comment This barely counts as a malicious attack. (Score 1) 105

I mean, come on. The freezers are on the Internet, no firewalls, fully accessible to anyone with a browser. Their "security" consists of rotating the admin password daily... to the current date. There are guppies out there that could gain access to these. The root cause here is willful negligence by the retailer's IT department.

Comment How to deal with Flock (Score 1) 115

The way you deal with Flock and their cameras is that you tell them you are terminating your contract with them and will be remitting payment for the remainder of the contract term. They have 30 days to remove the cameras from your property or arrange for removal. If the cameras aren't removed, you will remove them and store them at Flock's expense until Flock comes to pick them up or makes arrangements for pick-up.

Then you send them their money and, if the cameras are still there after 30 days, take 'em down and put them in storage. The cameras may belong to Flock, but it's still your property they're mounted on and Flock no longer has any right to have their stuff on your property. Don't argue with them, don't get into a debate with them, just do as you said you'd do. Sure they could take you to court, but seeing as they've received all the money they'd've been entitled to and their property is sitting there nice and undamaged waiting for them to come get it the court's going to ask why their case shouldn't be dismissed for failure to state a claim.

Comment Re:That old idea again (Score 1) 94

Those "very special" use cases are actually fairly common. I routinely deal with data structures in software I write that are read-mostly: large data tables that are accessed in the inner loop (so need fast access) but whose data is updated infrequently (anywhere from minutes to days between changes, and often the changes are in batches so many changes can be applied in one operation). Being able to put them in compressed memory would free up a lot of normal memory for things that do actively change, which would speed up the application noticeably.

I don't think CRAM is a solution to the current memory price crunch, but it's certainly an interesting idea. The Redis cache software, for example, would probably benefit highly from higher capacity. And of course the same techniques can be adapted to flash/SSD drives where the memory itself isn't necessarily the speed bottleneck.

Comment Simple answer: "No." (Score 4, Interesting) 59

The answer is a simple "No.". Don't allow them. The vast majority will fail to meet reasonable criteria for acceptance, which is enough of a reason to reject them. For the rest, even if they're acceptable in terms of quality, the sheer cost of reviewing every pull request in detail and sorting the minority of acceptable requests from the swamp of slop will itself damage the project, diverting maintainer time away from feature work and fixing bugs, badly enough that it's not worth it. I think this sums it up nicely:

Why should I spend my time reading something you didn't care enough about to spend time writing?

Slashdot Top Deals

There is very little future in being right when your boss is wrong.

Working...