Have you ever thought about it: currently, junior developers are being thrown out because the AI can develop better. Senior developers are then only supposed to monitor the AI results….
๐๐๐ฟ๐๐ณ๐ฟ๐ถ๐๐๐ถ๐ด – ๐ฒ๐ณ๐ณ๐ถ๐๐ถ๐ฒ๐ป๐, ๐ต๐ผ๐ต๐ฒ๐ ๐๐ถ๐ป๐๐ฝ๐ฎ๐ฟ๐ฝ๐ผ๐๐ฒ๐ป๐๐ถ๐ฎ๐น, ๐ช๐ฒ๐๐๐ฏ๐ฒ๐๐ฒ๐ฟ๐ฏ๐๐๐ผ๐ฟ๐๐ฒ๐ถ๐น.
๐๐ฏ๐ฒ๐ฟ ๐๐ฎ๐ ๐ฑ๐ฎ๐ป๐ป….? We are cutting our own qualification chain. After all, if we no longer train junior developers, how are future senior developers supposed to grow up?
This example can currently be applied to many industries: marketing, consulting, project management, and many more.
Such quick fixes are often taken by top management because they promise very short-term results / savings / benefits. However, the long-term effects are forgotten.
๐๐ป ๐ฑ๐ฒ๐ฟ ๐๐ป๐ณ๐ผ๐ฟ๐บ๐ฎ๐๐ถ๐ธ ๐ต๐ฎ๐ฏ๐ฒ๐ป ๐๐ถ๐ฟ ๐ฑ๐ฎ๐ ๐ง๐ต๐ฒ๐บ๐ฎ ๐๐ป๐ผ๐-๐๐ผ๐-๐ง๐ฟ๐ฎ๐ป๐๐ณ๐ฒ๐ฟ, ๐ข๐ป๐ฏ๐ผ๐ฎ๐ฟ๐ฑ๐ถ๐ป๐ด, ๐ช๐ถ๐๐๐ฒ๐ป๐๐ธ๐ผ๐ป๐๐ฒ๐ฟ๐๐ถ๐ฒ๐ฟ๐๐ป๐ด, ๐๐๐ฟ๐ฎ๐๐ฒ๐ด๐ถ๐๐ฐ๐ต๐ฒ๐ ๐๐ป๐ณ๐ผ๐ฟ๐บ๐ฎ๐๐ถ๐ผ๐ป๐- ๐๐ป๐ฑ ๐ช๐ถ๐๐๐ฒ๐ป๐๐บ๐ฎ๐ป๐ฎ๐ด๐ฒ๐บ๐ฒ๐ป๐ ๐๐ฐ๐ต๐ผ๐ป ๐๐ฒ๐ถ๐ ๐๐ฎ๐ต๐ฟ๐ฒ๐ป ๐ถ๐บ ๐๐ผ๐ธ๐๐. ๐ช๐ถ๐ฒ ๐๐ถ๐ฟ ๐ฒ๐ ๐ฎ๐น๐๐ผ ๐๐ฐ๐ต๐ฎ๐ณ๐ณ๐ฒ๐ป, ๐ช๐ถ๐๐๐ฒ๐ป ๐ถ๐ป ๐จ๐ป๐๐ฒ๐ฟ๐ป๐ฒ๐ต๐บ๐ฒ๐ป ๐๐๐ฟ๐ฎ๐๐ฒ๐ด๐ถ๐๐ฐ๐ต ๐ป๐๐๐๐ฏ๐ฎ๐ฟ ๐๐ ๐บ๐ฎ๐ฐ๐ต๐ฒ๐ป ๐๐ป๐ฑ ๐๐ถ๐ฒ ๐๐ถ๐ฟ ๐ฒ๐ ๐๐ฐ๐ต๐ฎ๐ณ๐ณ๐ฒ๐ป, ๐ฑ๐ฒ๐ป ๐ช๐ถ๐๐๐ฒ๐ป๐๐๐ฟ๐ฎ๐ป๐๐ณ๐ฒ๐ฟ ๐บ๐ถ๐ ๐๐ฅ-๐ฃ๐ฟ๐ผ๐๐ฒ๐๐๐ฒ๐ป ๐๐ ๐๐ป๐๐ฒ๐ฟ๐๐๐ฬ๐๐๐ฒ๐ป.
In my view, this topic will play a key role in the AI context!
๐๐ฎ๐๐๐ฒ๐ป ๐ฆ๐ถ๐ฒ ๐๐ป๐ ๐ฑ๐ฎ๐ฟ๐ฎ๐ป ๐ฎ๐ฟ๐ฏ๐ฒ๐ถ๐๐ฒ๐ป, ๐ฑ๐ฎ๐๐ ๐๐ถ๐ฟ ๐ฑ๐๐ฟ๐ฐ๐ต ๐ธ๐๐ฟ๐๐ณ๐ฟ๐ถ๐๐๐ถ๐ด๐ฒ ๐ฆ๐ฐ๐ต๐ป๐ฒ๐น๐น๐๐ฐ๐ต๐ฬ๐๐๐ฒ ๐ฑ๐ถ๐ฒ ๐๐๐ฟ๐ฎ๐๐ฒ๐ด๐ถ๐๐ฐ๐ต๐ฒ ๐จ๐ป๐๐ฒ๐ฟ๐ป๐ฒ๐ต๐บ๐ฒ๐ป๐๐ฏ๐ฎ๐๐ถ๐ ๐ป๐ถ๐ฐ๐ต๐ ๐ด๐ฒ๐ณ๐ฎฬ๐ต๐ฟ๐ฑ๐ฒ๐ป.
Using the example from above: Junior developers must learn to both prompt and develop “with” AI. However, they must still be able to build up know-how in order to be able to evaluate AI results later on. Even if the understanding of roles in the development process will change fundamentally, experience cannot be replaced. And…
๐๐ฟ๐ณ๐ฎ๐ต๐ฟ๐๐ป๐ด ๐น๐ฎฬ๐๐๐ ๐๐ถ๐ฐ๐ต ๐ป๐๐ป๐บ๐ฎ๐น ๐ป๐ถ๐ฐ๐ต๐ ๐ฝ๐ฟ๐ผ๐บ๐ฝ๐๐ฒ๐ป…
Hashtag#informatikersindcool Hashtag#knowledgemanagement Hashtag#despiteandbecauseofki
