3 ms·
This is very true. Learning how to say no in a constructive way is hard. Doing it over text is impossible. The contributor obviously is passionate about your pr
by xupybd 4y ago
This is very true. Learning how to say no in a constructive way is hard. Doing it over text is impossible. The contributor obviously is passionate about your project and that is great. You might be able to channel that to work with your vision. The chances are they'd be grateful for some mentorship if that worked for you both. I suspect it might as you'd get more work done on your project and they'd get to improve as a developer.
I would try to let go of your frustrations with this person (easier said than done). If you do that you can try to maximize what you can get out of this. Possibly a life long friend, probably more work on your project.
- verdverm 4y agoHaving been one of those people who wanted to help out another project (https://goa.design https://goa.design) where the vision did not align, I left to build something on my own (https://hofstadter.io https://hofstadter.io) and am having way more fun doing it and there were no hard feelings. It's best to not try to force things when the vision is different, as OP describes it
- xupybd 4y agoYeah that's true. I have a friend that fired all his staff and has never been happier. For him not having to deal with others to get the job done is a much better experience. Personally I've always loved working along side others. Having my ideas challenged and coming up with something other than my own vision. Different people have different preferences I guess.
- verdverm 4y agoLetting go of one individual does not mean you are abandoning teamwork, often you have to because one bad apple will spoil the bunch. If your happiness and excitement are drained by this person, I'd say the choice is pretty clear.
- xupybd 4y agoAlso very true and those projects you linked look very cool. I've not really explored code generation in the past but I'll have to have a look. I like idea. Put the magic up front so later when you're maintaining there is no magic.
- verdverm 4y agoI like the way you describe the magic being upfront, that might end up in the docs somewhere :] With hof, the magic is at development time, than just once upfront, you can regen code as you designs and data models evolve. I think what you are getting at is that it is not runtime code gen and you can see all the code that makes up your program in files and got.