---
title: "Every SAP codebase I audit has the same blind spot."
date: "2026-04-14"
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:ugcPost:7449784981343641603
canonical: https://damirmajer.com/notebook/2026-04-14-every-sap-codebase-i-audit-has-the-same-blind-spot/
---

# Every SAP codebase I audit has the same blind spot.

LinkedIn · Post · By Damir Majer · 14 April 2026

It is not the code.\
It is the boundaries.

The Code Lens catches naming, duplication, and method size.\
Important.\
But not sufficient.

The Architecture Lens sees what code reviews miss:

1\. Where modules know too much about each other\
2\. Where a change in one place forces changes in five others\
3\. Where boundaries exist on paper but not in practice

These are decisions that compound.\
Every sprint they stay invisible, the cost of every future feature goes up.

Not because developers write bad code.\
Because nobody looks at the level where the real damage happens.

What is the one boundary in your codebase that everyone knows is wrong but nobody touches?

#SoftwareCraft #SoftwareArchitecture

## Sources

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