---
title: "You're maintaining code you didn't write."
date: "2026-02-22"
language: en
text: full
source: "LinkedIn"
format: "Post"
credit: "By Damir Majer"
contributors:
  - name: "Damir Majer"
    role: author
original: https://www.linkedin.com/feed/update/urn:li:share:7431423378110046208
canonical: https://damirmajer.com/notebook/2026-02-22-you-re-maintaining-code-you-didn-t-write/
---

# You're maintaining code you didn't write.

LinkedIn · Post · By Damir Majer · 22 February 2026

That used to mean legacy code. Old stuff. Known unknowns.

Now it also means last week's AI-generated code that nobody reviewed properly.

3 signals your codebase is crossing into unmaintainable territory:

1\. Time to understand a change > time to make the change\
2\. Only 1-2 people can safely touch the critical modules\
3\. Code reviews are rubber stamps because nobody has time to think

The first two were always there. The third is new.

AI writes in seconds. You maintain for months.

The maintenance tax is invisible until someone leaves.\
Or until the module breaks at 2am on a Friday.

I've seen teams where 60% of development time is spent reading code, not writing it.\
Not because they're slow. Because the code fights back.

\---

What percentage of your time goes to maintaining code you didn't write?

#CleanCode #SoftwareEngineering #TechnicalDebt #CodeQuality

## Sources

- [View the original on LinkedIn](https://www.linkedin.com/feed/update/urn:li:share:7431423378110046208)
