I totally agree. I commit when I have the working piece of code, with meaningful commit message. That way it is SO much easier to find what you did in the past.
Senior mobile developer at Bizimply. I build crossplatform mobile apps since 2014. By using React Native i create solutions loved by the users (because they’re native) and by the business (because it
Yeah! But actually with this kind of work you often have not really working piece of code or even at the beginning not working at all. And still you should commit that IMO.
In the past I didn't do it, I committed only when it worked perfectly. And the result was 3, maybe 4 commits. Then few months later I was wondering "Damn, why this change is here?!"
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I totally agree. I commit when I have the working piece of code, with meaningful commit message. That way it is SO much easier to find what you did in the past.
Yeah! But actually with this kind of work you often have not really working piece of code or even at the beginning not working at all. And still you should commit that IMO.
In the past I didn't do it, I committed only when it worked perfectly. And the result was 3, maybe 4 commits. Then few months later I was wondering "Damn, why this change is here?!"