> I started to become interested in programming around late 90s and I don't remember anyone floating the idea that OOP, libraries or IDEs will make programming obsolete as a profession.
The version of this hype that I remember from circa 2004 was UML[1] was going to make most programming automated. You'd have an architect that would draw out your problem's architecture in a GUI[2], press a button to automate all the code to build that architecture, and have a programmer fill in a couple dozen lines of business logic. Boom, program done by two or three people in a couple weeks, let's all go home. It uh, didn't work out that way.
You can read a lot more about all this by following the various links to concepts & products from Rational's Wikipedia page, https://en.wikipedia.org/wiki/Rational_Software (the Rational Unified Process page in particular brings back some memories). It wasn't badly intentioned, but it was a bit of a phase that the industry went through that ultimately didn't work out.
[1] https://en.wikipedia.org/wiki/UML
[2] https://en.wikipedia.org/wiki/File:Component-based-Software-...
It's interesting that even with the rise of transformers, UML still isn't popular. I wonder if that, or some other visual way of representing specs, might make a comeback.