Avoiding my "locus of attention" becoming the machine with ~/.junkdrawer
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 8/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Domain
- developer-experience
Research direction
The issue is a conceptual essay about a "system junk drawer" for quick, messy fixes in a personal dotfiles repo, and it names no file, function, or test. Nothing in it says what to change, so there is no entry point to start from. Done would need a maintainer decision on whether the junk drawer (~/.junkdrawer) should exist and what form it takes, which is design work to settle in the thread before any code.
Written by the indexing model from the issue text.
Description
"Me, I have a science fiction writer's conviction that the damn robot is supposed to speak
human, not the other way around."
– Spider Robinson
As any system becomes more complete & structured, it is often psychologically demotivating to deviate from it. This kind of habituation is a double edged sword for software systems specifically as that care & attention can quickly steal your "locus of attention" from whatever task you were on to adding a tiny bit of functionality to the system.
You then have two choices:
- Dispatch a gremlin to add said function, which itself will increase your short-term cognitive entropy.
- Deviate from the system, and leave yourself a "wort" or a "gotcha" to clean up in the future
When one recognizes this property of systemics however, the dichotomy above reveals itself as the obvious false dichotomy it is. There is a third choice:
- Dispatch a gremlin to add said function, which itself will increase your short-term cognitive entropy.
- Deviate from the system, and leave yourself a "wort" or a "gotcha" to clean up in the future
- Bless a "system junk drawer" for such quick & dirty solutions, and how a gremlin can clean that junk drawer out for you
Indeed if we follow this rationale we are Jetson leaving the mess he told Rosie he makes frequently to appease the growing demands of Mr. Spacely and the ever ominous button to be pushed.
- Dominant language
- Shell
- Stars
- 1
- Forks
- 0
- Avg merge
- 14h 36m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from indexzero/dotfiles
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 4/5 3-5 days Newbie friendliness 56/100
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 4/5 3-5 days Newbie friendliness 39/100
-
Difficulty 1/5 Under an hour Newbie friendliness 48/100
All issues in indexzero/dotfiles
Similar issues
-
bug CLI documentation
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
openai/codex#56630 · 3 comments · 3 reactions ·
Maintainers usually reply within 1 day
-
0. to triage
Difficulty 1/5 Under an hour Newbie friendliness 67/100
roundcube/roundcubemail-docker#478 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
level/task type/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
wazuh/wazuh-installation-assistant#1177 ·
Maintainers usually reply within 1 day