4 ms·
Don't "run" programs, don't let them "spawn" threads, don't allow CPU to "follow" instructions, don't "read" or "write" files, should I keep going? All these wo
by nercury 3y ago
Don't "run" programs, don't let them "spawn" threads, don't allow CPU to "follow" instructions, don't "read" or "write" files, should I keep going? All these words used to mean humans doing things, we have been anthropomorphising the machines since the beginning. You are fighting a loosing battle here, better to just calm down and relax.
- dleeftink 3y agoA warm-up exercise before going into any programming task is coming up with names for the methods and interfaces I intend to implement. A more difficult exercise is coming up with apt names without anthropomorphising--something I rarely succeed at. I'm often drawn to analogs in the musical realm (Scales, Sequences, Signals, Tuning), carpentry (Blueprints, Components, Scaffolding), libraries (Resources, Pages, Indices), the natural world (Roots, Trees, Seeds, Leaves), physical media (Slots, Packages), publishing (Versions, Releases) and even cooking (Mixers, Recipes). We often understand technology by way of analogy or prior experiences. Whenever dealing with the abstract or unknown, metaphors are often the first tool to make sense of them [0]. [0]: https://en.m.wikipedia.org/wiki/Metaphors_We_Live_By https://en.m.wikipedia.org/wiki/Metaphors_We_Live_By
- ben_w 3y ago"Computer" being a former job title would've been on my list :)