15+ years of software and system engineering experience.
Everything seems to be impossible until it is done.
The Openstack migration was complete and now it was time to focus on reliability, automation, monitoring, and logging. Focus on improvements for daily operations and recovery.
Soon after my first few months, we realised that I liked to maintain complex systems like a Kubernetes or database cluster. So I moved from the role of a DevOPS engineer to that of a site reliability engineer. The company caught my attention and the product evolved from a proof of concept to an initial prototype. Given the compliance and security requirements, the company decided to move from a public cloud offering to a private cloud deployment. We evaluated the following two offerings: Microsoft's Azure Stack and Openstack. Initially, we migrated from Azure to Azure Stack and finally, after almost a year, to Openstack.
My first task was to design and implement Continuous Deployment and Continuous Integration pipelines for our kubernetes microservices platform. The platform was running in Azure and Travis CI was used as a hosted Continuous Integration service.
The QualityPark company develops, maintains, and customizes the Micro Focus Dimensions RM ( Requirement Management ) solution for enterprise customers. Part of my job was to integrate new features and enhancements into the core Dimensions RM solution. I was responsible for designing, implementing, testing, and integrating Java based components into the core of the Dimensions RM solution. I was the back-end developer on the Java team, along with a front-end developer who did the implementations for the web applications (CSS, HTML, JavaScript). I also did product presentations to clients and provided technical support and feedback.
I literally took time off from my job as a developer and decided to work as an unskilled laborer. This brief career change also helped me with my personal development. It improved my attitude towards hard physical work and also helped me lose some weight.
I worked on the Partner B2C API team. We were responsible for designing and developing an API for the EPost Brief product. The development department was organized according to the Agile Scrum methodology. The release process was done together with the Operations department. The team was responsible for deploying a working Puppet configuration and the rollout was performed by the Operations department.
The company AdClear GmbH was founded in March 2011. In the same month, I was hired as a Senior Java Software Developer to lead the web application development from the beginning. The company had about 8 permanent employees at that time. I already knew most of them from my time at the zanox AG. My job was to design the web application along with the related backend services. Later that year, a frontend developer was hired. He was a fresh student who I brought on board as a mentor.
Hired as a working student to develop a web application using Microsoft C++ based on the cgi interface of IIS 6. Completed the exam and got hired as a Java Software Developer. 2006 - 2010 Migrated core services from a legacy system developed in C/C++ to Java Platform Enterprise Edition. 2010 - 2011 Technical lead of the Public WebServices team to build a highly scalable public REST /SOAP API.
During my studies of Applied Computer Science at the HTW (former FHTW) Berlin I did an internship at the company Total. The project of this internship was the development of an e-commerce like web application for internal use.
I have several years of experience in leading and mentoring people and organizations.
With over 15 years of experience in software development. I have developed a sense of reasonable good and bad architecture. In my opinion, a reasonably good architecture requires that the technical and non-technical requirements are known in advance. In most cases, the communication structure of a company is also reflected in the software/system architecture, especially when it is developed and implemented by multiple teams (Conway's Law).
After reading the book 'Principles' by Ray Dalio. I was inspired to put together my personal working principles.
They have to be valued and earned constantly.
Be clear at the start of a meeting. What is the meeting about and for who ?
Starts with yourself
Don’t repeat over and over the same discussion and conversations. Break repeating cycles they are mostly number one time consumers.
It's all about the ratio of time and outcome.
The number one priority of tools is to help people to be more productive and save time instead of cost time.
If tools are not in line with point a) then drop them or replace them with another tool.
Focus has to be on the people to lead.
Help them to grow.
Be authentic and lead by example.
Don’t expect more from others then from yourself