Tool Selection and Usage Policy #
This document explains tools used at Pandion Ltd. and the reasons for their selection.
Basic Policies #
Selection Based on Purpose #
- Tools are means to achieve purposes
- Consider balance of functionality, cost, and learning cost
- Select according to team skill level
Ensuring Consistency #
- Unify tools for the same purpose
- Value data integration and visibility
- Minimize operational costs
Development Tools #
Version Control #
- Git: Distributed version control system
- Reason: Industry standard, flexibility, abundance of learning resources
- Usage: Use GitHub or GitLab
Code Management #
- GitHub/GitLab: Code hosting and CI/CD
- Reason: Integrated development environment, security features
- Usage: Private repositories as standard
Development Environment #
- IDE: Select according to personal preference
- Recommended: VS Code (free, rich extensions)
- Reason: Lightweight, multi-language support, debugging features
Communication Tools #
Chat #
- Google Chat: Internal communication
- Reason: Integration with Google Workspace, simple operation
- Usage: Daily internal communication
- Clients: Use tools specified by clients (Slack, Teams, etc.)
Video Conferencing #
- Zoom/Teams: Online meetings
- Reason: Stability, recording features, large-scale support
- Usage: Pre-meeting preparation and agenda sharing
Email #
- Gmail: Formal communication
- Reason: Reliability, recordability, security, integration with Google Workspace
- Usage: Clear subject lines, set reply deadlines
Project Management #
Task Management #
- Notion: Project management and documentation
- Reason: Flexibility, integration, low learning cost
- Usage: Workspace per project
Time Management #
- Currently not implemented: Time tracking is not performed
- Future consideration: Consider tool introduction as needed
Document Management #
Document Management #
- Google Drive: Internal documents
- Reason: Integration with Google Workspace, access control, backup
- Usage: Organize in hierarchical structure, set appropriate permissions
Security Tools #
Password Management #
- Bitwarden-based: Password management
- Reason: Open source, security, cost efficiency
- Usage: Secure password management for individuals and teams
VPN #
- WireGuard: VPN connection
- Reason: Lightweight, fast, security
- Usage: Required for remote work
Cloud Services #
Infrastructure #
- AWS: Cloud infrastructure
- Reason: Rich services, scalability, learning resources
- Usage: Use minimum necessary services
Storage #
- Google Drive: File sharing
- Reason: Integration, access control, backup
- Usage: Set appropriate permissions
Monitoring and Logging #
Application Monitoring #
- Appmil: Monitoring for internal projects
- Reason: Lightweight, simple, cost efficient
- Usage: Use for internal projects
- Clients: Use monitoring tools specified by clients
Log Management #
- CloudWatch/Loggly: Log management
- Reason: Aggregation, search, alert features
- Usage: Output structured logs
Tool Introduction and Changes #
New Tool Introduction #
- Confirm Necessity: Consider whether existing tools can solve it
- Evaluation: Evaluate functionality, cost, learning cost
- Trial: Set trial period on small scale
- Introduction: Gradual introduction after team-wide consensus
Tool Review #
- Regular Evaluation: Review quarterly
- Effect Measurement: Confirm usage and effectiveness
- Improvement: Consider better tools if available
Cost Management #
Budget Setting #
- Set monthly budget per tool
- Manage annual budget
- Evaluate ROI (Return on Investment)
Utilizing Free Tools #
- Actively utilize open source tools
- Maximize use of free tiers
- Move to paid plans as needed