I see the term "dirty" or "dirty objects" a lot in programming.
What does this mean?
A dirty object is an object that has changed in its content, but this content has not been synchronized back into the database/disk. It's a typical situation of desynchronization between a cache and a storage.
CONTEXT: original question was phrased as I find a lot in "programming dirty"
, this answer attempts to address that. The accepted answer is about dirty objects
, the new question after it was changed, and a significantly different subject.
"Programming dirty" as you quote it, can mean that you use a "quick and dirty" method for solving a problem (archived), usually to stay within time constraints, and hoping to fix it later.
Programming dirty is often used with prototyping (i.e., a mini-program that shows the principles of a concept, later to be replaced by the actual product), where it is needed to show something quickly, but your code is not meant to last and you expect it to be thrown out (note: in the real world, companies don't always kill prototypes, leading to maintenance nightmares of the dirtily programmed code).
© 2022 - 2024 — McMap. All rights reserved.