An interview with
Andre Bahrdt | Software Dept. Head
„The past is written, but we are left to write the future.“
– Jean-Luc Picard
1) What is your role at Plasmion?
I have been with Plasmion since April 2023, serving as the Head of Software Development. In this role, I provide support and guidance to our management and customers. My responsibilities include analyzing planned processes and developing solutions that seamlessly align with the needs of both parties. Additionally, assisting colleagues with technical challenges is also a part of my role.
2) What skills are particularly valuable for your work at Plasmion?
Distinguishing between small and large-scale solutions is a valuable skill in this position. It is equally important to maintain a perspective on the „big picture“ when implementing any solution. As a developer, the focus should always be on providing a practical solution for the customer—one that supports them without overwhelming them with unnecessary complexity.
3) Why did you choose Plasmion as an employer?
Plasmion seeks simple and easy solutions for its customers, and these are the same goals I aim to achieve with my software. The opportunity to „think outside the box“ with Plasmion’s products and research, diving into undiscovered realms of our world, sparked my interest and motivated me to join the team. I am excited to be part of this journey.
4) What’s the biggest misconception people outside the field have about software development?
That software, automation, or even AI can magically solve every problem quickly and easily. In reality, software development is more of a support for processes and/or users. But that only works if you really understand and question what you’re doing in the first place. Otherwise, you’re just doing the same thing, only on a computer instead of on paper.
5) Looking back, which technical decision causes you the most headaches today?
Honestly, none. Every decision made sense at the time it was made. What matters more is leaving room to revise decisions later if needed, that way you avoid future headaches.
6) How often do you have to compromise on code quality to meet deadlines or other demands?
It really depends on the situation and how well you communicate. Sometimes you just throw something together quickly because it’s only needed once. In those cases, you don’t have to hold it to the same standard as a product you’re selling. It comes down to communication and weighing costs and benefits, and often there’s a way to balance both sides so everyone’s satisfied.
7) What common practice in software development would you most like to get rid of?
The tendency to think only within your own little box. There are lots of experts in specific fields or technologies, but they often stop right at the edge of their specialty. Looking beyond, collaborating or even just taking a peek at what others are doing, is avoided. And that creates friction and problems that don’t really need to exist.
8) If you could run a software project with no time or budget constraints, what would it look like?
Projects like that really depend on the passion and curiosity of the people involved. Without that, they tend to lose direction and fizzle out. Personally, I actually enjoy the challenge of working within constraints. Trying to deliver something within a set budget or deadline, while still holding onto your own quality standards, is where I find the work most exciting.