With some configuration, developers would be able to run the frontend server in their local environment in Debug mode (the Debugging tab in VS Code). With this set up, breakpoints can be inserted very easily and data can be examined without the need to insert console.log() everywhere in the code. This could speed up development time and reduces the likelihood of a console.log statement sneaking its way into the production environment (where it doesn't belong).
Tech Debt Triage
The purpose of our technical debt triage process is to analyze technical debt to determine risk level of the technical debt and the value in tackling that technical debt.
Risk Value Scoring:
Level
Value
High
3
Medium
2
Low
1
Technical Debt - Risk Types
Level
Value
Business Area Risk - Risk of business area visibility / damage to user experience
1
Developer Fault Risk - How likely will this tech debt cause a future error related to coding on top of it
2
System Fault Risk - Risk of system errors or application downtime
1
Time Scale Risk - Compound risk effect if left alone. How much more difficult to fix or dangerous will this become over time?
1
Time Sink Risk - How much will this tech debt slow the development process down
Description of the Tech Debt
With some configuration, developers would be able to run the frontend server in their local environment in Debug mode (the Debugging tab in VS Code). With this set up, breakpoints can be inserted very easily and data can be examined without the need to insert
console.log()
everywhere in the code. This could speed up development time and reduces the likelihood of a console.log statement sneaking its way into the production environment (where it doesn't belong).Tech Debt Triage
The purpose of our technical debt triage process is to analyze technical debt to determine risk level of the technical debt and the value in tackling that technical debt.
Risk Value Scoring: