The AI automation paradox: between a flood of output and the search for meaning

The scenario: A team of developers is tasked with expanding a software programme’s user management system. An AI assistant generates the necessary code within a few minutes, adds tests and suggests changes to the database. What would previously have taken several working days appears to be completed in a single morning.

But then the real work begins: Does the proposed solution fit in with the existing architecture? Do the automatically generated tests also cover permission conflicts and unusual usage scenarios? Is personal data being processed correctly? Will this result in a solution that works in the short term but incurs high maintenance costs later on? And does the new feature actually solve the users’ problem? 

This is precisely where the automation paradox lies: AI takes a large part of the code-writing work off the team’s hands, but does not automatically reduce their workload. Instead, the volume of results that need to be checked and accounted for increases. The focus of the work shifts from production to assessment. The more powerful automation becomes, the more important human skills – ‘future skills’ – become, as these cannot simply be automated.

These ‘future skills’ determine the value of AI-generated code 

Systemic and entrepreneurial thinking: Systemic thinking looks beyond the individual ticket. Developers must recognise how a change interacts with role models, data protection, support processes, business logic and other components.  

Architectural judgement: AI can generate code, but does not automatically know all the decisions that have evolved within a software system. Development teams must be able to assess whether a solution is secure, extensible and comprehensible. 

Ability to navigate uncertainty: Not every AI-generated suggestion can be scrutinised with the same level of rigour. Teams must therefore make decisions based on risk. The ability to navigate uncertainty means identifying critical points at an early stage, selecting appropriate verification methods and making uncertainty visible.  

Reflection and decision-making competence: AI quickly provides plausible answers. It is precisely this plausibility that can lead to proposals being accepted without scrutiny. Developers must therefore be able to distinguish between: 

• technically feasible, 
• functionally viable in the short term, 
• technically sound, 
• justifiable in the long term. 

Making this distinction requires experience, self-reflection and a willingness to challenge a seemingly ready-made solution.  

Psychological resilience and a new team culture: the automation paradox also affects one’s professional self-image. Those who have hitherto associated quality primarily with code they have written themselves may experience this change in role as a loss. Psychological resilience must therefore not be seen as a private matter for individuals alone. Teams need clear quality standards, transparent responsibilities and an open approach to uncertainty.

What needs to change in initial and continuing education 

A basic technical understanding remains essential. If you do not understand code, you cannot reliably assess its quality. However, simply writing code is no longer sufficient as an educational objective. 

In future, learners will need to work more frequently with incomplete, ambiguous and potentially flawed solutions. Rather than simply implementing a given task correctly, they should learn to question requirements, prioritise risks, justify architectural decisions and evaluate the impact of a solution. 

For Dresden University of Applied Sciences, this development is part of a wider question: what skills do graduates need in a world of work shaped by AI, digitalisation and constant change? At the Dies Academicus 2026, students, academic staff and industry partners discussed, amongst other things, future skills, examinations in the age of AI and the employability of tomorrow. The findings form the basis for a university-wide development process on the future of study and teaching.  

Practical relevance is crucial here. Insights from regional businesses can highlight the decisions that development teams actually have to make and where new pressures are emerging. Dresden University of Applied Sciences explicitly links research and teaching with application-oriented knowledge transfer and the challenges of social and technological change.  

Join the discussion now at Brains on Silicon 2026 

Prof. Dr Marius Brade and Manja Unger-Büttner will be speaking at Brains on Silicon 2026 on the panel ‘Between a flood of output and the search for meaning – what skills development teams need today’ (16:00–16:25, Stage 3). 

The audience will be involved in the discussion and can use a QR code to contribute their own observations, challenges and further ‘pieces of the puzzle’. The results are intended to provide impetus for new skills profiles and a joint educational initiative. 

Brains on Silicon 2026 will take place on 14 and 15 September 2026 at the International Congress Centre Dresden. Under the theme ‘Closing the implementation gap’, this B2B conference on applied AI focuses on the transition from piloting to practical implementation. 

Tickets are available at https://brainsonsilicon.com/