What is important as a software developer

Profession as
Software developer

Contrary to the cliché, in your job as a software developer you won't be sitting alone in a dark basement. You should feel like talking shop with others during your lunch break about whether there is an open source jquery plug-in for the problem or whether Java has "broken" object-oriented programming. Because even if there will be one or the other night shift where you forget the world around you with headphones in your ears, as a developer you are dependent on your colleagues on site and on specialist forums on the Internet. Although you write code for yourself, your day-to-day work consists of meetings and teamwork as well. You speak regularly with your project manager, the Q&A department, designers and sales to incorporate their feedback and wishes into your work. You won't have to deal with clients as often, but that too can happen, depending on the size of the company or agency that employs you and how much project management is expected of you. Often, for example, you have to help customer service with technical questions and answer support inquiries.

During your studies you will have already determined whether you are more of the "quick and dirty" type or whether you tend to think of the bigger picture when programming. In your day-to-day work you will, on the one hand, take care of development in the traditional way, but on the other hand, you will also take care of the software architecture and documentation. Technical design documents need to be written and internal wikis need to be maintained. Sometimes you even have to do design tasks and create elements of the GUI (Graphical User Interface).

Anyone who now thinks that they think most of the day in their job as a software developer and can program with a plan should do an internship before starting their career. You will have to put a lot of brainwash (and coffee or energy drinks) into fixing mistakes. It can well happen that you are currently working on a feature and then some bug fix urgently needs to be done because the main customer has problems. This is where you need patience: It is important to reproduce, find and fix the bug as quickly as possible without causing further errors. And sometimes that's not that easy, because all too often you have to understand the incompletely commented code of your colleagues. Those who have a high tolerance for frustration and don't get upset about other people's code so quickly have a much more relaxed job. Just see it the way it is: not everyone has your skills and they are difficult to replace.

In small teams, you can slip into the role of internal quality assurance at short notice if there is no in-house tester. After all, before a new software version is released, it must be ensured that everything works.

Overtime is the order of the day when something needs to be finished. Depending on how project management works in the company, you may have to commit to certain features and time frames. You will hardly find a software developer who, when he comes close to solving a problem, simply goes home and switches off. As a programmer, you know that nothing is more rewarding than software that works exactly as it should. It's just a good feeling to be able to create something that works completely from nothing. A bit like Lego for adults.