"value":"\n <p>It's been <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2023\/08\/08\/8-years-of-dotfiles\">more than nine years<\/a> since I started <a href=\"https:\/\/github.com\/opdavies\/dotfiles.nix\">my dotfiles repository<\/a>, which is a collection of configuration files for tools I use.<\/p>\n\n<p>Originally containing my <code>.gitconfig<\/code> configuration file for Git, it now contains my configuration for Neovim, tmux, Git and a lot more.<\/p>\n\n<p>One of the things I like is being able to see and read other peoples' dotfiles and take inspiration from their configurations.<\/p>\n\n<p>I see some configurations that are very complex and customised, and some which are simpler.<\/p>\n\n<p>Recently, I've been thinking about how much customisation is too much, and moving towards a more minimal configuration.<\/p>\n\n<p>This isn't specific to command-line tools and also applies to customising GUI programs such as PhpStorm or VSCode.<\/p>\n\n<p>A more complex configuration means more code to maintain.<\/p>\n\n<p>It's more difficult to work on different computers, whether you're pair or mob programming, or working on a remote server. Would you still be productive if you didn't have all your configurations?<\/p>\n\n<p>If you've changed the default behaviour of a command, such as not allowing merge commits in Git or rebasing by default, if someone doesn't have that same option, is that going to cause confusion or introduce inconsistencies?<\/p>\n\n<p>I'm not going to reset all my configuration files to their default values, but I'll continue to review and decide whether I want to customise something on a case by case basis and whether adding it - especially if it's a larger addition, such as adding a Vim plugin - is worth the maintenance overhead.<\/p>\n\n<p>The same as in an application, I don't want to add modules or plugins that I'm not going to use or aren't adding value, and I want to ensure I'm making the most of what the software offers.<\/p>\n\n ",
"format":"full_html",
"processed":"\n <p>It's been <a href=\"https:\/\/www.oliverdavies.uk\/daily\/2023\/08\/08\/8-years-of-dotfiles\">more than nine years<\/a> since I started <a href=\"https:\/\/github.com\/opdavies\/dotfiles.nix\">my dotfiles repository<\/a>, which is a collection of configuration files for tools I use.<\/p>\n\n<p>Originally containing my <code>.gitconfig<\/code> configuration file for Git, it now contains my configuration for Neovim, tmux, Git and a lot more.<\/p>\n\n<p>One of the things I like is being able to see and read other peoples' dotfiles and take inspiration from their configurations.<\/p>\n\n<p>I see some configurations that are very complex and customised, and some which are simpler.<\/p>\n\n<p>Recently, I've been thinking about how much customisation is too much, and moving towards a more minimal configuration.<\/p>\n\n<p>This isn't specific to command-line tools and also applies to customising GUI programs such as PhpStorm or VSCode.<\/p>\n\n<p>A more complex configuration means more code to maintain.<\/p>\n\n<p>It's more difficult to work on different computers, whether you're pair or mob programming, or working on a remote server. Would you still be productive if you didn't have all your configurations?<\/p>\n\n<p>If you've changed the default behaviour of a command, such as not allowing merge commits in Git or rebasing by default, if someone doesn't have that same option, is that going to cause confusion or introduce inconsistencies?<\/p>\n\n<p>I'm not going to reset all my configuration files to their default values, but I'll continue to review and decide whether I want to customise something on a case by case basis and whether adding it - especially if it's a larger addition, such as adding a Vim plugin - is worth the maintenance overhead.<\/p>\n\n<p>The same as in an application, I don't want to add modules or plugins that I'm not going to use or aren't adding value, and I want to ensure I'm making the most of what the software offers.<\/p>\n\n ",