Thank you for this answer. The truth is that for a long time I felt guilty for deciding to stay tied to engines that did not require knowledge in programming (mainly rpg maker) but with this kind of experiences I see that even so, I have the opportunity to defend with what I know and I have at hand.
On the other hand I'm surprised by so many responses saying "no, working as a team to make a game is the most stressful" because from the outside it doesn't seem the case, like, a bunch of devs talking cool and agreeing to do their dev stuff together. That's not the reality as far as I can see.
Viewing post in Your experiences working in a team
Hah. Even aaa game companies rarely create their own engine. But the engines they use cost real moneys.
Deving together is like making a movie with several directors.
Can be done, but is hard to find directors willing to share the work . Better find dedicated programmer or artist. But professionals usually like to get paid. And non professionals, well, look at the other comments. Good advice there. Or just look at a discussion and changelog of some wikipedia pages. On the surface the strangers work well together, but under the hood, the flame wars and bickering happens ;-)