Working principles and habits that make software easier to change and less likely to break. The group includes the SOLID principles of object-oriented design, the rule against repeating the same knowledge in several places, writing automated tests before the code they check, integrating every change into a shared codebase often, passing a component what it needs rather than building it inside, and restructuring code without altering what it does.
Browse By
Software Engineering Practices
Filter Results6 entries
Sources
SOLID - Wikipedia
Has Member: SOLID Principles, LeadQuote, Has Member: SOLID Principles, Lead
In object-oriented programming and functional programming, SOLID is a mnemonic acronym for five principles intended to make source code more understandable, flexible, and maintainable.
Don't repeat yourself - Wikipedia
Has Member: Don't Repeat Yourself, LeadQuote, Has Member: Don't Repeat Yourself, Lead
"Don't repeat yourself" (DRY) is a principle of software development aimed at reducing repetition of information which is likely to change, replacing it with abstractions that are less likely to change, or using data normalization which avoids redundancy in the first place.
Test-driven development - Wikipedia
Has Member: Test-Driven Development, LeadQuote, Has Member: Test-Driven Development, Lead
Test-driven development (TDD) is a way to write source code that involves writing an automated unit-level test case that fails, then writing just enough code to make the test pass, then refactoring both the test code and the production code, then repeating with another new test case.
Continuous integration - Wikipedia
Has Member: Continuous Integration, LeadQuote, Has Member: Continuous Integration, Lead
Continuous integration (CI) is the practice of integrating source code changes frequently and ensuring that the integrated codebase is in a workable state.
Dependency injection - Wikipedia
Has Member: Dependency Injection, LeadQuote, Has Member: Dependency Injection, Lead
In software engineering, dependency injection is a programming technique in which an object or function receives other objects or functions that it requires, as opposed to creating them internally.
Code refactoring - Wikipedia
Has Member: Refactoring, LeadQuote, Has Member: Refactoring, Lead
In computer programming and software design, code refactoring is the process of restructuring existing source code-changing the factoring-without changing its external behavior.
Reader Challenges (0)
No disputes yet. Spotted an error or a better source? Open the first one.
Sign in to dispute this or suggest a correction.