Abstractions are of course due when time is right. It's difficult to address but imo not be the goal from the get go, to introduce abstractions to a codebase.

Abstractions are of course due when time is right. It's difficult to address but imo not be the goal from the get go, to introduce abstractions to a codebase. There is also a cultural thing around abstractions where inexperienced developers look up to or are fascinated with the complexity of something or someone that brings that to the table. It's also a common feature of certain so called architects, because they probably feel they need to some advanced techniques. The thing is though, that when you have worked with developers or architects that advocates for simple abstractions, and it over time proves that is both efficient and cheap, then you start to doubt complexity in total. Also remember that complexity is often not complex per se, as long as you spend time on breaking that complexity down. And then you have a better fundamental platform for solving what you need to. Simple code is fast code. And also easier to change.