Simon, what does a backend developer actually do?
A backend developer writes programs that run in the background and that you don’t see directly. But that doesn’t mean these programs are less important – quite the contrary: backend applications bundle the logic that the user interface can then simply access. Depending on the project and task, this also includes setting up and querying databases, which also run in the backend. Often there’s also a pinch of system administration involved, as you also manage the servers on which the written applications run to a certain degree. The functionalities in the backend can be implemented with a variety of programming languages. Examples here are Java, C#, Python, PHP or increasingly Golang. These programs offer API interfaces for the frontend and, if well programmed, can be used for a variety of frontend solutions. For example, an app can use the same backend functionality as a website, without investing the great effort of complete logic programming.
Why do you focus on backend development?
Designing algorithms is like solving puzzles for me. I enjoy thinking about a problem and designing a logic for it. When you finally start the program after hours of puzzling and everything runs smoothly, it feels great. Because the individual projects are always different and the languages used also vary, you have a lot of variety and there’s never a dull moment.
Who is suited for specializing in the backend?
As a backend developer, you should have a certain affinity for mathematics, even if you rarely calculate. However, the algorithmic thinking you learn from it is very important for programming in the backend. Enjoying solving complex, logical problems is also advantageous. From time to time, a certain resistance to frustration also helps, as problems cannot always be solved quickly and at the first attempt. Having an interest in computers is certainly also beneficial. While it’s not absolutely necessary to be familiar with the latest hardware, you should at least know and understand how the machine you’re working on functions.
“Designing algorithms is like solving puzzles for me. I enjoy thinking about a problem and designing a logic for it.”
Simon Brunner
And what does a frontend developer do, Johannes?
The frontend is, simply put, the visible part of a website or web application – in contrast to the backend, which focuses on the server-side part. The frontend developer programs the user interface and the connection to the backend, which then allows the frontend to retrieve needed data from the server. Since websites or web apps are also often accessed from smartphones and tablets, a responsive design is also often expected, which displays the application optimized for the respective devices. Technologies such as HTML, CSS, and JavaScript are used, including popular extensions of the JavaScript programming language such as the React library or the Angular framework. Generally, a fairly broad knowledge of various technologies is needed for web development.
Why did you specialize in the frontend?
My motivation for studying computer science stemmed from a passion for UI, design, and technology. I’m fascinated by offering users the best possible and intuitive solutions that, ideally, are also fun to use, following the motto ‘Don’t make me think’. The result of frontend development is usually visible to the developer themselves, as well as to the user, so you often receive feedback on your work. Whether it’s design or code, it’s incredibly fun to build a project from the ground up, focusing on architecture, maintainability, and clean implementation, or expanding the website with new pages/views or features within the framework of the conceived UI.
What skills and interests should one have for working as a frontend developer?
Frontend development requires a range of creativity and analytical thinking. Very important is also good communication skills and interpersonal empathy to put oneself in the position of customers or users. After all, a good frontend should be easily accessible to everyone, not just the developer who juggles ones and zeros daily. Additionally, one should bring a willingness to learn and interest in technologies, as these are continuously evolving.
“My motivation for studying computer science stemmed from a passion for UI, design, and technology. I’m fascinated by offering users the best possible and intuitive solutions.”
Johannes Pfleghar
What tasks does a full-stack developer take on, Tillman?
The full-stack developer combines both backend and frontend know-how. He is, so to speak, the Swiss Army knife among developers. As the person who understands both sides, he usually moves somewhere between backend and frontend in development. He designs and develops interfaces between backend and frontend and is in exchange with the respective developers on how to best conceptually solve arising conflicts. In case of bottlenecks, he can be a floater and help out any team.
Why did you choose the profession of a full-stack developer?
As a full-stack developer, you get to see a lot. I can follow the development of the entire application and don’t just work for myself in my small area. It motivates me to always keep the big picture in mind. Also, the tasks are very diverse, and you always have something different to do.
Who is suited for the profession of a full-stack developer?
Since you work in both backend and frontend, you should also bring the skills of the respective fields. This means both logical and analytical thinking as well as a sense for design and usability. Conceptual skills should also be present. More than other developers, you must be able to rely on your soft skills for communication and mediation.
“As a full-stack developer, you get to see a lot. I can follow the development of the entire application and don’t just work for myself in my small area.”
Tillman Rossa
Backend good, everything good?
As we now know, a good website or web app is made up of the various puzzle pieces of frontend and backend, whose good interplay is essential. The frontend can be as intuitive and beautiful as possible, but if the right data isn’t displayed, a backend can be as well thought out as possible, but if the user can’t find the data. Since the boundaries between both worlds are often fluid, it’s advantageous to bring knowledge from both areas. Many thanks to our developers for the insights into their areas of expertise.
