3 ms·
Work ethic vs details-oriented are two diff things. Maybe have a pull request model where you approve and give feedback? If it's truly work ethic, then your ca
by curo 8y ago
Work ethic vs details-oriented are two diff things. Maybe have a pull request model where you approve and give feedback?
If it's truly work ethic, then your call on whether to continue the project. Projects/startups are like romance, don't try to change the person (to each their own), or expect change to happen, just let people be who they are and decide if you want to continue given their disposition.
Be humble, be chill, and know you have your own faults that he probably has to put up with. I'm an only child. I wish I had a brother, so for my sake (lol), prioritize your relationship above your project.
- deleted 8y ago[deleted]
- dikaio 8y agoWell said @curo, thank you.
- gary__ 8y agoIf you're a "bit OCD" and about to embark on code reviewing your developers work, might I suggest you think about what your standards are and document/communicate them before bombarding devs with change requests? That makes the whole process less frustrating IME. Also, to begin with, you might want to ask yourself "Would i go and ask the person to change this after it was committed" as a self check as to whether stuff needs changed - just to ease people in, until those guidelines are fleshed out. You could well say you plan to tighten it up - and eventually rely on developers to review each others work. Another process is a mini show and tell, where before each user story / feature is committed its shown in action to the person who requested it / QAs etc at the developers desk. Problems seen here may not even be the developers fault. A tendency towards reactionary defensiveness, and the recent goings on, might be best considered before doing this right now though. (It may well be you don't give the leeway you would a non family member for this as well.)