---
title: "3 languages. 200+ developers. 1 pattern."
date: "2026-02-03"
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:7424289780785483776
canonical: https://damirmajer.com/notebook/2026-02-03-3-languages-200-developers-1-pattern/
---

# 3 languages. 200+ developers. 1 pattern.

LinkedIn · Post · By Damir Majer · 3 February 2026

I've been coaching developers for 20 years.\
ABAP. Java. Web/TypeScript.

And the pattern is always the same:

1\. Methods that never end\
"This function has 500 lines, but it works."\
\- In ABAP: FORM routines with 800 lines (yes, they still exist)\
\- In Java: Service classes with 2,000 lines\
\- In TypeScript: React components with 600 lines

2\. No tests\
"We don't have time for tests."\
\- In ABAP: Unit tests? "We have QA."\
\- In Java: 12% coverage. "Good enough."\
\- In TypeScript: "We test manually in the browser."

3\. Copy-paste as architecture\
"It worked last time."\
\- In ABAP: Z-programs that only differ by name\
\- In Java: Util classes with 47 static methods\
\- In TypeScript: 12 nearly identical API handlers

Technical debt speaks no programming language.

And neither does the solution.

The same principles - naming, single responsibility, TDD, refactoring - work in every language.

Not because they're abstract.\
Because they're fundamental.

Which language does your team see itself in?

#TechnicalDebt #CleanCode #SoftwareQuality

## Sources

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