We used Twitter Bootstrap on our project for the past half year. In the beginning, it was great for prototyping and showing something in barely no time to the client.

Now we plan to re-design everything, and as the new design doesn't look too much like Bootstrap anymore and we didn't use a lot of functionalities anyway, we are dropping Bootstrap (except a few JS plugins maybe) and roll our own solution with Compass/Sass and maybe some Blueprint mixins.

I translated designers' PSD layouts to pixel perfect HTML/CSS sites for some years now, and as I'm aware of most of the caveats, I feel a lot more productive rolling my own solution for every new project, than using a standardized frameworks that forces me to do things in its way or forces me to alter (rape?) it so it does things my way.

In my opinion, CSS frameworks like Bootstrap are a very nice tool for programmers who want to have a visually nice, standard looking result really fast. But due to the fact that I have very high demands when it comes to aesthetic and semantic design with minimal HTML/CSS code, I found it impossible to work with standard solutions, as every project is unique.

I want my CSS code to do exactly as I want it to do, and ONLY THAT. When there's something new needed, I know exactly where to change my codes and don't have any side effects which inevitable lead to messy spaghetti codes and building site's all over your code in no time - and as soon as this has only begun, you'll never get your code clean again without a complete redesign.

That's my experience. Thanks for this very informative article. You may want to read this other very informative one here: http://css-tricks.com/dont-overthink-it-grids/.

Best wishes.