TheV2

Joel gathers his friends at a remote cabin to celebrate the completion of his latest feature film in his 12 features project.

This movie is part of Joel Haver's challenge to create 12 feature films in 12 months. I just watched it now and I think it's the most relatable, yet insane and perhaps one of my favorite movies of all time. So even if I might not feel the same way tomorrow, I have the urge to share it now.

After a long time I'm in a situation where I sometimes work on a temporary system without my individual setup. Now whenever I might add a new custom (nushell) command that abstracts the usage of CLI tools, I think about the loss of muscle memory/knowledge for these tools and how much time I waste looking them up without my individual setup. No, that's not a huge amount of time, but just out of curiosity I'd like to know how I can minimize this problem as much as possible.

Do you have some tips and solutions to handle this dilemma? I try to shadow and wrap existing commands, whenever it's possible, but that's often not the case. Abbreviations in fish are optimal for this problem in some cases, but I don't think going back to fish as my main shell for this single reason would be worth it.

Sometimes I create a solution to a simple problem. However instead of making use of the solution, I keep extending it unnecessarily. This is why for this kind of project, I want to systematically restrain my future self from adding new features beyond the initial vision e.g. by actively refusing generic and re-usable code.

What is the search engine friendly term for this approach or at least for this situation? "Ad-hoc programming" may be literally what I'm talking about, but in practice it's associated with unplanned happenings.

Is there any kind of fiction where multiple stories are connected in a recursive loop? The connection could be a character who writes or narrates the story. e.g.

• story A -> story B
• story B -> story C
• story C -> story A

Thanks in advance for any help!