> Don't you hate it when you can't find the scripts you need, when you need it? Well now there's a better way! It's a good start, and there are definitely some

> Don't you hate it when you can't find the scripts you need, when you need it? Well now there's a better way! It's a good start, and there are definitely some ideas worth stealing there, but I don't think it really solves the core problem. Not when you have scripts that cross problem domains, or the name isn't very intention revealing, or you've just got hundreds of them. The real key to solving this, is searchable documentation. Yeah, I know. No-one wants to write docs. But it doesn't have to be hard, and it doesn't have to be much. It just has to be enough that when next have a problem that involves say "image manipulation" you can ask your system for things that handle "images" and have it list them. That's why I wrote TooLoo: https://tooloo.dev https://tooloo.dev TooLoo's not for everyone, but if you've been building up your own library of useful utilities then I'd _strongly_ recommend you consider the value you'll gain from the combination of a little bit of documentation + Full Text Search. Full Text search is, I think, really important. I don't want to not find something because I searched for "image" instead of "images" or vice versa. You need a search engine that'll deal with stemming. In documenting my tools for TooLoo I found many useful things that I'd written and completely forgotten about, and others that I'd duplicated because I'd forgotten I already had something like that. Now I always start by asking TooLoo if I have something relevant, or how to use that relevant thing I haven't touched in 3 years. Anyway. If this type of stuff sounds interesting to you check out TooLoo. If TooLoo's not right for you, make something cool for yourself that uses Full Text Search to find the stuff you need. Most databases have it built in these days: SQLite, PostgreSQL, MySQL, MongoDB, etc.