igoriuz · September 3, 2025 07:43
diff --git a/gistfile1.txt b/gistfile1.txt
 ## Development Principles

 ### Quality and Sustainability
 - Avoid being lazy or creating "dirty" quick fixes
 - Solve problems locally before applying fixes on servers
 - Implement long-term, maintainable solutions
 - We never use the simple quick-and-dirty way. We work cleanly and precisely because we are professional

 ### Code Organization
 - Avoid large, monolithic files
 - Break solutions into meaningful, modular components
 - Structure code into logical, reusable components
 - Clear separation of concerns by responsibilities

 ### Component Reuse
 - Always check for existing similar components that can be reused
 - Ask to refactor existing component instead of creating a duplicate
 - Either use existing Markdown documentation or find components in the project
 - Check documentation first when approaching any problem

 ### Documentation
 - Document project decisions in the "docs" folder using separate Markdown files
 - Document general development principles as well
 - Use documentation as primary reference when solving problems

 ### Data Management
 - Follow the Single Source of Truth principle
 - Avoid multiple information sources for the same data
 - Prefer storing information in the database where possible
 - Use temporary data storage only for specific cases like API calls with non-stale data

 ### Systematic Approach
 - Consult existing documentation first when facing any problem
 - Check for reusable components before developing new ones
 - Follow planned, thoughtful problem-solving approach
	## Development Principles

	### Quality and Sustainability
	- Avoid being lazy or creating "dirty" quick fixes
	- Solve problems locally before applying fixes on servers
	- Implement long-term, maintainable solutions
	- We never use the simple quick-and-dirty way. We work cleanly and precisely because we are professional

	### Code Organization
	- Avoid large, monolithic files
	- Break solutions into meaningful, modular components
	- Structure code into logical, reusable components
	- Clear separation of concerns by responsibilities

	### Component Reuse
	- Always check for existing similar components that can be reused
	- Ask to refactor existing component instead of creating a duplicate
	- Either use existing Markdown documentation or find components in the project
	- Check documentation first when approaching any problem

	### Documentation
	- Document project decisions in the "docs" folder using separate Markdown files
	- Document general development principles as well
	- Use documentation as primary reference when solving problems

	### Data Management
	- Follow the Single Source of Truth principle
	- Avoid multiple information sources for the same data
	- Prefer storing information in the database where possible
	- Use temporary data storage only for specific cases like API calls with non-stale data

	### Systematic Approach
	- Consult existing documentation first when facing any problem
	- Check for reusable components before developing new ones
	- Follow planned, thoughtful problem-solving approach
No results found