Understand first, then structure
Software represents part of the real work of a business. Terms, data, responsibilities and workflows therefore need to be understood before a durable technical structure can be created.
ENGINEERING
Technology is good when it reliably serves its purpose.
Architecture, quality and security are not additional services for us. They belong to development, in the measure that the task and risk of a project require.
Architecture with a reason
Architecture is not a goal in itself. It should separate responsibilities clearly, make change possible and prevent a system from becoming unnecessarily hard to operate or develop further.
Quality during development
Tests, typing, reviews and automated checks are integrated into development. Which measures make sense depends on the importance, scope and risk of the software.
Security
Security is not only about login and passwords. Data handling, permissions, dependencies, configuration and deployment are treated as part of the system.
Operation
An application is not finished just because it works locally. Deployment, configuration, error behaviour, maintenance and technical observability are considered where they are necessary for reliable operation.
Continued development
Good technical foundations should make change easier. New features or requirements should not regularly force a complete rebuild.