blog

Should we really forget efficiency? No. But we should postpone focusing on efficiency until we are effective.

In the previous post, we explored why we need to be a bit rebellious to take the road towards becoming a “full-range engineer”.

In the previous post, we discussed what it needs to become a “full-range engineer” and have seen that this is quite different from what software engineers often strive for today. However, the idea of a full-range engineer is focused on creating more value in a highly complex, uncertain and ambiguous environment and thus also improving our value.

In the previous post, we examined how the omnipresent hyper-specialization in IT pushes software engineers into areas of human weaknesses and how nerd culture (involuntarily) reinforces the push. We also collected a little list of ideas how we can position ourselves as software engineers, aligned with humans strengths, preserving our value as software engineers in the face of modern AI solutions.

In the previous post, we discussed what humans and AI solutions are (not) good at and have learned the strengths and weaknesses of humans and modern AI solutions basically complement each other. We have also seen that software engineers often do not leverage their human strengths. Instead, they often position themselves in ways that places them in direct competition with the strengths of AI solutions.