Victor, I don't think that you've quite got what Fred Brooks was trying to explain. Your example has nothing to do with what Brooks was saying. You used an (internally) complex tool to construct your solution. That was the smart thing to do. It is one of the ways we manage the complexity that Brooks discusses.

Someone wrote that tool and solved the technical problems necessary to build it. They provided you with tools and APIs that abstract the underlying complexity of the problem, so that you could create an application with much less effort.

That has absolutely nothing to do with the essential complexity Brooks is discussing. Brooks led the development of the IBM System/360 and its operating system. That operating system abstracted the hardware and operating software so that others could use it to build and execute the applications they needed. Brooks well-understood abstraction as a tool for managing complexity. He also knew it had limits.

You might want to take a look at The Mythical Man Month if you haven't already read it. (The Mythical Man Month on Amazon))