Skip to content

Commit 571a804

Browse files
authored
Add GitHub usage and perspective (InnerSourceCommons#528)
Add GitHub usage and perspective
1 parent 2eb1c0b commit 571a804

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

patterns/1-initial/modular-code.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,6 +62,7 @@ and therefore promotes external contributions and onboarding of newcomers.
6262
1. Develop automated testing protection.
6363
1. Document usage of modules.
6464
1. Introduce semantic versioning.
65+
1. Committing to not breaking backwards compatibility.
6566
1. Use a dependency management software such as pip, nuget, npm.
6667
* More information and techniques are available from the book *[Working Effectively with Legacy Code](https://www.oreilly.com/library/view/working-effectively-with/0131177052/)* by Michael Feathers and *[Refactoring: Improving the Design of Existing Code](https://martinfowler.com/books/refactoring.html)* by Martin Fowler.
6768

@@ -72,10 +73,13 @@ and therefore promotes external contributions and onboarding of newcomers.
7273
* Modular code helps Agile: For the same functionality, you'll need to change more bits, but the modularity helps to materialize sooner (earlier and more reliable validations) and to prioritize the most relevant bits (separate value from waste).
7374
* Modular efforts increase autonomy and accountability for Engineers, which can raise satisfaction and quality.
7475
* Modular code makes the pathway to InnerSource and open source smoother.
76+
* Modular code gets used more often, and that diverse set of users often leads to higher quality code.
7577

7678
## Known Instances
7779

78-
Elements of the resolution have been proven by various companies.
80+
Elements of the resolution have been proven by various companies such as
81+
82+
- GitHub
7983

8084
## Status
8185

0 commit comments

Comments
 (0)