ANJUNAR / ABOUT

The personbehind Anjunar.

I want to understand how things connect. That applies to software as much as to life.

In software development, this becomes architecture: recognising connections, dividing responsibility sensibly and turning many individual parts into something that works as a whole. On a personal level, it becomes the question of how thinking, acting and one's own values come together.

Anjunar is the place where these interests meet. This is where I develop software, share my work and turn ideas into concrete projects.

01

My path

My career has taken me to Lufthansa and Portrix, among others. Working in industry shaped my understanding of software: a system does not only have to convince on paper. It has to prove itself in everyday use, cope with change and remain understandable for the people who work with it.

My time at Portrix was particularly formative. There I learned a great deal about how complex applications grow – and which decisions make their further development easier or harder. Not only from what worked well, but also from what later turned out to be cumbersome.

Over the years, these experiences have grown into my own idea of software architecture. I want to build systems whose connections can be followed and where a small change does not cause surprises in five other places.

Today, this experience flows into my own frameworks and into the development of individual web applications.

02

Why Anjunar exists

Not every project should have to start from scratch. At the same time, a shared technical foundation should not mean that every application ends up looking the same or has the same limits.

With Anjunar, I work on reusable building blocks that fit together and still remain independent. They include Scala.js UI for user interfaces, the Hibernate DDL Manager for evolving database schemas and the JSON Mapper for working with existing domain models. The projects are open source and accessible through this website.

For me, these tools are not an end in themselves. They are meant to make room for the actual task: developing an application that fits its purpose.

That can be a complex platform, but just as well a website for a DJ, a freelancer or a local business. The technical scope differs. The question behind it stays the same: what does this person really need – and how can it be built sensibly?

03

My philosophy

Besides technology, I am drawn to philosophy, consciousness and the question of how we perceive the world.

I think it matters to be able to consider different perspectives without committing to one too quickly. Taking a thought seriously does not mean I have to accept it as truth straight away. Nor do I want to dismiss a thought just because it is unfamiliar.

This openness also shapes how I engage with philosophical and spiritual traditions. I am less interested in which school turns out to be right than in what they help me understand and what I can test in my own life.

The connection to everyday life is important to me. A conviction may sound beautiful: what counts for me is how it shows in the way I treat other people and in my own decisions.

I want what I think, what I say and what I do to fit together as closely as possible.

I do not see this as a state I have reached, but as a task I keep learning from.

04

Work is love made visible

I understand the idea that “work is love made visible” in a very practical way.

To me, it means being attentive. Listening before I propose a solution. Doing a thing carefully, even where nobody is looking. And taking responsibility for what I bring into the world.

In software, this sometimes shows in inconspicuous details: an understandable error message, a form that asks no unnecessary questions, or a structure another developer can still follow later on.

Not all of it is noticed right away. Still, it makes a difference.

For me, good work is therefore more than a functioning result. It is also a form of appreciation for the people who use, maintain or build on that result.

05

Working as equals

For me, a project starts with a conversation, not with a list of technologies.

  • What do you want to achieve?
  • What have you been missing so far?
  • What should become easier?
  • And what might you not need at all?

I want to understand before I build. That includes questioning an idea or suggesting a smaller solution when it serves the task better.

Clear agreements, fair terms and direct communication matter to me. You do not need to know any technical jargon to work with me. My job is to make the options understandable and to find a suitable direction together with you.

I bring the technical experience. You know your project and the people it is meant for. A good solution comes from both.

Person to person

Let's build something meaningful.

Do you have an idea for a website or application, a question about my projects, or would you like to talk about software architecture?

I look forward to a conversation – person to person.

Built carefully with Scala JS UI.Imprint