Skip to content

Expand on patlet/problem of Modular Code Pattern #293

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Mar 22, 2022
Merged

Expand on patlet/problem of Modular Code Pattern #293

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
5ae99ce
Adding Patlet, rewriting Problem
spier Feb 13, 2021
207139f
modified Problem statement
spier Jul 4, 2021
49dae25
Fix caps in 'open source'
spier Jul 4, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions patterns/1-initial/modular-code.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,11 @@ Modular Code

## Patlet

TBD
The lack of modularization in the software architecture prevents reuseability, and with that the ability to reap the benefits of InnerSource. By helping the teams to understand the benefits of modularization, and making time to work towards that goal, more InnerSource collaboration can happen and the software architecture overall can be improved.

## Problem

Development does not want to spend the extra resources needed to develop modular components. As a result, shared components are not reused.
Engineering does not want to spend the extra resources needed to develop modular components. This applies to managers and developers alike. As a result, fewer components end up being reused, leading to duplication of work.

## Context

Expand Down Expand Up @@ -39,7 +39,7 @@ Development does not want to spend the extra resources needed to develop modular
* Provide incentives to teams to invest in modular code. Modular code is far more reusable. This could work well for large teams when working on modularized projects; team members can focus on their smaller assigned tasks.
- Developers could get an opportunity to increase their influence in the organization.
- Modular code makes the pathway to open source smoother.
- Modular code facilitates division of labour (as required for work in larger teams, or as an Open Source project)
- Modular code facilitates division of labour (as required for work in larger teams, or as an open source project)
- Modular projects enable team members to focus on their own smaller assigned tasks.
- Modular code makes Agile implementation easier.
- Modular efforts increase autonomy and accountability for Engineers, which can raise satisfaction and quality.
Expand Down