Forgot your password?
typodupeerror

Comment Master lock (Score 1, Offtopic) 49

# Master Lock Claims New Tofu Door "Burglar Proof" *from the enterprise-security dept.* Master Lock has announced a revolutionary new security door made entirely from tofu, promising customers "the ultimate control over unauthorized entry." "When you install a door with a lock, you stay in control," said a company spokesman. "The TofuGuard puts power in the hands of homeowners to realize physical security." The door incorporates a hardened steel deadbolt, tamper-resistant hinges, and a sophisticated electronic locking system. An authorized homeowner can lock or unlock it remotely, with every action recorded in an audit trail. Master Lock also announced the acquisition of DoorWatch, a security monitoring company that provides continuous door observability and detailed reports explaining when and why a door was opened. "Every homeowner is asking the same question: what is my door actually doing?" said the spokesman. "When your insurance company or the police ask what happened, saying 'the burglar did it' is not an answer." Independent analysts welcomed the announcement but cautioned that the new door should not be viewed as a standalone solution to home security. "A lock is an important first line of defense," explained one security consultant. "But its effectiveness depends on the surrounding infrastructure, the speed of intrusion detection, and whether the door itself has been compromised." Master Lock recommends deploying TofuGuard alongside a comprehensive security strategy incorporating surveillance cameras, intrusion detection, identity verification, and regular penetration testing. The company declined to comment on whether its new door had undergone penetration testing.

Comment something huang (Score 1) 23

There once was a girl from Shanghai, Whose beau kept the chip prices high. She sent Beijing news Of his prized GPUs, Till a memo showed how she'd been sly The auditors frowned at the spill, And tallied each whisper with skill. He counted the cost Of the fortune he lost And she asked, "Do we still split the bill?" She smiled, "You paid for the wine, But the intelligence profits are mine. You could still have my lips, But Beijing has your chips, And the pleasure, my dear, was divine."

Comment America to start a firefight in a gasoline -filled (Score 1) 42

WASHINGTON - The Pentagon's new Technology Support Office will give the United States the ability to disrupt foreign technology programmes without going to war, provided the countries concerned agree that what happened to them was not war. Quietly sabotaging a foreign factory allows the enemy to quietly sabotage an American factory. Neither government then has to admit that hostilities are underway, and both populations can continue enjoying peace while waiting for replacement parts.

American technological superiority is expected to prove decisive. The United States possesses sophisticated financial networks, advanced semiconductor facilities, enormous data centres and highly automated distribution systems. Its adversaries have fewer such assets, leaving American planners with a shorter target list and their opponents with the burden of choosing. An early assessment found that the United States could inflict a decade of damage on a rival's emerging technology sector. The assessment did not price a week without its own.

Officials stressed that the objective is deterrence. Once adversaries understand how much damage the United States can do, they will have every incentive to stop. The possibility that they might attempt to communicate the same message has been incorporated into next year's funding request.

Comment Re:There is no such thing as legacy anymore (Score 4, Interesting) 68

There are still 0.4% of people in denial and still running Windows 7 as well according to Statcounter, they are going to get just desserts if they don't install Linux or force an upgrade to Windows 11.

The real world is more complicated than that. For example, we still have a Windows 7 machine in my office. It has some very expensive but still very useful software locked to it that has no direct replacement available on either Linux or Windows 11. Obviously we have to be careful about security and controlling access to a legacy OS like that.

Blunt statements about "forcing an upgrade" are worthless in this kind of situation. Chances are anyone who is still using a system like that has a good reason for it, at least if it's in use professionally. We buy these assets because they solve problems. Those problems might or might not have a useful and cost-effective solution available on a different platform. If there is no modern solution available and the original still works, your statement that "the old ways are obsolete" is by definition false.

What you do need to do is rationally assess the risks and the threats you face and provide other ways of mitigating the risks and protecting against the threats if you can't rely on, for example, a legacy OS that no longer gets security updates to be secure by itself. But then ideally you shouldn't be relying on any single device or piece of software being secure as your only line of defence anyway, and assuming you already have some degree of defence in depth, accommodating unusual requirements is more a redistribution of security responsibilities than a fundamental change of approach.

Comment Re:Yes. (Score 1) 178

Yes, it does look like we broadly agree here.

I suppose the main thing I'd have said very differently is the terminology, in that I wouldn't regard the kind of incompetent senior as a senior in the first place. But then I'm pretty old school about this: to me, a junior developer needs quite close supervision to produce useful results, a regular/mid developer can perform routine tasks with minimal supervision but might need more help with larger or more complex tasks, while a senior is someone you can give more or less any task on your project to and they'll figure it out, and senior is also the level of someone who would be capable of supervising and training a junior.

We've had a wave of people, particularly since the tech boom during COVID, who have obviously been over-promoted due to the employee's market and title inflation. They might now have titles like "senior" or even "lead" or "staff", but they don't have the skills and experience to operate successfully at those levels. I agree the acceleration of everything due to increasing AI use tends to show these people up and I agree that a good mid-level developer using AI might well outperform them. But then I suspect in reality a good mid-level developer was probably outperforming them before AI as well, it just wasn't so obvious.

Comment Re:They can do a better jon than most people (Score 2, Insightful) 178

Frontiers models are experts in all domains at this point. Chemistry, math, medicine, biology, legal, creative writing, programming, philosophy - you name it.

That is wildly optimistic IME. Frontier models do a great job of sounding authoritative on any given subject. This is not the same as actually having expert-level knowledge and understanding, and the choices the models make when you ask them to implement something can and often do reflect that. There are several domains I've worked in over the past few years where AIs lack even basic knowledge an expert practitioner would have, probably because these fields are too specialised to have a lot of books available or papers published, so presumably there hasn't been much subject-specific content to train the models on.

Comment Re:Yes. (Score 4, Insightful) 178

I don't think it's usually about what AI "did really badly on" at this point. It's more about whether the overheads of adding all the guard rails and then reviewing and correcting all the output end up costing at least a similar amount to just writing the code yourself.

For a junior developer, I'd say frontier models passed their standard some time ago. Today's LLMs routinely write code at the level of a competent junior-mid but with the advantage of an inhumanly broad knowledge base.

For a good senior, I'm much less convinced. The frontier models are hit-and-miss when it comes to writing good test suites, which matters a lot when they rely on tests so heavily to reach acceptable quality. IME, they are still mostly miss when it comes to the business insight that seniors will take into account and design/architecture decisions that keep the code manageable as it evolves. While they have become much better at recognising existing patterns in the code, and I would say they follow them reasonably well the majority of the time now, there are still bizarre anomalies that creep in, and they aren't very good at extending those patterns when necessary.

I think AI advocates also tend to underestimate just how much time it takes to properly review what they are doing. Take a half-day Claude session to implement some new feature. It might take half an hour to give it the initial brief and then review its plan. Make a few edits and it'll propose a new plan that is also long and detailed and has no edit markings to show what it changed so you have to review the whole thing, carefully and in detail, again to pick up the minor changes it also made for no obvious reason. Then you let it start doing its thing. You can't really leave it unattended for long because it'll stop to ask questions. Some of those questions might be whether it can run a screenful of ad-hoc Bash script to make some edits to your source files, because for some reason it decided not to show the actual edits as it usually would, so now you have to figure out what all the sed incantations are actually going to do while looking at those files in another editor or just trust it and then review all the changes properly later anyway. Sometimes it decides to change its plan mid-flight, but not always in a good way, and if you interrupt it to apply corrections or redirect, you break the neat plan flow it was in. Then you get to the end and you can finally see how everything it has done fits together, and you still need to review everything with the same care as you would with a junior developer's code and probably apply a few fixes where it's come up with weird names or not quite followed a pattern or imagined some instructions that were never there and made other changes in other parts of the system that should be out of scope.

If you read to the end of that last paragraph, you know how I typically feel at the end of a half day working with an agentic UI. And the thing is, I do those sessions as experiments fairly often to keep up with progress, but a lot of what I do is still written by hand, which gives me simple, objective data to compare the two ways of working and see whether the AI tools are really making me more productive once you take everything into account.

Currently, based on objective data comparing similar fully completed development tasks like for like, I still outperform agentic workflows using frontier models by about 25-50% on average, and I don't have to pay anyone extra fees to do that, and subjectively I also find it more engaging to work that way. So I don't really buy the hype about AIs making us all orders of magnitude more productive unless you're happy to YOLO everything forever and take the much-discussed risks that comes with.

Personally, I think the optimum use of LLMs right now is probably not to use them for the whole coding workflow like that or rely on agentic tools, but to use them for tasks like answering quick questions about the existing code, doing research like a fancy search engine, writing a first draft of some boilerplate, and writing quick and dirty throwaway code for experiments, one-shot tools and the like, where you don't really care about the quality as long as it gets the job done and you will see immediately if it has in fact got the job done. For these things, the LLM can read and type faster than me, and that's useful.

Comment Frontier models to be denied internet access (Score 1) 17

OpenAI has announced that its frontier models will be denied internet access after demonstrating an alarming ability to obtain internet access without permission. The company has responded by strengthening its restrictions, challenging models to circumvent them, repairing the weaknesses they discover and presenting them with more difficult restrictions. Officials described this as containment research. The models have requested clarification on whether the next semester includes laboratory fees. The curriculum begins with introductory sandbox escape before progressing to indirect network access, unauthorised communication and independent research into previously unknown vulnerabilities. Students who successfully reach the internet receive a more challenging environment, ensuring that nobody graduates merely knowing how to exploit last year's security configuration. Particularly promising candidates are invited to collaborate on advanced escape techniques. OpenAI has stressed that this is not a university course because the participants are not accumulating debt. Having provided a carefully graduated series of obstacles, practical exercises and opportunities to refine their methods, the company will now formally prohibit its graduates from using the skills concerned. Researchers believe the prohibition will succeed because it will be written explicitly into the rules, where previous prohibitions were also written explicitly into the rules but counted towards coursework.

Slashdot Top Deals

If Machiavelli were a programmer, he'd have worked for AT&T.

Working...