Development practices are the repeatable techniques a team uses while designing, building, checking, and changing software. They support several parts of the Software Development Life Cycle rather than belonging to one isolated phase.
For example, a developer may write a unit test while implementing a requirement, run that test during continuous integration, and use the result during code review. The same test can later help maintainers detect an unintended change.
Current notes
- Modular Design
- OOP Design
- Maintaining Modularity
- Unit Testing and Test-Driven Development
- Code Review and Pull Requests
The notes start with modular boundaries and object-oriented design, then look at keeping those boundaries useful as software grows, testing behaviour, and reviewing changes. This is a reading order, not a rigid sequence of SDLC phases: the practices overlap throughout development and maintenance.
These practices reinforce one another. Modular design creates focused responsibilities and interfaces. Tests provide repeatable evidence about behaviour. Reviewers examine the change, its design, its risks, and whether the evidence is suitable. Future notes can cover broader testing strategies, version control, continuous integration, secure development, and release practices.