Keep it Small
Last updated
What is Keep it Small?
You should design and implement small, focused components that serve a specific purpose, rather than large, monolithic components that try to do everything. This can help to improve the maintainability and scalability of the system by making it easier to understand, test, and modify individual components.
More in stage 3: Object Oriented Programming
- Object Oriented Programming
- Be consistent
- Meaningful names over comments
- Indentation and Code Style
- Pure functions
- Minimize cyclomatic complexity
- Avoid passing nulls, booleans
- Keep framework code distant
- Use correct constructs
- Tests should be fast and independent
- Organize code by actor it belongs to
- Command query separation
- Keep it simple and refactor often
Keep it Small: common questions
Can I learn Keep it Small in Hindi?
This lesson is written in English. Once you sign in, open it in the interactive course and ask the AI tutor to explain Keep it Small in Hindi or Hinglish. The tutor answers from this lesson’s own text, so it stays on the syllabus, and it runs on your own Google, OpenAI or Anthropic key.
Is this Keep it Small tutorial for beginners?
It is lesson 19 of 94 in the free Software Design and Architecture roadmap, in stage 3, Object Oriented Programming. If you are new to Software Design and Architecture, start from stage 1 and come back here in order; if you already know the earlier stages, this lesson stands on its own.