We at punkt.de therefore decided early on that we would not only use the DevOps approach for ourselves, but also actively work on it and "develop for development". The best example: the Codecoon boxes - our latest project. Here, the appropriate development environment with web server, database, PHP and TYPO3 comes fully configured in one package. The fact that it is possible to work mobile without a server connection - a small advantage in passing. What infrastructure virtualization or the increasing automation in the configuration and operation of systems is really about is being able to integrate software into running processes more quickly. It's about quality, transparency and ultimately efficiency, which has a positive impact on costs. This can rarely be experienced more convincingly than when eight or more hours suddenly become 15 minutes to set up a new developer laptop. Saving time is one thing, but the other positive result for us is less susceptibility to errors thanks to automated steps that are "cast in code".

Speaking of saving time: for us, development for development also means sharing our knowledge with others - for example, when it comes to practical solutions for delivering locally developed software to a server. This can sometimes be very time-consuming and complex. It's quicker and easier with our tried-and-tested deployment and five to six lines in the configuration file... Then just "press a button" in Jenkins - et voilá. Time saved again.