Yep. I have found the mantra "Build what you need" works best. Only once you end up having to solve a separate problem that shares common attributes/patterns w

Yep. I have found the mantra "Build what you need" works best. Only once you end up having to solve a separate problem that shares common attributes/patterns with the first should you you extract a common framework and rebuild both on it. You have a proven need and you're not just blindly building "someday this could be used for"-type code.