Yeah, unnecessary abstractions are just bloat. Generalizations should be introduced when necessary not when possible. I don’t think your opionion is an outlier

Yeah, unnecessary abstractions are just bloat. Generalizations should be introduced when necessary not when possible. I don’t think your opionion is an outlier among people who have experience in maintaining software. But a lot of teaching make it seem as if abstraction is a goal in itself. A driver for unnecessary abstraction is the idea that “it will be more difficult to abstract later” not realizing over-designing is a cause of this problem in the first place.