In the previous post of this blog series we discussed the assembly line fallacy, the misconception that software development is the same as building a car and learned that software development is part of the design, not the construction.

The current AI hype is accompanied with a lot of predictions that software development will be taken over by AI solutions soon and most software developers will lose their jobs together with most other white collar workers. While I agree that AI solutions will have a significant impact on software development, I disagree with the notion that software development will be taken over by AI solutions anytime soon.

Recently I tried to catch up with the recent developments in platform engineering when I experienced once more a just too familiar déjà vu feeling. During my research, I came across the following definition of platform engineering:

In the first part of this two-part blog post, I explained why I think most job ads today are rather pointless and are not particularly helpful in finding the people you need. Then I discussed some pointers that lead the way towards better criteria for job ads and mapped them against the typical job ad of today.

Sometimes I read through job ads and almost always they leave me a bit at a loss. They always ask in a checklist style for some traits and experiences that based on my experience are either rather pointless or not really essential. Or they ask for a very narrow hyper-specialized profile garnished with the usual “you should be team-minded” antidote which is even worse regarding today’s challenges.