This directory contains utility scripts that follow the "spilled coffee principle" - ensuring that anyone can quickly restore their environment after a system failure.

Installs Java and sets up necessary environment variables. Supports multiple platforms and Java versions.

# Install default Java version (17)
./install-java.sh

# Install specific Java version
./install-java.sh 11

Features:

• Detects operating system automatically
• Supports Debian, Fedora, Arch, and macOS
• Falls back to manual installation for unsupported systems
• Sets up JAVA_HOME and PATH environment variables
• Provides educational information about the JVM

Installs Go and sets up the Go workspace.

./install-go.sh

Features:

• Detects operating system and architecture
• Attempts to install using system package manager
• Falls back to manual installation if needed
• Sets up GOPATH and other environment variables

Resolves conflicts between npm and nvm installations.

./fix-npm-nvm-conflict.sh

When adding new utility scripts, please follow these guidelines:

1. Naming Convention: Use install-{tool}.sh for installation scripts
2. Error Handling: Include proper error handling and status messages
3. Cross-Platform: Support multiple platforms when possible
4. Documentation: Add usage instructions in the script header
5. Environment Variables: Set up necessary environment variables
6. Idempotence: Scripts should be safe to run multiple times
7. Educational Content: Include information about the tool being installed
8. Logging: Use the common logging functions from logging.sh

All utility scripts should use the common logging functions provided in logging.sh. This ensures consistent output formatting and makes it easier to distinguish between different types of messages.

# Source the logging functions at the top of your script
SCRIPT_DIR="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
source "${SCRIPT_DIR}/logging.sh"

# Available logging functions
log_info "This is an informational message"
log_success "This is a success message"
log_warning "This is a warning message"
log_error "This is an error message"
log_debug "This is a debug message (only shown if DEBUG=1)"

Benefits of using these logging functions:

• Consistent visual formatting across all scripts
• Clear distinction between different message types
• Easier debugging and troubleshooting
• Ability to filter messages by type

The "spilled coffee principle" states that anyone should be able to destroy their machine and be fully operational again that afternoon. These utility scripts help achieve this by automating the setup of various development tools and environments.