Skip to content

Add code-repo configuration issues to the list of tech debt examples #294

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
andyblundell merged 3 commits into from
Apr 17, 2023
Merged

Add code-repo configuration issues to the list of tech debt examples #294

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
78e57ba
Added code-repo config to the tech debt list
andyblundell Apr 17, 2023
4b61cf0
Update tech-debt.md
andyblundell Apr 17, 2023
506ed7e
Fix tab issue
andyblundell Apr 17, 2023
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
7 changes: 4 additions & 3 deletions tech-debt.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,9 +8,9 @@

"Technical debt" is a term which refers to undesirable things about the way a system is built which are not apparent to users of the system, but impact the ability of the team to make changes to it quickly and safely. Tech debt arises due to processes or practices in the past, but has an ongoing impact on the present, in that it:

* Leads to bugs and loss of reliability
* Means changes take longer to develop, and makes it harder to predict how long the work will take
* Causes dissatisfaction and disengagement in the delivery team
* Leads to bugs and loss of reliability
* Means changes take longer to develop, and makes it harder to predict how long the work will take
* Causes dissatisfaction and disengagement in the delivery team

There are many different views on what is and isn't tech debt - this is ours.

Expand Down Expand Up @@ -41,6 +41,7 @@ Here is a non-exhaustive list of examples we consider to be *in* scope of "techn
* Code you no longer need ([e.g. a new managed service is available](patterns/outsource-bottom-up.md))
* Technologies no longer needed (e.g. you've introduced something better than what you used before)
* CI issues, e.g. lack of [fast feedback](patterns/fast-feedback.md), or intermittent [build failures](practices/continuous-integration.md)
* [Code-repository configuration issues](practices/security-repository.md), e.g. lack of branch protection rules
* Manual processes that could be [automated](patterns/automate-everything.md)
* Software components with inappropriate / confused [domain boundaries](patterns/architect-for-flow.md)
* Use of obsolete / unsupported technologies
Expand Down