作者： Thabo Krick

I help developers and testers of (mostly automotive) embedded systems to catch up and move forward with their testing process. Due to the highly regulated nature of safety critical software development I often encounter technology stacks that are immensely behind the curve. Building a desktop or web application is nothing like building embedded software for a car but that doesn't mean embedded software development must fall behind. Many best practices from other domains can be applied to catch up and move forward. After my degree in computer science & economics one of the first things I did was to familiarize myself with Jenkins. The project's goal was nothing less but to set up a new software factory from scratch. This exciting journey - first for a new software project, later scaled up for all software development departments - made me fall in love head over heels with improving and automating processes, connecting different steps and tools to ultimately create coherent workflows that make life easier for developers and testers. The transformation from a simple one-machine setup to a sophisticated cluster with over 70 agent machines that process millions of lines of Java, Matlab and C code required me to overcome a lot of obstacles. It wasn't always easy but I didn't mind it. Especially now looking back, I feel that struggling is a great teacher and some best practices are best understood if you have first felt the pain of ignoring them. In 2016 I joined the awesome team I'm still working with today. Each with a different background we help developers, testers and their supporting teams by providing software with cutting edge technology to enable them to build safety critical software for embedded systems efficiently with high quality. I focus on connecting different tools. Naturally for continuous delivery pipelines but also to enhance interactive workflows (e.g. requirements based testing) by integrating our products with ALM / PLM solutions.