He likes tough challenges, regardless of whether he is building banking applications or brewing homemade beer. He is also convinced that open source and openness is what drives technological development forward. Meet Daniel Pfeifer, one of our sharp developers.
Daniel Pfeifer is a system developer and Principal Consultant for RedBridge' Development Department. He was born in Germany but has lived in Sweden for the past 16 years.
According to Stefan Andersson, CEO of RedBridge, Daniel is a person who stays on top of all technical changes in the IT industry with great joy and action. He lands every project that he starts, even if the challenges are sometimes very tough. In addition, he is always there for his colleagues and is happy to help others find solutions to difficult issues.
RedBridge's developers work primarily with large, complex software systems, often in the Java programming language. A key area is to streamline customers' most important processes with smart technical innovations. One example is Scania's research and development department. Here, Daniel and his colleagues have created a tool for collecting and analyzing vast amounts of information from Scania's tests of truck prototypes. The tool facilitates the work of employees at Scania every day and these are the results that are the most rewarding, says Daniel and adds: Especially when we build solutions that we know our customers will be able to use for a long time to come, that feels feels good.
RedBridge system developers have historically helped customers in particular within banking and insurance. They identified the first mobile apps for a bank that is now used daily by the bank's customers. For another bank, we moved the entire development and operations platform into a separate cloud with new development methods like DevOps and CI / CD (continuous integration / continuous delivery & deployment). Aside from the fact that the services are meant to improve the experience for our customers customer, it is also often about building smart Java applications that make the client's own developers think it's fun to work, says Daniel.
The choice to work with open source is not only important to Daniel. This is the way of thinking on which RedBridge is based. Open source contributes to society's technological development. The opportunity to see what other smart people have done and thought, and the platform to contribute and share, is constantly improving, he explains and continues:
With openness there is the possibility of working in a way that's more standardized and cost-effective. Additionally, you do not get locked into an expesive ecosystem depending on any single provider. In the long run, it is good for the customer and well invested money.
Daniel has seen many organisations build temselves into a corner by purchasing proprietary solutions that are difficult to get out of. You might be paying big money only for support and maintenance because there is no source code to look at. In the end, if you're not happy with how a closed system works, the only alternative is to switch to a whole new system.
In addition, most developers think it's fun working with open source. Both for the freedom and for the chance to contribute to a broader context and the whole of community. By choosing transparency, it is easier to attract the best employees. So how do you fit in at RedBridge? Daniel answers: Driven people who want to share the knowledge they have and who like to listen to what others have to say. Because when everyone learns a lot, we move forward together.
When Daniel is not solving challenging problems at work, he takes care of his children of 3 and 5 years. But it also happens that you find him coding his own, smaller projects on the side. When he is not brewing his own beer, of course. His hobby may not be all that surprising when you know that he is born in Germany, one of the beer strongholds of the world.
Stefan Andersson thinks Daniel's beer brewing reflects how he works. He is curious and is not afraid to try new things. He discards of the methods that do not work well and stick with what is working. This leades to him finding new flavors that others would have missed, allowing him to deliver something out of the ordinary.
Once the source code is open, anyone can see how a product or solution is built, and use the code and change it to develop custom variants. Anyone who wants to can learn how the product is built all the way down to the core and even improve it. This is one of the major benefits of open source: when everyone can read and review the code, bugs and errors can be easily found and fixed. Around open source, large communities are often created by developers who can share experiences and disseminate suggestions for improvements. The opposite is called a proprietary solution, a product that you buy from, for example, Microsoft or IBM. If you invest in such a product and the owner of the product decides to shut it down, you have to change your product no matter how many hours you have invested to make it work in your business. Examples of open source products are Firefox, Linux operating system, Android mobile operating system, and the Java programming platform.
Unlike open source, open standards are not software, but rules and documents which govern how something should be built and function. Examples of open standards are HTML and TCP / IP, published by the World Wide Web Consortium (W3C) and Internet Engineering Task Force (IETF) organizations. Both of these standards are basic building blocks for the Internet. They control how we build websites and how they work and communicate with each other. Java EE / Jakarta EE is also an open standard that has enabled many Java applications to live for a long time, regardless of which provider have been chosen to run the app.