Code Maintenance
Also known as: software maintenance, legacy code
The ongoing process of updating, fixing, and improving software after its initial release to correct bugs, adapt to new requirements, and improve performance. Most professional developers spend more time maintaining existing code than writing new code.
💡 Intuition
Software is never 'done.' Like a garden, it needs constant tending — fixing bugs, updating dependencies, and adapting to changing needs.
Core Idea
Maintenance typically consumes 60-80% of software's total lifetime cost. Writing maintainable code from the start saves enormous effort later.
🔬 Example
🎯 Why It Matters
Most professional developers spend more time maintaining existing code than writing new code. Maintenance skills are essential.
⚠️ Common Confusion
Maintenance isn't just fixing bugs — it includes adapting to new requirements, improving performance, and preventing future problems.
Related Concepts
Prerequisites
Next Steps
How Code Maintenance Connects to Other Ideas
To understand code maintenance, you should first be comfortable with documentation and software development life cycle. Once you have a solid grasp of code maintenance, you can move on to version control.
Go Deeper
Frequently Asked Questions
What is Code Maintenance in CS Thinking?
The ongoing process of updating, fixing, and improving software after its initial release to correct bugs, adapt to new requirements, and improve performance.
Why is Code Maintenance important?
Most professional developers spend more time maintaining existing code than writing new code. Maintenance skills are essential.
What do students usually get wrong about Code Maintenance?
Maintenance isn't just fixing bugs — it includes adapting to new requirements, improving performance, and preventing future problems.
What should I learn before Code Maintenance?
Before studying Code Maintenance, you should understand: documentation, software development life cycle.