About — EnBeZ e.K.

company: EnBeZ e.K.
owner: Andreas Zeuch
location: Schauenburg-Elgershausen
experience: 20+ years
reach: across Germany
focus: Software & architecture

Career

I have been working with software for more than 20 years. I started in classic IT consulting, with networks, servers, telecommunications and training. Today my focus is on software and architecture.

How I work

Projects begin with an assessment. I read the code, look at the data and talk to the people who work with it every day. I design only after I understand the system — and the design is usually smaller than the initial request. What is not needed does not go into the system.

During implementation I work in steps that can be verified individually. You see what is emerging as it happens and can intervene while a decision is still open. That is less comfortable than one grand design at the start, but it keeps the project close to operations.

I write decisions down, including the alternatives that were rejected. Whoever takes over later should not have to guess why something was built the way it was.

In collaboration I prefer short paths: a message, a meeting, a decision. Records and open points live where both sides can see them — not in an archive nobody opens.

Why mid-sized companies

Mid-sized companies have projects that are large enough for a purpose-built solution and small enough for a clear scope. The people involved know their operation, and a decision is not split across three committees. That is where software can emerge that arrives in everyday work. It suits a way of working that takes the existing system seriously. A system that is not understood there will not prevail.

After handover

Documentation is part of the finish: structure, operation, open points. Your team gets a walkthrough, and the code is yours. If a question comes up later, it is not an emergency but a task someone can take on — with or without me. The walkthrough is aimed at the people who will operate and maintain the software.

Principles

Responsibility for the whole

I take responsibility not just for a part but for the whole picture: data, interfaces, operations. A component that works on its own but does not carry the whole is not a solution.

Justify decisions

Every significant decision is recorded together with its alternatives. That keeps it clear why a route was chosen — even if assumptions change later.

Documentation is part of the work

I document as I go instead of turning it into a last-minute obligation. The documents are addressed to the people who operate or later take over the system.

Avoid dependencies

The client should be able to take over. That is why code, documents and a walkthrough are part of the result — not as an extra, but as part of the job.

Technology

I work with web technologies, relational databases, interfaces and Linux servers. Which language and which tool are used depends on the project — not on a standard list. Proven tools are preferred as long as they carry the task. The decision is justified within the project, not fixed in advance.

Web
Databases
Interfaces
Linux

Andreas Zeuch