On systems that outlast their commission.

Software that works on launch day is not the same as software that remains useful five years later. The difference is rarely a matter of features. It is a matter of judgment: what to include, what to leave out, how to name things, and how to leave a system that someone else can understand when the original authors are no longer in the room.

At Cadmus, technical work is not treated as a service that ends at delivery. It is treated as a responsibility that continues for as long as the system is depended on. That changes what "done" means. It changes how architecture is chosen. It changes how carefully interfaces are designed.

The environment around a system is part of the system. Local constraints—connectivity, operational habits, institutional memory, the people who will actually run the thing—are not edge cases. They are design inputs. Ignoring them produces software that looks modern and fails quietly.

I am interested in technology that compounds: codebases that can absorb change without becoming opaque, products that remain operable under real conditions, and engineering practices that prefer clarity over cleverness. Speed matters. Durability matters more.

Cadmus is a company that builds from Albania. The technical standard we hold ourselves to should be indistinguishable from the standard we would hold anywhere else. That is not a claim about prestige. It is a claim about seriousness.