For me, the single most important thing about Open Source is that it means I can solve a problem once and then /never have to solve that problem ever again/ in the future.
So any code I write I like to open source, because that's the best possible way I know of ensuring I won't have to waste time solving that same problem again.
The other thing that helps is that I think I've found a cure for project guilt.
I used to feel guilty about my projects - each one was Yet Another Thing that I should be spending more time on.
The fix I discovered was to make sure every single one of them has good test coverage and comprehensive documentation.
Effectively I treat each one as something which can stand on its own if I effectively abandon it - the thing works, and is documented, and other people can use it as-is without me feeling guilty that I'm not constantly actively working on improving it.
Also, you need practice, write 5 ideas a day. Doesn't matter what ideas, things might exist or not exist. After a while, you will have a pile of garbage with some really good jewels between them.
PS. It was mentioned in the book, I don't recall which one.
I'm pretty sure GCE does the same, just last week I had a need to test something and with 1vCPU instance was ready in about 3-4 mins. Next time will check logs to confirm it. But seems the reasanoble thing to do.
I wonder what's drives you to make so many Py modules? Do you see reusing modules for your own projects or do you have some other grand plan?