I'm not sure what the product is that you're building or how complex it is, but my sense is that maybe you're trying to start too big. You may be passionate ab

I'm not sure what the product is that you're building or how complex it is, but my sense is that maybe you're trying to start too big. You may be passionate about it, but if you don't have the skills to contribute, setting the goal of contributing to that product without any intermediary wins is guaranteed to demotivate. Put another way, lets say your business is an automotive repair shop, but you're not a mechanic. You are passionate about fixing cars and work with a bunch of people who are really talented at fixing cars so you want to jump right in. If your first task is to repair the inner workings of a combustion engine, you're going to give up before you even start. Start by learning how to work a wrench and change tires. Assuming you are truly passionate about fixing cars, completing this simple task will provide you with an emotional reward. Move to something slightly more complicated that will require you to learn something else. It's not a perfect analogy -- you could ask a 100 developers what wrench to pick up and get 100 different answers ranging in complexity, power and learning curve -- but the idea is to avoid tasks that have a huge up-front learning curve that would result in demoralization and disinterest.