1980s DOS deletion mishap offers a timeless reminder about command-line permissions

A 1980s anecdote from The Register’s “Who, Me?” column recounts how a construction site manager accidentally deleted all files on a colleague’s PC using the DOS command ‘DEL *.*’. While the story is decades old, its core lesson – that careless command-line use can have immediate and destructive consequences – remains relevant for anyone working with modern development tools, including AI command-line interfaces and automation scripts.

The incident, shared by a reader called Clay, happened on a Swedish construction site where two site engineers were the only staff with computers. Clay, the most junior member of the management team, was curious about the machines. During a lunch break, he asked the junior engineer if he could try the PC. The junior engineer complied, and Clay entered the only command he knew: ‘DEL *.*’. The command deleted everything in the directory he had been allowed to access.

Por que importa

Key facts

The moral of the story, as The Register puts it, is “never believe a suit who says they’re handy with tech.” For developers and engineers today, the anecdote underscores a broader principle: access control and permission management are critical, whether the environment is a 1980s DOS machine or a modern cloud-based AI toolchain.

Why this matters for developers and AI tool users
Command-line interfaces are still a core part of many developer workflows, including those involving AI models, automation scripts, and container management. A careless `rm -rf` or a misconfigured pipeline can delete important data, models, or configuration files. The same risk exists in AI tooling where users may run shell commands via agents or automation platforms.

Contexto

The 1980s story is a cautionary tale about the importance of:
– Restricting write and delete permissions to trusted users and scripts.
– Using version control and backups to recover from accidental deletions.
– Testing commands in sandboxed environments before running them on production systems.
– Auditing command history and logs to detect mistakes quickly.

The incident also highlights the social dynamics of access: a more senior person requesting access to a machine they are not familiar with. In modern AI development, similar situations can occur when non-technical stakeholders request direct access to production systems or AI model registries.

Limitations and context
This story is a single anecdote from the 1980s, not a systematic study of command-line errors. The technical environment (DOS) is far removed from today’s Linux, macOS, or cloud shells. However, the psychological pattern – overconfidence in a little-known command – is timeless. The story does not provide details about the specific files deleted or whether backups existed.

The relevance to AI and developer tooling is indirect but instructive. As AI agents and automation tools gain the ability to execute shell commands, the risk of accidental destructive actions increases. Developers should apply the same permissions discipline to AI tooling as they would to any other command-line interface.

Source: The Register, “Manager showed off his DOS prowess – with a command that wiped data” (https://www.theregister.com/software/2026/07/27/manager-showed-off-his-dos-prowess-with-a-command-that-wiped-data/5278057)