Skip to main content
Skip to content
Menu

Enterprise Software Intermediate 3 parts Updated

Build a technical debt classifier

You'll have a working script that automatically flags code, process, or system changes that create future maintenance costs — so you can surface hidden debt before it compounds.

What you'll make

Technical Debt Classifier

  1. scan_files() — the debt detection function: what to include
  2. load_context_rules() — your override criteria: what to include
  3. score_debt_impact() — prioritization logic: what to include
  4. main() — orchestration and reporting: what to include

Paste your Python script that runs against real files or documentation from your system

The 3 parts

Each part ends with a check you can see.

  1. Map Your Maintenance Burden

    Catalog what actually costs you time when working on your system to establish baseline debt patterns

    Done when

    A ranked list of your top 10 maintenance pain points with time estimates and specific examples from recent work

  2. Build the Detection Logic

    Create a scan_files() function that automatically flags your specific debt patterns in code or documentation

    Done when

    Working scan_files() function that detects at least 3 of your maintenance patterns when run against real files from your system

  3. Calibrate Impact Scoring

    Build score_debt_impact() and load_context_rules() functions that prioritize debt findings based on your actual maintenance costs

    Done when

    Complete classifier that runs on real files and produces a ranked debt report where the top items match your manual priority assessment

    Capstone: you put together your Technical Debt Classifier.

Where this helps

An elective: a single lesson that sits outside rtwo's job certificates and doesn't count toward one.

About this lesson

What you'll be able to do

  • Run a working technical debt classifier on your actual codebase or system documentation
  • Identify where AI catches maintenance risks vs where your domain knowledge has to override
  • Have scored criteria for what constitutes debt in your context vs generic code quality flags
  • Create a repeatable process for debt assessment that improves over time

Who it's for

  • Software engineers or technical leads who inherit systems and need to understand hidden maintenance costs
  • Anyone responsible for system modernization decisions who wants objective debt measurement
  • Teams trying to quantify technical debt beyond 'this feels messy'

What it won't cover

  • Actually fixing the debt you find — this is about detection and measurement
  • Setting up code analysis infrastructure from scratch
  • Convincing leadership to prioritize debt reduction

Skills you'll practise

  • Pattern recognition for technical debt indicators
  • Threshold calibration for automated flagging
  • Context-specific override rule development
  • Debt impact scoring and prioritization