garden VS sd

https://github.com/davvid/garden

Project Description: Garden is a git multi-repo powertool. Garden lets you define custom workflows over arbitrary collections of git trees.

If you find yourself running bespoke commands across a smattering of git repositories then Garden can be a big improvement over a big pile o' scripts and repos.

What do you want to be tested: Test the documented feature-set and new-user onboarding experience. Give feedback on its usefulness as a development/testing aid.

Contact Info: Open an issue on the project page

If you're into this kinda thing then then you might be interested in my take on improving over a "big pile o scripts" (and repos).

https://github.com/davvid/garden

Garden is a multi-repo powertool for running custom commands and mashing random shell scripts and loosely-coupled repos into a version-controllable config file. If you're weird like me you might like it.

I ended up with so many random git repos, shell scripts and other miscellany that I ended up writing a tool to manage that stuff using a yaml file so that it's easy to transport and recreate my setup anywhere.

"garden" is kinda like a mashup of the flexibility/power of shell scripts with the convenience of being able to declare your development environment.

https://github.com/davvid/garden

I was kinda surprised when someone submitted the first issue =)

https://github.com/davvid/garden/issues/1

git-cola was pretty much written for my own personal use, but it grew a few more users as well.

Prefixing these utility scripts is a nice tip, I used to do that as well.

Some time ago I found https://github.com/ianthehenry/sd though. It's a light wrapper around your own scripts which provides namespaces, autocompletion, custom help texts + some other QoL enhancements around that. It improves discoverability and usability a lot, very happy with it.

A few things that can help with memory:

- spaced repetition for stuff that you use sporadically. I use Anki, it's great. For how to use it, this article is great: https://borretti.me/article/effective-spaced-repetition. I've found a positive feedback loop where the more I know how to do things without looking anything up, the more I use the CLI, the easier I remember things, the more things I discover, etc. I read once that when learning a new language, you should aim for content where you know 80%/90% already. It seems to be true for learning the CLI, and especially for integrating that learning into my day to day job.

- sd (https://github.com/ianthehenry/sd) for lowering the cost of creating a "documented alias". Before that I made aliases with either alias, or bash functions, all starting with "," to quickly see all which are "mine" (I read that trick in an article that I can't find), now the more complex stuff is in sd with some documentation.

Yeah :( https://github.com/ianthehenry/sd/issues/9

The trouble is `sd` is just so easy to type on a qwerty keyboard, and it's such a nice mnemonic for "script directory." I've thought about renaming it, but I can't think of anything I like nearly as much.

zsh can do this if you set the PATH_DIRS option, but if I remember right it doesn't autocomplete deeply nested directories, just one level.

I made a little tool that dispatches hierarchical commands in a slightly nicer way, with intelligent autocomplete with command descriptions: https://github.com/ianthehenry/sd