About Me

Why roestzwiee?

It translates to 'roasted onion' — a nod to my legacy handle in the gaming world, where I just roasted what I found. For now my mission is to add a little extra flavor to the web.

Philosophy

Technology is my passion, both at work and in my private life. I believe it encompasses much more than just software for PCs and smartphones. We require software for vehicles, household appliances, and robotics. We are living in an unprecedented era for humanity as whatever we do, software is involved and soon, AI will be too. Therefore my Philosophy is to create software that is secure, reliable.

Working with AI

Since the release of ChatGPT and similar tools in end 2022, AI is developing at a fast pace. This creates risks and opportunities alike.

For me as a Developer its important to know and understand the code I'm writing. AI can be a great tool to speed up development, but I always double check the results and never blindly trust them.

For me as a private person AI does provide help in content creation but also help when searching for an idea or learning something new. Beside the fact that everything an AI provides you needs to be double checked for correctness, I strongly believe to consider the value of self written content over AI generated content.

Whilst AI can drastically simplify our everyday life, AI will never bear responsibility on the actions I'm doing. It is therefore mandatory to not forget to practice our skills and sometimes just put AI aside.

Coding Principles

No matter where or what you code, it's important to follow the SOLID principles. SOLID comes from Robert C. Martin and stands for five principles that help write clean and maintainable code. These principles are:

  • Single Responsibility Principle – Each class should have only one responsibility.
  • Open/Closed Principle – Open for extension, closed for modification.
  • Liskov Substitution Principle – Subclasses must be substitutable for their base classes.
  • Interface Segregation Principle – Many specific interfaces instead of one large one.
  • Dependency Inversion Principle – Depend on abstractions, not concrete classes.

It's also always important not to overshoot the goal: Stay short, stay clean, and code only what is necessary.

This is where these principles help:

  • YAGNI – You Ain't Gonna Need It: Only implement features you actually need.
  • DRY – Don't Repeat Yourself: Avoid code duplication through reuse.
  • KISS – Keep It Simple, Stupid: Keep the code as simple as possible.

Interest in Ethical Hacking and Data Protection

The GDPR is one of the greatest achievements of our European society. While it often causes frustration for clubs, businesses, website owners, and retailers, for us software developers, it should spark something else: genuine interest.

Our data and our online behavior—especially in e-commerce—are incredibly valuable to large corporations. However, if poorly secured, this data becomes a goldmine for cybercriminals as well. Today, it might be credit card numbers; tomorrow, as digitalization progresses, it will be vehicle registrations or sensitive health records used for malicious purposes.

Even though the bureaucratic side of GDPR seems like a heavy burden for many small businesses, maintaining a secure IT infrastructure is absolutely critical. To me, Cybersecurity is one of the most vital growth areas—not just within software development, but as a comprehensive full-stack approach across a company's entire IT landscape.

To truly understand how attackers think and operate, I spend my free time sharpening my skills on platforms like Hack The Box.