>IT lead insists we don't need backups, "git takes

File: HBox dying of laughter.jpg (117KB, 900x1200px) Image search: [Google]

117KB, 900x1200px

>due to git's misleading command structure

>>56052381
should have used cvs :^)

>>56052381
https://www.atlassian.com/git/tutorials/undoing-changes/git-revert

Reflog?

>>56052381
huh? i dont believe this story. whenever this happens just force push a local copy?

>>56052381
So... the staffer run with --force? Or?

If you don't use Perforce it's not a real company.

>>56052435
this. the irony

Version control software is overrated tbqh famalam

>>56052446
Perforce will be dead soon thanks to Git and Bitbucket Server.

>>56052381
>"I don't know how to use the tool I was given to work with." scenario.
>Shitty management who can't use the proper tool for the job

All of this is git's fault.
Yep. Sure, m8.
Seriously wtf do you expect from a bunch of retards who use git for backup? That's almost "no mistakes allowed" level.
Also >>56052442

TL;DR
Your colleague's mistake was understandable, the reaction was not, but you know you have a shitty management so it should be expected. However there is no reason to blame git.

There's no such thing as good version control software. They all have cryptic and complex commands, and they all have the ability to utterly destroy your project if you don't have an autistic person's level of expertise with them.

A company that isn't retarded has teams for different parts of a project and they don't overlap. Then you use zip archives. We did this for 30 years at my company and it never failed.

>>56052552
>Then you use zip archives. We did this for 30 years at my company and it never failed.

https://en.wikipedia.org/wiki/Zip_(file_format)

>Initial release: 1989
>'30 years'

>>56052575
>being this autistic about exact numbers

>>56052599
Where do you think you are?

File: 1459784571351.jpg (161KB, 1890x1417px)

161KB, 1890x1417px

>>56052381
>>IT lead insists we don't need backups, "git takes care of that automatically"
I refuse to believe these people exist in real life

File: 111.jpg (789KB, 1153x1730px) Image search: [Google]

789KB, 1153x1730px

>i don't know how to use git
lol

Git is shit for backups. If you use it locally and your data gets corrupted/overwritten, you are basically fucked

>>56052792
If you use anything locally and your data gets corrupted/overwritten, you are basically fucked

i have yet to find a good turorual on how git works

it is fucking pure blackmagic

I'd love to use it, but it is just reserved for elitsit autists that tell you to read the fucking non-existant manual

I hate you need to install it to do the first file upload for a project..

>>56052435
How the fuck can people not know about the reflog and call themselves real developers, Jesus Christ.

>>56052381
>we don't need backups

HAHAHHAAHA look at this faggot and laugh

>>56052951
This worked pretty well for me:

https://git-scm.com/book/en/v2

I like this explanation of how git works on a conceptual level:

https://www.sbf5.com/~cduan/technical/git/

I have spent a lot of time with git though, so I might be one of those "elitist autists".

>>56052736
she scares the shit out of me for some reason

Do legitimate companies actually use git? I always thought it was a meme SJW thing. Perforce is the industry standard.

>>56052951
http://learngitbranching.js.org/
This helped me learn a lot. Also finding a helpful log alias to visualize your repository is a god send. Personally, I use:

git log --all --graph --pretty=format:'%Cred%h%Creset -%C(auto)%d%Creset %s %Cgreen(%cr) %C(bold blue)<%an>%Creset' --abbrev-commit --date=relative -n 20

>>56053249
Yes, legitimate companies use git. I know that while Google has a really fucked up version of source control, many teams within it still use git. At Amazon, literally every team but ones that work with very old code use git. Everybody in my office (an Amazon satellite) uses git, though I've seen old configurations file which get auto-generated by our package manager for Perforce.

>>56052885
well, than its not a backup system, is it??

My job isn't really tech related, but the point of my story is kind of related to your predicament

>part of my job is basically writing various shit on blueprints related to what we're doing
>doing a project that encompasses about 7 main buildings, 3 balconies, a few smaller kind of office buildings and some mechanical buildings
>our plans are basically just 2 buildings and I'm told to just write the names of the buildings on them, photocopy the prints, and use the same blueprint for every building
>all the specs of the buildings are all different, if I did that they wouldn't match up at all
>say "that's retarded", get some blueprints of the actual buildings printed off and just use those so there's actually some clarity in what I'm doing, not just a bunch of confusing copies of the same building that dont match up at all
>low and behold my company gets sued for something stupid, the blueprints I was using end up being crucial in the case, and if we had used the same blueprint for all the buildings we would have had a really hard time proving that we weren't actually at fault (long ass story that isn't really relevant to the thread)
>ended up saving my company potentially millions of dollars worst case
>end up getting a raise from the same superintendent who told me to just use the same blueprints over again, he thanks me for not mentioning that little tidbit to anyone

tl;dr, take some fucking initiative and just do it. If you think backups should be made just make some backups, if your company is anywhere half decent you probably have a room full of old computers, hdds, etc, etc, etc that no one ever uses anyways. Hindsight is 20/20, but you could have backed that shit up, thrown the HDD in your desk, office, storage closet, whatever, then when shit is hitting the fan you could have been the hero with backup in hand. Its way easier to beg for forgiveness than it is to ask for permission

>>56053347
Taking initiative gets you fired as soon as a moron in charge needs a scapegoat for anything.

>retards who can't into git
Hey bob can you please check in the file, I need to do shit

>>56053292
>than
kys

Even if one person completely destroys the master branch, shouldn't each employee have a copy that they're working on? At most, you should be losing about a month worth of work, not three years.

>>56053589

Only if you work for some shitty company, Anon.

I took my job by the balls and now I'm raking in the cash.

>>56053589
>being a pussy
Anything can get you fired if you fuck up. Although I guess I'm protected by a union so my job is kind of different, I almost have to kill someone to get fired. I can get "laid off" whenever though

So you can just wipe out a fucking repo on a technology designed to make that sort of thing impossible to do?

Is OP dumb or is your precious git shit?

>>56053589
If you got fired for taking the """"""""""""right"""""""""""" initiative then your company is shit.

An example of right initiative: Like this thread management says backup is irrelevant you do it anyways.
An example of wrong initiative: Management says that backup is important you in your autism says that git does that and money could be saved if backups weren't made.

>>56052381
Everyone else has a full backup in their local copy

>ITT people who think they know how corporations work

Rule #1: You never take initiative if you have a stupid boss.
Rule #2: There's a 90% chance you'll have a stupid boss.
Rule #3: Keep your resume up to date.

>>56053749
Yes but in this specific case, OP possible could have made a backup and been the hero his company needs, but doesn't deserve

>>56052492
Bitbucket Server is kind of shit, desu.

>>56053764
Making a backup which could be stolen in a hack in a company with a shitty IT department like this is exactly what can get you fired or even accused of espionage.

Seriously, never take initiative if the people around you are dumb. Never ever.

Hahah you stupid gits

The whole point of git is that it's distributed, so if one copy of the repository gets deleted or corrupted or whatever, it can be copied from elsewhere with all the change history intact.

Anyway, it's not Gits fault that the user messed up, not to mention using it in a centralized manner which defeats the whole purpose of Git

>>56053624

autismTriggered == True

>>56053868
yet git is designed to allow you to destroy future commits and force those changes on the remote

>>56052719
They do, either way OP is wrong, assuming they aren't treating git like CVS. This should be easy to recover from.

>>56053781
>Seriously, never take initiative if the people around you are dumb. Never ever.
You will go nowhere in life.

>>56053940
You'll go even less without a job.

Anyone who works in IT long enough knows to keep your head down.

>>56053686
OP is dumb. Git has plenty of safeguards against this. You can't push changes to a branch that aren't a fast-forward unless you use "push --force" and repository managers like Gitolite let you ban certain users or everyone from being able to force-push due to how dangerous it is.

Even if the guy in OP's story really force-pushed, every other person in the business who has the repository checked out has a full copy of the repository including every branch, so every computer in the business effectively has a full backup. Anyone could just force-push the damaged branch back to what it was before.

Even of the guy in OP's story was the only person who had the repository checked out, you could still recover the repository on his computer by using the reflog. Git doesn't delete unreachable commits for a period of 90 days after they become unreachable from any branches. Reflog shows you the history of each reference and effectively lets you undo any change in the repository that happened in the past 90 days, including "destructive" changes like branch deletions, force-pushes, rebases, resets, etc. If you know how to use the reflog, you can't accidentally lose data in Git.

>>56054003
>shilling this hard
>blatantly lying

Git has resulted in millions of man hours being lost from cryptic confusing commands and the ability to destroy everything very easily.

It's literally banned in some IT departments.

>>56054054
>It's literally banned in some IT departments
They should consider banning clueless retards instead.

>>56054054
harry potter has resulted in millions of children worshiping the devil from clear spell manuals that destroy faith very easily

it's literally banned in some schools

>>56054066
>banning clueless retards
There are basically only clueless retards graduating from CS programs these days. There's a reason why people actually hire Indians.

>>56054054
>Git has resulted in millions of man hours being lost from cryptic
that's because there are people using it as a backup solution
IT needs to seriously start having standards but garbage companies will do anything to meet budget lines

>>56054102
indians are the gold standard of clueless retards

>>56054054

>and the ability to destroy everything very easily

>company has say, five employees
>each of the five employees has a copy of the master repo, each working on fixing a different bug
>one employee accidentally the entire master repo
>another employee replaces the master repo with their local copy
>company continues on, the retard employee does not get the promotion he was hoping for

Some IT departments are retarded, due to not knowing how git works.

>>56052381
>I hate git for being shitty enough for this to happen, but by god, I hate management just as much.
but it's ust your ITs fault for not understanding how git works and not configuring it properly (e.g. forbid force push)

>>56054054
Why on earth would I shill an open source product?

>millions of man hours being lost from cryptic confusing commands
Yes.
>and the ability to destroy everything very easily.
No. You can only "destroy everything" if you don't understand Git.

Git is not perfect. Its biggest problem is its interface. Git was designed without any consideration towards user friendliness, and it has grown organically with a mess of Perl and Bash scripts, so not only does each command have a cryptic syntax that "made sense at the time," each command has a different cryptic syntax. Because of this, most people just rote-learn the basic commands that they need and they have no idea what to do to get themselves out of trouble.

Of course, Git is trendy right now, so a lot of IT companies are trying to pick it up. Some, like in OP's case, will use it for critical infrastructure without employing a single person who understands how it works. When they inevitably get the repository into a state that they don't know how to fix, they don't bother to learn, they just throw their hands up and blame Git. This is the mistake.

>>56054133
in defense of poo, the CS brogrammer garbage is worse

>>56052381
You don't like git, so you're either:
>I don't use version control! Haha! Now where was that function definition, I think we're using functions.1.old.new.redone.py now???
or you're
>SVN and CVS are old so they're good even though they're relatively primitive, let me just set up a new SVN server on my dedicated server which is an old Core 2 Duo rig in my basement hooked up over WiFi. I don't understand, why do hundreds of people complain about problems getting a copy of my GMOD mod over SVN?

If you code, use version control. If you code with a team, use fucking version control. If you're using version control, use fucking git. If you're too stupid to figure out git, you're too stupid to write good software.

That all being said, fuck the IT guy for not having backups.

>>56052491
You're the first type I see.
Don't you feel disgusting when you open your projects and have to scroll past 30 lines of commented out code, with the caption "commented out 2008-05-04 by Anon, saving just in case we need to roll back"?

Every developer I've had the displeasure of working with who eschews version control does this garbage.

>>56052552
If you're too stupid to operate a simple program, you're too stupid to write good software. Please stop writing software and ruining it for everyone else.

>>56052951
Have you tried using this new site called google? It's great, you put in your questions and it finds other people who have answered it. Usually on stackexchange.

>>56052381
The problem ain't git, the problem is the millions of retards that put git on their CVs when the only thing they know is pull and push origin master.

Git is very simple, you just need to read the fucking manual instead of stackoverflowing every single thing you want to do.

Fucking pajeets

>>56054256
>read the fucking manual
but as a busy millenial i dont have enough time to use capitalization or punctuation, let alone read complicated technical documentation that will help me write quality software everything is all about going fast and breaking things today dont you know anything grampa desu senpai i cant believe these old developers not taking advantage of the internet it triggers me so hard TRIGGER WARNING SHITLORD OMG LOL

Should I suggest my company uses GIT? The (mostly backend) web developers are literal retards. I think I am twice as fast as they are after 1 year, being 2 years behind them and coming in with 0 experience.

Right now they just code right on the server remote, and back it up daily. We haven't really had any issues so far... team is about 5-6 people. My fear is its going to slow them down so much we will never get anything done.

>>56054211
What are you going to do if i use SVN bitch nigga

>>56054410
Try my darndest not work with you or use your repositories for anything, and shit-talk your choice of tools and abilities as a developer if it comes up in discussion, with a heavy emphasis on assuming that you're too stupid to read the manual for git.

>>56054436
And what if i can use both Git and SVN for working on different projects with different people?
I actually know both and you know only one, how hard should i shit talk your inability to use different tools? Are you stupid or something?

>>56054486
I can use SVN just fine. It's just not 2005 anymore so it's kind of a piece of shit.

>>56053894
>comparing to a boolean constant

Get out

How do I git gud at git? Real gud

>>56054783
using it

>>56054835
I'm pretty much limited to diffing between commits, status, log, push, pull, and unstaging. Pajeet tier.

>doesn't know how to use ___
>blames ___ when it doesn't work

How do I become a normie like you?

>>56053239
Because she is a strong black woman?

>>56052381
I dont get this. Isnt the point of gitHUB to have a backup in the cloud?

>>56054211
Fuck off steve you faggot

>>56055081
Many companies run their internal VCS, continuous integration, backup, etc. on the LAN instead of using a cloud service; some projects can't use third-party services for legal or regulatory reasons, others have been ongoing since before those services existed, others still just don't have the need for it

>>56054377
You're worried about slowing them down with source control when they're editing code directly on the production servers? Holy fucking shit man, that's some 1998 amateur action. I mean shit even 1998 people were developing locally and using ftp to push the source to production.

>>56055081
>it's a normie thinks shithub itself is git post

>>56054377
>deploying test code directly to a production server
>no test servers, not even just a local httpd on developers' PCs
>no VCS, going to guess no other form of backup either
Potentially slowing them down should be the least of your worries, this is a real amateur hour team if they're exposing themselves to so much needless risk every single day of losing everything or knocking out the production server

Reminds me of when I did team projects in college and emailing .zip snapshots of our code back and forth was still the only form of "version control" we knew, some practices are so bad that you need to show them another way before they burn themselves and your entire team gets sacked

>>56052381
>he changes the head and pushes changes
So?
It sounds like you're the one who can't use git

>>56054929
because she looks like a friggin alien with those long arms and weird hair

>>56052381
Complain to the higher ups, the guys who control the IT lead. Tell them about how fucked he is.

Since this seems to be the git general thread, I'll ask:

So let's say my repo has 5 branches being worked by five different teams. Let's say I need to push a critical bugfix ASAP into all 5 branches. How do I go about doing this? In bitbucket sometimes I see people pushing into multiple branches in one commit, how do I do that?

>>56052541
>>"I don't know how to use the tool I was given to work with." scenario.
It's managements responsibility to arrange training for their employees if they are supposed to use technologies they don't know. This training doesn't have to be more than: Read this compact git guide 1 hour per work day until you are finished and understand it.
If you just hand someone inexperienced a git access and all he ever does is pull and auto push that's what happens.

>>56054929

You know whats 2spooky4me? That feeling comes from thousands of years of evolution - something in our past has conditioned us to find something about that image threatening and posing a danger.

I wonder what kind of fucked up shit we experienced back then to cause that.

Realistically though it's probably because she resembles a giant fucking Emu

>>56053715

>back up anyway
>IT finds out
>Why the fuck are you undermining me anon
>IT hates you and starts to talk shit
>you become an easy target for anyone who wants to get along with IT
>start to be isolated
>management noticed you're not getting along with the group
>get fired

the corporate world is such fucking shit; it's 90% politiking and 10% actual programming

>>56055111
I'd off myself if my name was that dumb.

>>56056890
develop and commit it to one branch. Grab the hash of the new commit and use cherry-pick to put it on each other branch

>>56053249
>meme SJW thing
/pol/ pls go

ITT: people too dumb to use git
therefore too dumb to use version control
therefore too dumb to write good software

Thinking version control is backups retarded though, those people deserve what happened to them.

>>56053249
You're thinking of Github anon, and even that has legitimate devs when you ply away the attention whores, because your user-page shows how many commits you have
Also, git was writen to help with the development of the linux kernel, and you can say many things about Torvalds, but you can't say he's all about being PC

File: Screenshot from 2016-08-13 11-25-27.png (35KB, 1157x592px) Image search: [Google]

35KB, 1157x592px

>>56053249
>Perforce
well then, the industry standard is shrinking anon

I remember using svn and how trashy it was and slow, then we get git which is blazingly fast, better CLI, and people are bitching that its difficult. Must be the Gen Z fags.

>>56057925
but reading a manpage is haard!
why don't we just use dropbox :)

Similar tales have happened with Subversion.

>>56052719
Oh, they do. They do.

>>56052575
Fine: ARC, LHA, LZH, whatever was the flavour at the time.

>>56053193
a lotttt of people that use git basically only know how to commit, push, and pull.

as an example, i'm willing to bet that at least 25% of github users don't even realize that you can call `git clone` with an optional target path/directory. as far as obscure git tricks go, that's akin to saying "protip: turn your stove heat to *maximum* to boil water faster", but i'd be shocked if more than 80% of github users know this off the bat.

>>56058014
commit push pull merge mergetool and branch are the only commands these people need, if you run into a situation where you want git to do something different you can just look at the manpage or google, why would I learn 100 commands before using the tool? If one would run into OPs situation he could find out about reflog in 2 minutes.

>>56053917
> force those changes
So, the staffer was plain idiot that didn't know how to use perhaps the most important tool in his job and deserved to get fired.

>>56053249
Everyone uses git, dumbass

>>56053249

git is the software developed by Linus. Github is a website using this software.

e.g. In our company we have our own git server with gitlab

>>56058060
i would argue that developers should be more aware of how git works, but not necessarily "100 commands" depth. you're making this false dichotomy where if the OP's staffer were simply well-educated enough to not be dangerous with git, that would necessarily require that he become an expert in it.

i think there's a lot of space in the middle ground. the problem is the culture in tech industries. there's a saying that you should just "learn enough to be dangerous" which in this case is literally kind of true. can we promote learning enough to be helpful, or learning enough to be trustworthy?

>>56053249
hahahaha holy fuck are you retarded?

>>56053239
u racist!

>>56053749
If boss stupid than you. Why you are not his boss?

>>56053249
>I always thought it was a meme SJW thing
Are you the retard that believes everything /pol/ proclaims?

>>56058148
The world is, sadly, not really a meritocracy.

>>56052381
sounds like y'all got what you deserve for being tech illiterate

>>56052381
Everybody in this story is retarded including OP.

File: 338.png (19KB, 339x362px) Image search: [Google]

19KB, 339x362px

Been learning how to use git for university work, lost 6% for an assignment since I couldn't work with git expiring the due date, due to Windows 10 permission issues, meaning I missed out.

Still pretty neat.

>>56053249
Do people actually use Perforce, i thought TFS was like king meme

>>56052381
You're all retarded.

Unless literally all of you pulled that, someone has a local copy that isn't fucked.

>>56052381
>IT lead insists we don't need backups, "git takes care of that automatically"
So a software firm had no contingency plan in case of hardware failure?
>neverhappenedinarealcompany.mkv

>>56057502
Don't work at such a shifty company, retard.

I constantly berate managers for bad decisions and disobey dumb requests, but we're all fairly close and it's just part of the company culture. The culture is the understanding of
>if I fuck up, tell me so we can fix it
and it's so refreshing.

>>56059185
>windows
Found your problem.

Is there any good git GUI software? I don't want to teach all of mine 10 coworkers git cli and we really need version control

>>56059381
and now the thread dies, how convenient

>>56059230
We use Perforce at my company.

>>56052381
I never come here but I had to comment when I saw the thread on the front page. Obviously changing head doesn't destroy anything, so presumably OP meant changing a branch's target, which also doesn't destroy anything for normal operations like merge or even rebase (which does dereference commits and make life hell for a bit but does not destroy work and it doesn't even really destroy commits). But if for some reason he reset the branch, AND hunted down some commit that wasn't mutually merged and for some reason passed that to the command AND zero other branches in the ENTIRE REPO were downstream in history from dev, and then he pushed AND used --force AND the server was not configured to disallow this AND it's been 30 days (the default reflog lifespan for unreachable commits) AND garbage collection has run - what in the holy fuck OP? Is this how stupid /g/ usually is?

This is like complaining that Unix commands are unclear or badly designed because anybody can sit down with sufficient rights and run rm -rf /

I mean do you have any idea how aggressively stupid you sound, OP? Don't throw shade on what little high quality software there is in the world because you and the fuckups you work with allow yourself to use tools you know apparently nothing about.

>>56059381
>>56059514
Just suck it up and tell them to RTFM. You shouldn't need to teach developers how to do that.

>>56052381
This thread is bait. The scenario is literally impossible.
If you want to shitpost about your least favourite versioning software, please do it on reddit.
I don't even know what's more stupid, your shitty OP that never happened or all those Anons believing you.

>>56059869
not an option because i am _slighty_ above them which means they were assigned to me by other managers and they expect to get the job done. i obviously can't do it if 10 people need to learn cli and i won't put the project in jeopardy if 1 of those 10 people fuck something up. I need gui

>>56059936
Dude, what kind of Pajeet firm are you working for? Just get daily incremental backups of the Git server and be done with it.

>>56052381
Should've used hg from the beginning. You'll always know what specifically the command does.

>>56059936
how are people who fuck up learning about pull/push/commit/clone even able to program?
what programming language is so small and simple that people unable to read a manual of 200 words can learn to program in it and even become employable?

>>56053774
Atlassian and all its products are shit. They are a bunch of crappy developers with pricey desks who can't fucking maintain nor upgrade their own products.

>>56061438
name better alternative

>>56052381
>IT lead insists we don't need backups
What a fucking dumbass.