Avoiding my "locus of attention" becoming the machine with ~/.junkdrawer
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 8/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Necesita aclaración
- Estado de actividad
- Activo
- Área
- developer-experience
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
"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.
- Lenguaje dominante
- Shell
- Estrellas
- 1
- Forks
- 0
- Merge medio
- 11 min
- PR fusionados (30 d)
- 2
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Sin guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de indexzero/dotfiles
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
-
Dificultad 4/5 3-5 días Aptitud para principiantes 39/100
-
Easy to remember one-linersAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 48/100
-
oneliners: evergreenAbierto
Dificultad 3/5 Medio día Aptitud para principiantes 15/100
Todos los issues de indexzero/dotfiles
Issues similares
-
bug raised-by:verifier
Dificultad 2/5 1-3 horas Aptitud para principiantes 79/100
medici-finance/assay#4008 ·
Los mantenedores suelen responder en 1 día
-
bug: `curl NAME` exports an unquoted, uninterpolated command that is not runnablePosiblemente ocupada @dannyward630 la tomó hoy. Abiertobug good first issue
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
yunaremaia/git-api#61 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
cloudflare/skills#247 ·
Los mantenedores suelen responder en 1 día
-
Update nwg-panel to 0.12.3Posiblemente ocupada @zen0bit la tomó hoy. Abiertopackage-update
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día