The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
There are no stupid questions- just stupid people. Keep that in mind as you answer my very possibly stupid question:
Any advantage to having the development team standardize in terms of the git client? I know they all basically do the same thing- pushes, pulls, merges, branches, etc. But is there any reason to ask all developers to use the same one (like Git GUI or Sourcetree), or is this just micromanagement with no benefit? I was just spitballing that maybe, if everyone is on the same sw and there's a problem in the client itself, it's easier to deal with, or maybe there are tiny differences which make it advantageous to keep everyone on the team using the same one? Thoughts?
Anything that is unrelated to elephants is irrelephant Anonymous - The problem with quotes on the internet is that you can never tell if they're genuine Winston Churchill, 1944 - Never argue with a fool. Onlookers may not be able to tell the difference. Mark Twain
The best git client is the command line. I kid you not. The first time I heard it I scoffed at the idea. But after a while I would not go near any of them tools today. I know this feels like a stretch if you come from a VS/CVS sort of background -like I did - but try it.
To be clear: command-line for git pull/branch/add/commit/push that is.
For solving merge conflicts i use meld but here everyone uses their own tools for that. I would not want to work in a place where ppl need support for such basic tools...
"If we don't change direction, we'll end up where we're going"
I don't think there's a real need for it, although if you all use the same tool you can help each other and give tips and tricks.
However, people have their own tools and preferences and I always like it when employers take my individual needs into account.
One thing to watch out for is licensing.
GitKraken, for example, has a free tier for open source development, but it's not for professional teams.
A developer may not care about that a lot and I think you can just download and use it, but your company is legally obliged to buy a license*.
If everyone uses their own tools, make sure they get the appropriate licenses.
And that's where another pro to all using the same tool comes in... Managing licenses is a hell of a lot easier
* Although the chances of getting caught/fined may be very low.
I do use a SBC as my Jenkins and local Nuget server but it's a bit more powerful than a pi NanoPi M4V2 - 4GB it works beautifully - I have several of them in my house - my network streamer ( LogitechMediaServer ) runs on one fitted with a 1TB M2 SSD NVME which easily holds my music collection ( thousands of flac files ) the digital stream feeds my outboard USB DAC .which pipes the analogue to my hi fi system ( that's another story ) I love SBC's
"I didn't mention the bats - he'd see them soon enough" - Hunter S Thompson - RIP
Last Visit: 31-Dec-99 18:00 Last Update: 13-Jun-21 22:09