# Notes — Genyra

> Engineering notes from Genyra: COBOL to Java as the wrong modernization, what legacy code is and how to analyse it, and private AI with self-hosted LLMs.

Canonical page: https://genyra.com/notes

Longer pieces on the questions behind the work: why COBOL outlived its replacements, what legacy code actually is, and what it takes to run AI inside your own boundary.

## Why we write these.

A service page says what we do. A note explains why we do it that way, with enough detail that an engineer can disagree with us on the merits. Each piece stays on one question, states what it rests on, and is updated when the position changes.

Nothing here is a case study. Where an example is needed it is a synthetic one, and it says so.

## Current notes.

The pieces are listed below, most recent first. Each one links back to the service page it informs.

## Related work

- [Private AI: running language models inside your boundary](https://genyra.com/notes/private-ai-inside-the-boundary): What private AI means, when a self-hosted LLM is required, what runs inside the boundary, how to size hardware honestly, and how it is operated.
- [What legacy code is, and how to analyse it](https://genyra.com/notes/what-is-legacy-code): What legacy code means, how it differs from technical debt, and how legacy code analysis tells you whether to refactor, rebuild or leave a system alone.
- [COBOL to Java was the wrong modernisation](https://genyra.com/notes/cobol-to-java-was-the-wrong-modernisation): COBOL to Java modernization left application servers, JVM upgrades and licences that are now the next legacy. Why native is the point, and what to do instead.

Contact: contact@genyra.com

Genyra LLC and the Dubai business Genyra L.L.C-FZ / Genyra.ai are distinct entities. Project scope and the contracting entity are agreed explicitly.