cats VS homeshick

Out of this frustration I've built: https://github.com/Endava/cats. It's for APIs, but mostly addressing exactly this case: don't use strings for everything, if you choose to use it though, make sure you add patterns for checking if things are valid, make sure you think about all the corner cases and all the weird characters that can brake you app, and so on.

If the API has an OpenAPI spec available, you can use: https://github.com/Endava/cats

This is why we need better tools which will give benefits for the added complexity. If you need to create both the feature files AND the code, it's just complexity with little benefits. But frameworks like https://github.com/karatelabs/karate or https://github.com/Endava/cats are hiding this complexity and remove the code layer entirely. Which, in my view, this is where you need to be in 2023, particularly for API testing.

I've built a tool specifically to test if these kind of characters will reach API backends: https://github.com/Endava/cats. My idea was that APIs should explicitly reject or sanitise input containing such characters.

Cats by Endava

This one's my favorite - has been working reliably and with barely any intervention for years now: https://github.com/andsens/homeshick

My own dotfiles: https://github.com/epiccoleman/dotfiles

I have a work mac, work linux, and home mac. I want the same terminal-based development environment on all of them, but each requires just a little bit of customization.

For example, the .gitconfig for work is different from home (e.g. my username/email). Ditto for my .ssh/config and my shell aliases.

I also use Nix to manage all my tools, and the home-manager configuration is slightly different between mac & linux due to platform support.

I've gone through a few iterations of home-built solutions, including extending homeshick[1], before discovering YADM which implemented everything I had done but better.

[1] https://github.com/andsens/homeshick

I do roughly the same and then manage them with 'homeshick' ( https://github.com/andsens/homeshick )

Have a look at https://github.com/andsens/homeshick project, it makes this workflow much easier.

Homeshick for dotfiles: https://github.com/andsens/homeshick

Docker for Obsidian and Alfred syncing - the three target limit on the free tier is just barely enough for 2 of my own computers and my work laptop.

I've also got a Brewfile for installing the basic tooling on macOS

I also have a "how to set up a new computer/server" document on Notion that I use so I don't forget any steps.

This is the exact reason I use Fish. The only thing I _need_ to get installed on random servers is Fish itself.

No need to install and configure oh-my-$shell or other huge monstrosities. Most of my stuff comes from a simple homeshick[1] sync with a few files in it.

[1] https://github.com/andsens/homeshick