Analogy for explain...
 
Notifications
Clear all

Analogy for explaining how a file is deleted?

39 Posts
19 Users
0 Likes
4,577 Views
TomP
 TomP
(@tomp)
Posts: 36
Eminent Member
 

The simplest way I have put it is using a library index card analogy, whereby the file itself is the book, and the index card is how the file system finds the book.
When you delete a file, you don't remove the file itself, rather the index card for where that file was.

This can then be used to explain how files can be partially overwritten or fully recoverable.

 
Posted : 12/01/2010 4:18 pm
jaclaz
(@jaclaz)
Posts: 5133
Illustrious Member
 

I have used a hotel analogy, with guests checking in, leaving their briefcase behind when they check out, etc. So in the hotel directory, "Smith's Room" goes into the pool of "Available Rooms" when Smith checks out, but it isn't an "empty room" because it still contains Smith's briefcase (data).

Since this hotel has a lazy housecleaning staff, the briefcase remains there until the room is reassigned, at which time the new guest discovers it and throws it down the hotel's trash chute to make room for his own stuff.

….

Not perfect, of course, but as analogies go, it's useful and understandable.

Good one. )

Though you missed the part about all guests of the hotel being as mad as "my" typographers. wink

jaclaz

 
Posted : 12/01/2010 5:13 pm
BattleSpeed
(@battlespeed)
Posts: 36
Eminent Member
 

Good one. )

Though you missed the part about all guests of the hotel being as mad as "my" typographers. wink

jaclaz

Yes, I should have mentioned that this hotel caters to demented travelers, and as a result most of the "Available Rooms" at any given time will have abandoned luggage in them, left behind by the previous goofy guest. wink

 
Posted : 12/01/2010 5:41 pm
(@keeper)
Posts: 106
Estimable Member
 

There is a very generic and simple analogy in the TV show Numb3rs, I can't remember the episode (I think it was season 3). It involved coins being flipped (1 or 0) when recovering a file.

 
Posted : 12/01/2010 5:51 pm
Beetle
(@beetle)
Posts: 318
Reputable Member
 

The simplest way I have put it is using a library index card analogy, whereby the file itself is the book, and the index card is how the file system finds the book.
When you delete a file, you don't remove the file itself, rather the index card for where that file was.

This can then be used to explain how files can be partially overwritten or fully recoverable.

That's what I said previously…

 
Posted : 12/01/2010 5:55 pm
(@douglasbrush)
Posts: 812
Prominent Member
 

I used the book quite a bit. I do like the warehouse with the old guy at the front office. "That space has some old stuff in it bu it is marked for destruction if you need to use it."

Also, I explain that it is not deleted - just marked for deletion and hidden from view.

 
Posted : 12/01/2010 7:48 pm
jhup
 jhup
(@jhup)
Posts: 1442
Noble Member
 

The library card file and the book itself.

Cards are the FAT/MFT, book is the file.

Remove the card, cannot find the book - yet it is still there.

It sort of works for memory versus HDD (which I think most non-tech people confuse in general). Book on shelf on disk, book in hand in memory.

 
Posted : 12/01/2010 8:17 pm
Beetle
(@beetle)
Posts: 318
Reputable Member
 

The library card file and the book itself.

Cards are the FAT/MFT, book is the file.

Remove the card, cannot find the book - yet it is still there.

It sort of works for memory versus HDD (which I think most non-tech people confuse in general). Book on shelf on disk, book in hand in memory.

I like that last one. Book on shelf book in hand.

 
Posted : 12/01/2010 8:58 pm
(@douglasbrush)
Posts: 812
Prominent Member
 

…and human processor. Now I could only quad core my brain…..

 
Posted : 12/01/2010 9:16 pm
Beetle
(@beetle)
Posts: 318
Reputable Member
 

…and human processor. Now I could only quad core my brain…..

ROFL,

but you'd have a split personality disorder!

 
Posted : 12/01/2010 11:02 pm
Page 3 / 4
Share: