Developer Playbook
Your guide to setting up your development environment, understanding our architecture, and shipping production-grade features with confidence.
Welcome to the team! We’re a small, focused development team building production-grade SaaS applications and Shopify apps. Our engineering culture is built on four core principles: Predictability, Readability, Simplicity, and Upgradability.
This playbook contains everything you need to get started, from local setup to deployment workflows. Use the navigation below or the sidebar to explore our standards, workflows, and best practices.
Essential Resources
Before diving into our codebase, familiarize yourself with these industry-standard guides:
Communication & Best Practices
- How To Ask Questions The Smart Way - Learn to ask effective technical questions
- The Twelve-Factor App - Best practices for SaaS development
Style Guides
- Python: PEP 8, Google Python Style Guide
- JavaScript/TypeScript: Airbnb JavaScript Style Guide, TypeScript Best Practices
Code Quality
- Google’s Code Review Guide - Effective code reviews
- Conventional Commits - Standardized commit messages
- OWASP Top 10 - Security best practices
📖 See the Getting Started section for a comprehensive list of recommended reading.
New Team Member? Start Here
Tech Stack Overview
Backend (Python-based)
- FastAPI with Python 3.14
- PostgreSQL 15+ for data storage
- Redis for caching and queues
- Celery for background jobs
- Docker + Docker Compose for local dev
Backend (TypeScript/Node-based)
- Node.js 22.21.0 (NestJS/Fastify/Express)
- PostgreSQL 15+ for data storage
- Redis for caching and queues
- BullMQ for background jobs
- Docker + Docker Compose for local dev
Frontend (React)
- React 18+ with TypeScript or JavaScript
- Next.js for build tooling and SSR
- Tailwind CSS for styling
- Node.js 22.21.0 recommended
- Bun for fast package management
Development Tools
- Biome for linting and formatting
- Ruff for Python linting
- Pre-commit hooks for code quality
- Vite for fast development builds
- Postman for API testing
Documentation Sections
Our Engineering Culture
The Four Rules
- Predictability - Every endpoint follows the same pattern, every component has the same structure
- Readability - Code should tell a story that anyone can understand
- Simplicity - Minimal dependencies and clear separation of concerns
- Upgradability - Version APIs, keep business logic in services, design for change
What We Value
- Shipping early and often - small, incremental improvements
- Clear communication - over-communicate in async environments
- Testing - if it's not tested, it's broken
- Documentation - future you will thank you
- Code reviews - learn from each other, maintain quality