3 ms·
We are in precisely the middle of this. We have documents in our product that encapsulate an essential step in a workflow, but for some unholy reason, someone d
by dclowd9901 11y ago
We are in precisely the middle of this. We have documents in our product that encapsulate an essential step in a workflow, but for some unholy reason, someone decided to call them "items."
Now day in and day out, I have to deal with classes like ItemViewer, ItemListController, etc etc, and half the time I have no idea what the responsibility, location or relationship of any given class is supposed to be. So much time just getting contextual background before I start working in an area of code. Couple this with early bad coding decisions around encapsulating responsibility and lack of testing coverage and I've got a relatively miserable 2-3 years ahead of me.
- tomsthumb 11y ago> someone decided to call them "items." I prefer to call my stuff "things."
- HillaryBriss 11y agoI like "entities" -- I feel so smart when I use that.
- shurcooL 11y agoThe only other name left is "entries", right?
- saurik 11y agoAn "entry" at least implies there is a list somewhere (as would "element"). Both "item" and "entity" are more like "thing". I could see adding "object" to the list.
- tomsthumb 11y ago"entry" is a fantasticly sinister name if you're writing the sql directly in your application though. object would be hilarious in java assuming the compiler lets you do that.
- dbenhur 11y agoHeh. Except for: element, action, slot, task, goal, task command, subject, target, source, destination, object, actor, path, key, memo, manifest, sender, receiver, self, this, thing, data, value, register, ... I think you enumerated them all.