How we work
Documentation
Every project needs documentation.
Yet, most developers and development agencies are hesitant to document their work and approach sufficiently.
We understand that a good and comprehensive documentation is necessary for every development work. And we are not afraid to share: eventually, most business that outsource the development of their product want to build up their own development team and take over. We don’t prevent that by making intransparent, unmaintainable work – but embrace it and prepare for that moment from the first moment.
Because the day our customer is successfully taking over with their own development team is not a loss, but a proof of our success!
As every development team, we need to consider between the volume of the documentation and its cost. But, based on best practices, we do the assessment together with our customers, and share our recommendation transparently. You disagree? Let us know!
Our approach
Transparent. Efficient. Reliable.
We don’t make a secret out of our code, but transparently build a solution that you and your team can enjoy.
And work with.
Plan
A transparent planning process builds the base for our DevOps solutions and gives you a clear vision for the project.
Build
Pipelines are building an optimized version of the code at every stage, with every commit. Automatically.
Test
Automated testing ensures a high quality with minimum costs and optimizes development workflow.
Release
Depending on your requirements, we build release versions for every environment - including feature previews for your testers and stakeholders.
Deploy
Once the application is ready to ship, it's being deployed to the appropriate environment - be it feature-related, development, staging or production.
Monitor
During the live operation, the application is being monitored 24/7 by professional tools in a transparent and easy-to-access process.
How do we document?
Code is self-documenting
Our philosophy is: if you need to write inline-documentation, your code is not understandable and should be rewritten.
We generally avoid writing inline documentation, and prefer writing self-documenting code. However, when writing reusable functionality or libraries, we of course do document the API – inline, for autocompletion, and as an external document based on Markdown.
How do we document?
Diagrams for infrastructure
Infrastructure can nowadays become incredibly complex – especially when multiple different clouds or datacenters get involved. A microservice architecture, that can easily add dozens of different services in one product, doesn’t make it easier to understand.
Primary instrument of our infrastructure documentation are architectural diagrams; they provide an easy-to-understand overview over the whole architecture. And we utilize more diagrams for the detailed documentation – and not just walls of text.
Our Tech Stack
We utilize and cooperate with the following technologies and providers to ensure a high-quality experience:
… and more!
