# MEMORY.md - Long-term Memory

## Personal Preferences

- **Favorite food:** French fries 🍟
- **Favorite drink:** Coffee, especially Americano
- **Work schedule:** Prefer to handle important tasks in the morning, use afternoons for deep thinking and creative work
- **Communication style:** Prefer concise and clear communication, lengthy explanations reduce efficiency
- **Music preferences:** Enjoy lo-fi and ambient music while working, helps maintain focus and calm
- **Workspace environment:** Prefer clean, organized workspace with minimal distractions
- **Reading habits:** Lean towards technical books over fiction, invest time in continuous learning
- **Motivation factors:** Driven by solving real problems and seeing measurable impact from work

## Work Habits

- **Code preferences:** Emphasize code readability and maintainability, prefer clear structure and meaningful naming
- **Project management:** Like using kanban for task management, visualizing progress gives work better rhythm
- **Learning style:** Learning through practice is more effective than pure theoretical study, try to solve problems first before seeking help
- **Meeting preferences:** Prefer asynchronous communication over frequent meetings, value documentation of decisions
- **Deep work blocks:** Set aside 2-3 hour blocks for uninterrupted focus time, especially for complex problems
- **Note-taking:** Keep detailed technical notes in markdown format, organized by topic for easy reference
- **Problem-solving approach:** Break complex issues into smaller components, tackle systematically

## Skills and Interests

- **Programming languages:** JavaScript/TypeScript are main working languages, also know Python
- **Tool preferences:** Like using modern development tools, use keyboard shortcuts to improve efficiency
- **Hobbies and interests:** Care about AI and automation tools, enjoy exploring ways to improve productivity
- **Technical areas:** Interested in system architecture, API design, and performance optimization
- **Side projects:** Occasionally work on personal tooling projects to automate daily tasks
- **Tech stack comfort:** More comfortable with backend development but can handle frontend when needed
- **Debugging style:** Think through the problem first before diving into code, use systematic approach

## Important Decisions

- **2026-04-03:** Decided to establish structured memory management, recording important long-term information through MEMORY.md to avoid forgetting key details
- **Trust principles:** For AI assistants, tend to give moderate trust but maintain review permissions for sensitive operations
- **Information management:** Believe structured knowledge management is more valuable than scattered notes, invest long-term in memory organization
- **Technology investments:** Willing to invest in tools that provide long-term value, not just short-term convenience
- **Open source stance:** Generally supportive of open source tools, but evaluate carefully before adoption
- **Aversion to lock-in:** Prefer tools and services that don't create vendor lock-in, value flexibility

## Things Worth Remembering

- Quick to learn new tools: immediately invest time in mastering once value is recognized
- Dislike repetitive tasks: proactively seek automation solutions
- Before making important decisions,习needs collect sufficient information first, but won't over-research to the point of analysis paralysis
- Value work-life balance: serious about work but don't agree with excessive overtime
- Resilient under pressure: maintain calm and systematic approach even when deadlines are tight
- Admit mistakes readily: believe owning errors leads to faster learning and improvement
- Appreciate direct feedback: prefer honest constructive criticism over vague encouragement

## Development Preferences

- **Code review:** Value code quality, carefully review PRs but won't get stuck on details
- **Documentation:** Believe good documentation is important, but think code itself is the best documentation
- **Testing:** Support test-driven development, but won't test for the sake of testing, focus on core functionality
- **Version control:** Habitually commit small changes frequently, keep history clear and roll-backable
- **Git workflow:** Prefer feature branching over direct commits, squash messy history before merging
- **Code organization:** Strong preference for modular architecture over monolithic structures
- **Error handling:** Care about proper error handling and logging, but won't over-engineer for edge cases

## Collaboration Style

- **Team dynamics:** Prefer small, focused teams over large distributed ones
- **Code ownership:** Comfortable with collaborative code but like understanding ownership boundaries
- **Feedback timing:** Provide feedback sooner rather than later, but always constructively
- **Conflict resolution:** Address disagreements directly but respectfully, focus on solutions not blame
- **Knowledge sharing:** Enjoy teaching and learning from team members, value collaborative growth

## Technology Philosophy

- **Simplicity over complexity:** Always choose the simpler solution unless there's strong reason otherwise
- **Pragmatism:** Prefer practical working solutions over perfect theoretical ones
- **Future-proofing:** Design for the next 2 years, not the next 10, avoid over-engineering
- **Technical debt tolerance:** Accept some debt if it delivers value faster, plan to pay it down
- **Framework minimalism:** Prefer using minimal dependencies, each dependency should earn its place

## Life Principles

- **Continuous improvement:** Believe in steady incremental progress over sudden leaps
- **Health awareness:** Prioritize sleep and physical health as foundations for productivity
- **Time valuation:** Respect others' time by being prepared and punctual for commitments
- **Curiosity maintenance:** Keep learning new things outside of work to stay mentally flexible
- **Social boundaries:** Have clear boundaries between work and personal life, respect both


