About
Hey, I’m Lukas! I’m a software engineer based in Germany, and I’m obsessed with automation. I believe that automating repetitive tasks helps avoid making mistakes and frees us up to focus on the more fun stuff (creativity and innovation).
My day job revolves around automating Open Source License Compliance and Security processes. I help development teams to ensure they consider the legal aspects of using Open Source in their projects and that they are aware of the security risks associated with their complex dependency trees. All while making sure that those activities don’t slow down the development process.
But automation doesn’t stop at work! I love applying it to side projects, from web applications to my smart home.
Beyond my day job, I’m a lecturer at the Baden-Wuerttemberg Cooperative State University (DHBW) in Karlsruhe, where I teach Web Engineering. I strive to equip my students with the skills they need to build and deploy modern web applications with confidence.
TypeScript has become my go-to language, though I’m also comfortable with Go and C#. While I used to work extensively with Python and C#, recent projects have me primarily focused on TypeScript (~90 %) and Go (~10 %). Next.js is my framework of choice for building web applications, but I also have experience with Angular and React. I’m constantly exploring different deployment strategies, from the granular control of Kubernetes (which I find particularly valuable for learning and experimentation) to the streamlined scalability of serverless platforms like AWS, Azure, and Cloudflare. Ultimately, understanding the strengths and weaknesses of each approach is key to building robust and efficient applications.
This blog is my digital playground where I (infrequently) share my automation adventures, web development experiments, and the lessons I’ve learned along the way.
My core beliefs about software development and Open Source
This section is a small collection of thoughts that shape my approach to software development in general.
- Software can never be 100% secure
- Open Source is not inherently less secore or more secure than other software
- Using Open Source is not free of costs
- Object oriented programming is not the best paradigm for most problems (The same is true for all other paradigms)
- Good software engineers need to learn continuously
- High quality, secure software is not a achievable end goal, but a continuous process