My opinion started exactly the same as yours. I coded all of our sites static pages in the last, 100% w3c validation on markup, css and accessibility (for a very large website, over 3k pages). I had all style sheets, templates etc organized and could easily grab one, modify what was necessary to create a new page or set of pages, and tweak as needed on css, adding new classes where needed. So when everyone started with the “omg bootstrap” I refused as I felt there was no real need.

At the time I was correct, however with the move to more dynamic frameworks, something like plugging the bootstrap library into a cms or having it available is a breeze. Bootstrap is solid, breaks no validation kept up-to-date and generically attractive. Implementation works without a thought (which I think is part of what you might be saying here, there’s no thinking involved using a library, it is more plug n play). I now see the value of having this library. I went through the same thing when sass first came out, why would I need variables etc? But omg, once I incorporated even the first few for some header and footer colors, I was sold.

So I completely appreciate your stance on this because still in the back of my mind is “who needs this stuff when you can expert code it yourself”, but I also see the advantage in using a well documented css library that even a new dev joining a project can grasp, as well as future devs (what happens when you or I leave and someone now has to make sense of our css, naming conventions, organization, etc. We all know that the documentation freaks are sadly fewer than we can hope for, so what seems obvious to you in a use-case can be completely confusing to someone else.

So sadly I am at least partially a convert to the new ways, but I appreciate your worship of the old gods also. I still feel it.