Design
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.
This blog post is about an observation I made pondering the slow adoption rates of several technologies in IT that I consider being game changers. My claim is:
Probably you also heard it several times before. Someone comes along saying that IT is a young and immature domain. That we are not yet an engineering discipline. That the way we write code sucks: Slow, not enough throughput, error-prone, not easily repeatable.
API design is a huge topic these days and you find a lot of information about how to design good APIs. Unfortunately, most of it is about tools or technology: Use Tool X for great APIs! Use technology Y and everything will be fine!