4
dakkarant
87d

for the 3rd time ive tried introducing some version control on a project that really needs it because it has multiple people working on it.

And because the last time my efforts got shut down because in practice people thought it was too much of a hassle to develop locally rather than on the shared development server directly, I made a feature that would let people checkout branches on said server...

Apparently the action of; saving > committing > pushing to your feature branch > merge after aproval, is still too much for people to comprehend; "I think this is too convoluted can't we just keep pushing to the production server to check our work and then commit and push to the master branch"

So I just got pissed and said fuck it, no more git then, I'm not even going to put any effort into changing tooling here anymore, and this is a massive project where we have to manually remove code that isnt ready yet from the staging environment.

Are the people I'm working with just this stupid or am I really overengineering this solution because I think 4 people should not be working on the same file at the same time without any form of version control and just direct upload to FTP.

(and yes, I know I should leave this job already, but social anxiety of starting at a new company is a big obstacle for me)

Comments
  • 0
    Introducing git for a whopping four people just because git is cool... well yeah, no. For such a small team, SVN with Tortoise is perfectly valid and way easier to use.
  • 4
    I think SVN over Git is a matter of opinion :D

    That being said, doesn't matter the size of the team or the project version control is always good practice.
  • 2
    @Fast-Nop SVN support looks super janky for mac, and much more complicated to set up than git imho
Add Comment