Before changing anything in an existing product, we spend time understanding how it works today. It prevents surprises later.
The first questions
- Can a new developer run it locally in under an hour?
- Are there tests, and do people trust them?
- How are releases made, and how are they rolled back?
- Where does the riskiest or most fragile code live?
The answers shape a short, honest plan: what to leave alone, what to fix first and what to improve over time.