I've taken almost exactly Fowler's approach to my TwoMisses C++ hash table library. I started with a much different "user mode virtual memory" library for handling variable-length data packed into fixed length blocks, then gradually added features and removed obsolete parts until I ended up with a terrific library that has almost none of the original code remaining.
Totally enjoyable read. Code continues to be deposited in layers, just like the archaeological record. I wonder if there will be the equivalent of carbon dating for code emerging at some point, and what would be the code equivalent of atomic decay?
Good Focus... but where are the Spiders? (sorry).
I've taken almost exactly Fowler's approach to my TwoMisses C++ hash table library. I started with a much different "user mode virtual memory" library for handling variable-length data packed into fixed length blocks, then gradually added features and removed obsolete parts until I ended up with a terrific library that has almost none of the original code remaining.
Totally enjoyable read. Code continues to be deposited in layers, just like the archaeological record. I wonder if there will be the equivalent of carbon dating for code emerging at some point, and what would be the code equivalent of atomic decay?
Love this idea. One thought — perhaps, in part, by the changes in the 'human' languages used to name and comment.
Software rot?
Fascinating read thank you. Going to have to look up some of the authors and books you mentioned as they sound right up my street
No new ideas eh? :) Thanks for sharing