AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
How to Structure Libraries With Variables
If you're a one-person team, you might not even need to go down to the primitive semantic layer. Primitives arguably don't change that much. Semantics you might need to change very often. Putting them in the same place increases the margin for error of somebody accidentally doing a release on something they shouldn't be doing. As you start to grow as a team, you want to reduce any sort of design-linting problem and to me that means split it up. Just split the stuff up.