35
Awlex
73d

That one time I was appointed to be a group project leader and forced my members to learn git. It was a fierce battle, but I did not give in.
Needless to say, I eventually got some thanks in return (after insults about git being complicated)

Comments
  • 6
    You mean there are devs that do not know git? WTF?
  • 4
    @arazzz You mean there are devs that do not know there are devs that do not know git? WTF? /s
  • 1
    I only use git self hosted at home so don't know it inside and out yet. We use IBMs Clearcase (the company standard) at work :'( planning to move to git in 6 months time
  • 2
    @arazzz

    There are some companies that do not use git. Even now.

    many devs may have forgotten git or never used it.
  • -1
    @arazzz I don't know and don't need Git, and in my company, we use SVN. We have better things to do than fighting a nightmare UI just to have features we don't need in the first place, like DVCS. Git is an error-prone, over-dimensioned usability disaster for 99% of the projects out there.
  • 1
    The hero the deserved! 😂
  • 2
    I did the same with latex a while back, we were writing our CS report at university and they wanted to do it in google docs :D it really helped in the end but i didnt get a word of thanks, in fact they kept complaining untill the end :D
  • 1
    @Fast-Nop
    - Error prone? How? "Everything is local" that is great the exact opposite of an error prone always online solution. -Complicated GUIs?!:
    1) Which GUI
    2) Really, are you stupid, it's logical and, if you use a GUI it's visual and easy to follow
    -99% of projects, really? From huge projects like the Linux kernel with many contributors, to small side projects, I haven't found a project yet, where it's bad.
    On the contrary, it's great for CI/CD(hooks), allowing for a faster workflow.
    - To difficult?: I learned when I was 13yo: As someone with very little actual coding experience and lack of understanding and appreciation for correct workflows.

    All in all, if you don't like GIT, fine(could you tell me why thou, I'm curios. But with actual arguments, please). Just don't try to make your unsupported "arguments" look like facts.
  • 1
    @xzvf if you can't understand why the UI is total crap, then I just hope that you'll never even come close to develop anything with UI. I have more important tasks to do than putting up with that shit just to do the auxiliary task of version control.
  • 3
    @Fast-Nop Git by itself is a CLI tool....... Which GUI did you use? That may explain you bad experience and make your points valid concerning THAT SPECIFIC GUI.
  • 1
    @xzvf yeah, and by UI, I refer to the CLI. It's not bad because it's CLI, it's because it's a bad CLI. As for the GUIs, guess why people usually drop them sooner or later and go for the CLI instead. It's because the design process was completely backwards with Git, which is why the GUI doesn't matter, you sooner or later will need the CLI. And then having used the GUI makes things even worse because you aren't really clear about which steps made the whole thing fuck up.

    Git solves some pretty hard problems that arise when you have 20 mio LOC and 1000+ devs world-wide, then SVN is a joke. But there aren't many projects like this, and the rest have to bear with the conceptual overhead.

    Starts with the model, I don't even want a stash because nothing relevant must be stored on the clients. Oohh working offline... great, compiler licence doesn't work anyway.
  • 1
    @Fast-Nop OK. If I may ask, what's backwards for you? I'm generally curious, because I have mostly used Git and you come, as far as I can tell from an Svn background.
  • 1
    @xzvf Yep, I love SVN because it's easy, which is why Toirtoise-SVN works well, and when I code after 2 months of system design, requirement coverage and failure mode analysis, I still know what to do.

    For good applications, you first design the intended workflow. Then the UI maps this workflow as easily as possible. And only then the backend is coded to implement the UI.

    With open source, it's often the other way around. First the backend is coded because that's the hard algo stuff, i.e. the kind of challenge most devs love, then a UI is hacked together as afterthought, and the user has to construct his own workflow from the plethora of options. Though this approach sucks for applications, it's great whenever you have machines communicating with each other.
Your Job Suck?
Get a Better Job
Add Comment