mapsi

1. Clear Channel Naming Conventions:
   • Project Channels: Use a consistent format like project-<name> for channels related to specific projects. For example, project-acme-website.
   • Functional Channels: Prefix functional channels with their purpose, such as design-, devops-, or marketing-.
   • General Channels: Create general channels like general, announcements, and random for broader discussions.
   • Location-Specific Channels: If your team is distributed, consider channels like london-team, nyc-team, etc.
   • Avoid Abbreviations: Use clear and descriptive names to avoid confusion.
2. Review Channels Regularly: Periodically review your channels to ensure they remain relevant and organised. Consider archiving channels that are no longer active or necessary.
3. Use Notion for Permanent Information: While Slack is great for real-time communication, consider Notion as the primary repository for permanent information. Use Notion for documen

mapsi

brew install kitty nvim git lazygit ripgrep fd

# required
mv ~/.config/nvim{,.bak}

# optional but recommended
mv ~/.local/share/nvim{,.bak}
mv ~/.local/state/nvim{,.bak}
mv ~/.cache/nvim{,.bak}

mapsi

# vim:fileencoding=utf-8:foldmethod=marker

#: Fonts {{{

#: kitty has very powerful font management. You can configure
#: individual font faces and even specify special fonts for particular
#: characters.

# font_family      monospace
# bold_font        auto

mapsi

# Git abbreviations converted from oh-my-zsh git plugin
# Add this to ~/.config/fish/conf.d/abbreviations.fish or similar

# Helper functions

function git_main_branch --description 'Get the default main branch name'
    command git rev-parse --git-dir &>/dev/null; or return
    
    set -l branches main trunk mainline default stable master