Of course they don't use git. And also they don't use SSH all changes get committed by FTP.


When I started he gave me root access and I had to clone the whole fucking thing, wich was about 2gb, via FTP.


He stumbled when I told him, that I will test all changes first on my local machine. They were used to work in production.


  • 6
    What. The. Autual. Freaking. Fuck.
  • 19
    They work on production so that no dev can deny a bug with "works on my machine". ^^
  • 3
    Wait, what?
    I'm not sure what is worse, not using a proper (and modern) version control or testing in production... I mean - how could they work previously? For (very!) small projects it may be "acceptable", but 2GB in files is not small!

    I wish you good luck.
  • 6
    @sbiewald I quit today. 😉
  • 2
    @Wombat good for you. So many people without technical backgrounds get angry when something "isn't right", there's nothing wrong whatsoever, and they refuse to give you an example of what's wrong saying "fix it".
  • 0
    What excuse could there possibly be for doing things this way?
  • 1
    @NeedsMoreDivs retarded dumbass?
  • 2
    Had about the same thing; but Dropbox and they kept projects from 10+ years around, and personal items like passports and what-not. I just don't get some people. Stay strong and try to educate or figure out a way to make it bearable.
  • 2
    @CoffeePanda in my inexperience, I did that also for a little while -- even when they were Git projects.

    I soon learned what a bad idea it was to stick Git repos in cloud-synced storage though. Easy way for repo objects to go missing.
  • 1
    Actually, adding onto the mistake of putting Git repos in Dropbox, I also discovered it makes it difficult to work in local repos if someone else is trying to do the same.

    I was the one who brought Git to the company I work at, so things were a little bumpy at first...

    Or maybe still are, but not nearly as much now.
  • 2
    Don't worry. You are not alone in the experience hehe
Add Comment