"Are you familiar with uploading your code to Google Drive?"

I left the building at that exact moment.

HR: We have received complain that you have been sexually harassing an intern.
Me: No, I wasn’t. Me and the new intern all we talk about is Coding, Apps, and TV-Series
HR: You are lying. I have the words that you said to the intern. Do you want me to read it out.
Me: I have no clue what I said to the intern so please read it out.
HR: You said, “Always pull before you push”. Do you remember saying this?
Me: Yes, I was teaching the intern how to use GIT.
HR: Okay, let me call the intern and let see if he says the same.

** Intern **
HR: Was he sexually harassing you today at any time.
Intern: No
HR: Did he said, “Pull before you push” to you?
Intern: Yes
HR: What does that mean, sounds like a slang for something sexual.
Intern: haha, no it means that I should pull the changes made to the files before I can push the changes I did to the code from my computer.
HR: But he said something else like he was teaching you how to use GIT
Intern: Yes, that’s what GIT is.
HR: Okay both of you can go and don’t use this type of terms in the future it doesn’t make good working culture.

Cat: *walks onto keyboard*
Me: Aww how cute
Cat: $ git reset --hard HEAD

This was during the first day of my first real dev job, straight out of college. I didn’t have have much experience with version control since I did mostly solo projects in college, and I wasn’t exposed to SVN or Git in school at all.

One of the senior devs was going to give me and another new guy a brief overview of the codebase. He sets us up with the GitHub repo for the codebase and tells us to clone the codebase locally. I didn’t really know what this meant but I felt kind of embarrassed to ask, so I just clicked “download as zip” on The GitHub repo.

After a minute he saw what I had done and was like “yeah, that’s not what you want to do” and showed me how to clone it. I was kind of embarrassed but I learned Git pretty quickly after that.

I don’t really have a moral to this story except that “no question is a stupid one” is much easier said than done for many people, and it can be embarrassing to ask certain questions sometimes.

During a random school project.

Me: *Explains why team members idea is bad*

Team member: *Im going to do it like this anyways.*

Me: *add explaination of why idea is bad to git commit log.*

1 week later: some parts of the project dont work like they are suppost to.

Team member: *dude can you help me bla bla....(encounters issue i mentioned regarding his idea)*

Me: *no, i've already got too much on my plate. please, sort it out yourself....*

At the presentation

Teacher: *ask question about problem*

Team member: *tries to blame the problem on me....*

Me: *shows git commit log to teacher*

Me: *passing grade*

Team member: *failing grade*

Justice served.

Mac: Suddenly turns off
Me: Fuck my code..F***
Mac: No response at all
Me: reset SMC etc etc
Mac: I am dead (no battery detection, dies after 10 min on power adaptor)
Me: Skips a heart beat..(Git, oh yea git)

**Takes Mac to store, After diagnosis**

Apple Freaking Genius (AG): Your Mac has a mother board problem it needs to be replaced.
Me: Hmm what is the problem exactly??
AG: Issues in logic board and some other components.
Me: How much?
AG: Out of warranty so $$$ (60% of original amount)
Me: (wtf?) Really
AG: It's entire motherboard replacement .. bla bla

**Bring it home > open > everything seems ok on multimeter as per circuit diagram > finally finds a voltage drop that is not consistent > minute short circuit > remove > check further > nothing else > reassemble > hit power button > starts fine > freaking battery detected > works fine**

0 $ repair

Fixes two more devices @ 0 $ in friend circle

Builds a raspberry pi backup laptop with 3d printed body..Ubuntu.. you know can't live without a computer

#ThugLife #Engineer

CEO: You need to use git.
Designer: No

CEO: You can backup stuff.
Designer: No

CEO: You don't have to save copies!
Designer: No

CEO: You will use a really cool command line!
Designer: No

CEO: It has unlimited storage
Designer: So when we start?

Three years into studying software engineering and three quarters of my class have no idea what git is.

But by gosh, can we code the shit out of a tic tac toe game.

Git makes it easy to search through historical changes they said. Git is amazing when working in teams they said.

It sure is.

If your coworkers do not commit every time they burp or fart, do not use "🚀" or "✨" or "fix" as a commit message, and do not push all their shitty experimental broken branches without cleaning up.

I'm surprised there are no piles of fecal matter behind their desk chairs.

The typical devRanter

1. Uses dark theme of IDE and devRant app
2. Hates his/her clients
3. Likes Arch based distros
4. Checks his/her ++'s count or notifications after publishing a rant
5. Hates facebook
6. Associate the morning with a cup of coffee
7. Can't do any job when there are no headphones
8. iPhone vs Android? - fuck, they both are good/bad
9. Every time googles git command to remove a local branch
10. The best VCS is git, but I never used any other VCS

No, I'm not "switching to FTP," it's about time your learn git mate.

Is Microsoft going to ruin GitHub? NO!

Are we going to get amazing git integration in VSCode? ABSOLUTELY!

They're a 600 billion dollar company and they're one of the leading contributors to open source. They know the community they are handling and how fragile it is. This is just a developer trust move from them.

Stop pretending this is the end of GitHub, cause it isn't.

Dev russian roulette

The company I work for...
Has:

1. No CI/CD
2. SVN instead of GIT
3. Outsourcing to India (oof)
4. No Automated Testing
5. Uses Bugnet (ancient, outdated)
6. No clearly defined code standards
7. No real documentation on the code
8. Rubbish code
9. No desire to reduce technical debt
10. Poorly maintained DB
11. Poor outdated equipment
12. A useless PM
13. Still priotizes IE support (??)

On a scale of 1 to 10 how fucked is this company and anything they develop?

The past 2 years where I work:

Me: hey let's use git instead of ftp!
Boss: should we?
Some time later: he is loving it...

Me: hey let's use trello instead of excell!!??!
Boss: huumm.. Dunno... Should we?
After much convincing: whole departments are using and loving it....

Me: hey let's move from rackspace to DO!
Boss: huumm... Convince me...
Year latter: everything smooth and muuuch lower prices... Managing 6 servers instead of one...

Me: UNIT TESTS!!!
Boss: nah, this but a waste of time...

For real? Get a grip man, I only encourage solutions tested ( no pun intended, or is it ) by me for a long time...

As a developer in Germany, I don't understand why anything related to development like IDEs, git clients and source code documentation should be localized/translated.
Code is written in english, configuration files too. Any technology, any command name in a terminal, every name of a tool or code library, every keyword in a programming language is written in english. English is the language of every developer. And English is simply a required skill for a developer.
Yet almost everything nowadays is translated to many other languages, espacially MS products. That makes development harder for me.

My visual studio menus are a mess of random german/english entries due to 3rd party extensions.

My git client, "source tree" uses wierd translations of the words "push" and "commit". These commands are git features! They should not be translated!

Buttons and text labels in dev tools often cut the text off because they were designed for english and the translated text is bigger and does not fit anymore. Apparently no one is testing their software in translated mode.

And the worst of all: translated fucking exception and error massages! Good luck searching for them online.

Apple does one thing damn right. They are keeping all development related stuff english (IDE, documentation). Not wasting money on translations which no developer needs.

Yesterday was Friday the 13th, so here is a list of my worst dev nightmares without order of significance:

1) Dealing with multithreaded code, especially on Android

2) Javascript callback hell

3) Dependency hell, especially in Python

4) Segfaults

5) Memory Leaks

6) git conflicts

7) Crazy regexes and string manipulations

8) css. Fuck css.

9) not knowing jack shit about something but expected by others to
produce a result with it.

10) 3+ hours of debugging with no success

Post yours

Please explain this bitbucket! 😂

Went blank when interviewer asked me do I know KITT. I knew that he didn't mean Knight Rider, but I could not think of anything sensible in the few seconds I had time to answer the question so I answered NO. Interviewer said that it is a basic requirement for the job and it seemed that I lacked the basic skill needed for the job.

Needless to say I didn't get the job. Later that day as I was telling my friends about the interview they seemed really confused....

"... but you know GIT very well. You use it on a daily basis. Why did you answer NO ?"

Damn, blew my interview on pronounciation issue :/

Month #1 at CS University. We write C on the terminal, with nano. No vi no ide no highlighting. Neither makefile is allowed. Professors don't know what git is.

I am pissed off.

Professor refers to Linus Torvalds as the most arrogant developer. Says no one uses Git and thinks it has no advantages over SVN. Forces us to use SVN. :'(

friend: so how are we gonna do this project together? download, edit then upload to google drive again. thats the fastest way.

me: how about git?

friend: what?

me: ill just create a repository and create branches before we merge it with master. no need to go through that process of downloading and uploading multiple times

friend: not sure... what... that.. is.....

me: oh we have a looooong way to go, ill guess ill have to teach u git right from the beginning

Fell like I can finally vent this now I've calmed down.

Me: You've fucked the tree again
Junior: No I haven't
Me: It says there "Fixing merge conflicts"
Junior: Well it wasn't me I wouldn't have done a merge
Me: It has your name next to it...
Junior: Well that commit wasn't there a second ago
Me: it's dated for Friday...
Junior: Well if you hadn't committed to master and blah blah blah
Me: We'll if you knew know to use git we wouldn't have this problem.

I'm not angry, mostly sad.

At my workplace we don't use git.
There are constant overwriting, sending code via email or USB stick and forgetting passwords to zip-files shenanigans going on.

I already use git for all my local projects (literally git init in the directory) but my coworker and I thought that it would be a great idea to have a local server with a Gitlab running on it.
So I started looking into running a self-hosted Gitlab (for about 15 minutes) and then our boss who was sitting right next to me almost shouted at us: "Such stuff should be coordinated with the boss! We don't just do something and burn my money because it's _cool_!"

No, git is not cool, it's necessary for crying out loud! Gitlab is cool but at the end of the day also just another tool too.

I guess I have some persuasion to do.

I don't know what version control has done to our boss that he has such a deep dislike for it.

Much-security.nl is down.

No, no hack or whatsoever. I just reinstalled the wrong server through my control panel.

The new blog version will hopefully be up tonight. 'you keep promising that' - I don't have a backup of the old version and I only just started using git so I can only upload the new version (or git pull). Next to that, except for the front-end, everything works now.

😐

Our manager is not a developer and he has no idea of what we are doing most of the time, but he thinks that stand-up meetings are the coolest way to control us.
Sometimes coworkers joke about his lack of knowledge and today I think we reached the highest jerk level: «Yesterday I opened a new branch on the git repository and today I'll continue on this task».
I struggled to stay serious on my turn.

When your professor tries to tell you no one uses git in industry and you feel bad for all the other students who believe him. Side note: he is convinced everyone uses subversion.

Management:

"We're gonna make our own builder that sets up pre configured files.

So we are gonna get rid again of GIT, because with our system you shouldnt be working over each others files if you keep out of other peoples files."

So they basically are saying, we are going back to no version control because you should all keep to the honor system because our system is better.

I'm fucking leaving...
And possibly leaving a poison pill to boot

Dude, for the hundredth time, stop leaving random chunks of commented out code all over the place in case we "need to find it easily later"...

This is literally the reason we use git.

No, I will not pass it in a code review. The same as last time. And the time before...

Dahhhhh

Started working at a large company with promises of a great framework, stable environment and bleeding edge tools, decentralised working environment, only to find visual studio 2010, no git, no project management tooling whatsoever, all documentation stored on svn, no slack or other modern communications platform, still using uploaded word documents as documentation for projects and meetings, so yeah I can truly say :/

Still not learning git properly. I still find it very hard to grasp how this works and although I'm starting to use it more and more, I just can't wrap my hear around it so I often reside to scp for upload and no version control at all.

:'(

There is no reason for any developer to not know git well. No fucking reason. Stop making shit harder for everyone by being like “oh I’m not the keenest on git” STFU and just learn it better you pussy.

git commit -m "Batman! (this commit has no parents)"

I'll show myself out.

Friend: I don’t need git. Git is for people like you who cant do good backup of their code
Me: Yeah, yeah, go do whatever you like...

2h later comes to me:

Friend: Can you make me repo and show how to use it...?
Me: What..? You drunk?
Friend: Naaah, no... My disk broke while ago...

Karma is a bitch :D

Friend :- Dude i made some changes and the code is not working now.
Me:- Bro, Do you even GIT it?
Friend :- No i don't GET it how it happened and how to restore it.
Me :- You destroyed my pun and my faith in your development skills -_-.

Product Owner: "need this doing in 6 months, can you do?"
Me: "we're too busy to start another project at the moment - can you wait about 6 months for it to start, or I'll have to hire more devs"
PO: "I'll just outsource it"

36 months later the company he outsourced to is out of business and hasn't delivered, and I've had their half-finished shit show git repo dumped on me.
No comments, no docs, and no units tests, so no fucking idea what it's supposed to do

I am backend + a bit devops
8 months I worked with front-end person in react.

8 months he was telling me.. git usage is not needed for front. There is no need for that, it is not like back.
Recently he made refactorization in a week time, this idiot did not do even single commit in the process.

4 months he was telling me, testing is not needed in front. Even if the work is complete, there is no point to cover with testing.

Today I heard from him, adaptive web design is impossible to do in css only, it needs having javascript to control right height and width size for elements.

At last. I got freed from him. He got fired.

Remember not to deploy today

Been a jr. dev at a company that's badly in need of more devs. So they hire a sr. dev to work w/ me. Dude's got yrs of xp over me, so he should be ramped up in no time, right?

Jk, he doesn't even know the basics of git. Also, his code is shit. If he's not let go anytime soon, at least I'll look awesome relative to this guy come performance reviews ¯\_(ツ)_/¯.

WTF is up with open-source projects using emojis in their commit messages... FUCKING emojis..

I get it, programming is fun and a hobby to many, but can we also keep at least a minimum level of professionalism here.

WTF is a wheelchair or bento emoji at the beginning of a commit message supposed to mean? Why the hell even bother to use it in the first place? There is no fucking reason for this retarded shit.

Is this what happens when activist developers get out of their way to make programming "inclusive"?

It is your personal project and so if you want to use emojis it is OK, I respect that (not really) but I can't trust your code, your commitment, or the quality of your work if I see those dumb Unicode characters there.

Git commit messages are not a game. Be playful with comments in code or your readme.md file but git messages should be a clear reflection of the changes not what a teenager's phone vomited on the keyboard.

git add *
git commit -am "stuff"
git push -f origin master

No regrets

*FourWeeks From Deadline*

Two CoWorkers: "Oh cool, Visual Studio 2017 is out, I am gonna switch"

Breaks the build.

They then tried to spend hours trying to get the project to work on both versions, with no success, then let us know.

I am just glad we use Git

TFW your client's git policies are so draconian that the dev teams use "develop" as trunk, and completely ignore the release process.

I wrote up 50 pages of git standards, documentation and procedure for a client. Bad indian director 9000 decides the admin (also Indian) who specializes in Clearcase and has no git or development experience is more qualified to decide and let's him set the policy.

FF to today:

- documentation, mostly contradictory, is copy pasted from the atlassian wiki
- source tree is the standard
- no force pushing of any branches, including work branches
- no ff-merge
- no rebasing allowed
- no ssh, because he couldn't figure it out...errr it's "insecure"
- all repos have random abbreviated names that are unintelligible
- gitflow, but with pull requests and no trust
- only project managers can delete a branch
- long lived feature branches
- only projects managers can conduct code reviews
- hotfixes must be based off develop
- hotfixes must go in the normal release cycle
- releases involve creating a ticket to have an admin create a release branch from your branch, creating a second ticket to stage the PR, a third ticket to review the PR (because only admins can approve release PRs), and a fourth ticket to merge it in
- rollbacks require director signoff
- at the end of each project the repo must be handed to the admin on a burned CD for "archiving"

And so no one actually uses the official release process, and just does releases out of dev. If you're wondering if IBM sucks, the answer is more than you can possibly imagine.

Taught my whole team that you can enter cmd/bash commands directly into windows explorer in the location bar.
No point in opening git bash to just clone a repo or open cmd just to run a php server.

I just got hired as a systems administrator at a company that develops web forms. NO ONE in the company has heard of git. They don't use any kind of version control.
I'm a little worried...

"no micro managing here!"

*Boss comes in at 5*
- how much work have you done?
- why isn't this finished yet?
- you're working too slow
- show me git status
- show me git log
- why is this taking you so long?

Late night coding and my last git message is "changed a shit load of stuff...don't worry I got this"

Good thing this a personal project haha

"I'm not ready"
"No one never is"

*commit right away

git-rebase-no-conflict

seriously, I know git is not the most user friendly, but really....

I attend to a course in my high school, like, it offers you a technical and a high school diploma in the end of tree years of course, anyway

last year I had this project. I had 4 other people working with me. I suggested we use git as there would be many people working in the project and git would help us manage all the files and get everything together in the end.

they didn't even bother to try learning it, I was like "fuck it, let's go without it", no one did anything till the last 2 weeks. then I was all stressed out getting the code together, manually, and the deadline was close.

In the end I wasn't able to put the chat this guy have made, he got mad and I was like "motherfucker, it would be one damn command `git merge` and your fucking chat would be in the final project"

oh it was great to get this out 😎😀
don't even know if I'm making sense xD

Oh no, oooooh nononono
they dont delete the branches after a pull request

232 branches? hhhhhhhhhhhhhhhhhhhno
and look at that naming

im intimidated, i dont want to work in this environment. No. NO!

Github Inc. (Feel good inc. parody)
=========================

Ha-ha-ha-ha-ha-ha-ha-ha-ha-ha-ha-ha-ha.
Github.
Fetch it, fetch it, fetch it, Github.
Fetch it, fetch it, fetch it, Github.
Fetch it, fetch it, fetch it, Github.
Fetch it, fetch it, fetch it, Github.

Fetch it, fetch it, fetch it, Github.
Fetch it, fetch it, fetch it, Github.

(change) Fetch it (change), Fetch it (change), Fetch it (change), Github
(change) fetch it (change), fetch it (change), fetch it (change), Github

Repos breaking down on pull request
Juniors have to go cause they don't know wack
So while you filling the commits and showing branch trees
You won't get paid cause it's all damn free

You set a new linter and a new phenomenal style
Hoping the new code will make you smile
But all you wanna have is a nice long sleep.
But your screams they'll keep you awake cause you don't get no sleep no.

git-blame, git-blame on this line
What the f*ck is wrong with that
Take it all and recompile
It is taking too lonnng

This code is better. This code is free
Let's clone this repo you and me.
git-blame, git-blame on this line
Is everybody in?

Laughing at the class past, fast CRUD
Testing them up for test cracks.
Star the repos at the start
It's my portfolio falling apart.

Shit, I'm forking in the code of this here.
Compile, breaking up this shit this y*er.
Watch me as I navigate.
Ha-ha-ha-ha-ha-ha.

Yo, this repo is Ghost Town
It's pulled down
With no clowns
You're in the sh*t
Gon' bite the dust
Can't nag with us
With no push
You kill the git

So don't stop, git it, git it, git it
Until you're the maintainers
And watch me criticize you now
Ha-ha-ha-ha-ha.

Break it, break it, break it, Github.
Break it, break it, break it, Github.
Break it, break it, break it, Github.
Break it, break it, break it, Github.

git-blame, git-blame on this line
What the f*ck is wrong with that
Take it all and recompile
It is taking too lonnng

This code is better. This code is free
Let's clone this repo you and me.
git-blame, git-blame on this line
Is everybody in?

Don't stop, shit it, git it.
See how your team updates it
Steady, watch me navigate
Aha-ha-ha-ha-ha.

Don't stop, shit it, git it.
Peep at updates and reconvert it
Steady, watch me git reset now
Aha-ha-ha-ha-ha.

Github.
Push it, push it, push it, Github.
Push it, push it, push it, Github.
Push it, push it, push it, Github.
Push it, push it, push it, Github.

No one uses Git, nor any code hosting service, but I'm the Junior.

Yeah okay, fuck you and your fucking siloes.

I won't tolerate lack of version control anymore, I'll be looking for the next "professional opportunity".

It's been a year , I have been contributing to open source and using GitHub.......
There were some people who criticized me for doing open source, saying there's no future in that and u will end up doing nothing.
(But I never listened to them and ignored there words)
Few days back the same person asks me how to start contributing to open source and help him learn git.
U know what I did then??
I ignored again.

I don't have a girlfriend to commit to.
So I commit to github...

Is it just me or does it look like I accidentally spelled “derp” in git contributions?

Inner Me: Where the fuck is this bug coming from
> Set a breakpoint in every single place where the method I'm using is being called.
> Try calling the method before every function call
Inner Me: FUCKING DAMNIT! It's been hours now
Inner Me: No way it's the library I'm using.
Inner Me: That couldn't possibly be the problem
> Try running it again and delete some more shit
Inner Me: FUCK MEEEEEEEE
> Getting delirious
> Begin to look at some stupid memes.
> Come back to it.
> Have an Ah-ha moment
> Try running it again but rearrange the order of the method calls
> Still no luck
> try git stashing a bunch of my changes
> git stash apply them back
> erase the method call entirely
Inner Me: well that sort of worked, but now all my numbers are incomplete
Inner Me: FUCKING FINE!!! I'LL LOOK IN THE GODDAMN LIBRARY
Inner Me: FUUUUUUUUUUUUUCCCCCCCCKKKKK a stupid integer casting was occuring to my floats!!!

Now Talking to my girlfriend.

Me: The problem was in the library I was using
Girlfriend: How are you going to fix it if it's in the library?
Me: ... I can, because I wrote the library...
Me: FUCK ME RIGHT?
Me: I guess moral of the story; sometimes the problems starts with ourselves
GF: Hahaha. Thats Deeep

.. for the first time I permanently lost access to one of my GPG keys that were actually in use. No revocation certificates, nothing in the keychains on any of my hosts... Keychain flash drive that got stolen had a copy of both, my fileserver used to have a copy of that flash drive until I deleted it to make room for a filesystem migration, and my laptop used to have one.. until I decommisioned it and shredded its hard drive to be deployed somewhere else...

fuck

I can't sign my git commits anymore, and I can't revoke the key either.

(╯°□°）╯︵ ┻━┻

I'm going to a friend's house because his computer won't boot. In case I don't return, please clear my git stash. No one needs to see that kind of crap.

Him: "No developer worth his salt puts each of his brackets on a new line."

Me: "I mean... I agree it's uglier but your whitespace commit means we git blame you for everything."

Him (upset): "You BLAME me? I'm sorry I have standards."

Me: "Not blame blame, git blame like the history view of the-"

....too late he reverts his commit and hates me for life.

I wasn't even disagreeing, I was trying to explain git blame. :(

Developer confession.

I always git push a new branch even though I know it will error as there's no upstream, just to copy the full git push with set upstream arguments from the error message.

Assigned to a new project team..

Using git, in a creative way. So.. "master" is "dev" branch, usually. Everyone can push their branch to dev server .. so it's "dynamic for us". Production branch is whatever, as long as the branch has the release version. Sometimes, the release comes from "master".. that mean "dev" in normal geek..

That's just Git. The source code is a saturated spagetti of Entity framework and Caliburn. It is littered with antipatterns, especially basebean. Holy Christmas and Easter that baseclass do a lot of stuff that has no place as a base class ..

Fucking frameworks, I'm gonna start to evangelize frameworks as the no1 antipattern.

MS SQL as the main DB, but is dumped to json FILES through a scheduled task to increase read performance on web.

There is a soap endpoint to expose the json files, fml..

I am assuming I was placed here to improve stuff, I have never in my life seen anything like this before.

There is a special place in hell for this repository

When you're the most "junior" person on the team and you're the one pushing for Git. How we've managed to come this far without any version control is beyond me. Especially with the fact that we've had to work alongside a 3rd party who handles a lot of the site dev...there have been a lot of "stepping on toes" over the years and no one ever thought "there has to be another way."

🙄

>Someone opens issue
>Am in school
> Opens Git(Nyan)Hub
>Sees Issue
>"yOuR pRoJeCt hAs a CopYrIghTeD nAmE"
>does not seem to be the case, we're a OSS project and the fact you can't copyright names but trademark them

>Me: "When there's a legal issue, open it up on email than on a issue, and your shit is invalid as well, fuck you."

> Closes and Locks issue

Welp, that's a wasted 2 minutes right there homes

Keep in mind I even asked a lawyers' statement from the company that this concerns them. Fucking FUD tactics again by some random

Let's add the fact there was NO DMCA from the mentioned plaintiff. Wow. just fucking wow dude.

I seriously do not understand the rants against Windows.

I love Windows 10 (got as free upgrade from MS), and have no issues with MacOS or Linux OS. I use them as well but do all serious work on Windows.

All my life, I have worked on business / commercial side and picked up Web development in last couple of years. I started using computers on DOS in 1992, and shifted to Windows 3.0 in 1995. There was no Mac or MacOS back then.

For serious work, I purchased a old Dell Precision M4700 workstation grade laptop with quad-core i7, at throwaway price, got 32GB RAM, 2.4TB (1x2 TB + 400gb) of SSD on super sale online, and installed it myself. It easily supports dual 4k monitors.

Git-bash on windows allows all the necessary linux command line on windows. Though not tried, Windows 10 allows embedded Ubunutu with linux terminal. Web development tools like - VSCode, git, github / bitbucket clients, NVM/Node, React / Redux / Webpack / Gatsby / Jest, REST clients, GraphQL client and server, Graph Server, Chrome PWA / Chrome Dev Tools, http/Websocket/WebRTC interception, Google Firebase SDKs, AWS sdks, cloud utilities, CI/CD tools work flawlessly. Windows even has its own package manager for applications.

Another real-world argument for why I always say git is worth learning properly.

Had to track a really weird bug down today. Had no idea where it came from, how long it'd been in the code and hadn't the foggiest what was causing it. Realistically it could have been introduced any time in the last year or two, and that's tens of thousands of commits in this repo.

Git to the rescue. Knocked up a quick script to test the case in question, fed it into "git bisect run", and 30 seconds later git found the exact (small) commit that caused the issue.

It's a brilliant part of git, yet it seems like almost no-one I know uses it. Some use "git bisect", but using "git bisect run" and passing a script to it seems to be alien to most - yet it's probably my most used tool when it comes to tracking down bugs like these.

Aaaah, I fucking love it to death, when customers spontaneously decide to hire a separate, unrelated company to add new content pages to the website developed by our company.

That furuncle of a company must have had real pro devs to just create a new /html folder, dump their shit content in there and just manually add links in the existing CMS pages.
HOLY FUCK!
As you might already have expected, the /html folder contains:
- static *.html files for every page
- inline CSS in the *.html
- the crappiest PHP mailing script I have ever witnessed
- images with random resolutions, mostly too small

The layout of these puke-ridden pages obviously doesn't fit neither the existing color palette, nor has anything common with the current layout or typography at all.
These bastards don't even use Git!

Come on, dear customer, could you PLEASE fucking NOT hire a completely separate company to do OUR job?
PLEASE? PLEASE?!

I had to compare the whole deployment folder with our repo to find out what else these brain-damaged cunts changed in our code!

GIT LOG VERSION 101
----------------
75fed18 pay no attention to the man behind the curtain
56772ff added security.
6374fdd needs more cow bell
6b27de9 Committing fixes in the dark, seriously, who killed my power!?
bffce8a giggle.
7e93977 Refactored configuration.
e66c495 pgsql is more strict, increase the hackiness up to 11
5690dd9 Revert "just testing, remember to revert"
daa84ba Still can't get this right...
097f164 this should fix it
367f271 GIT :/
f46d735 bump to 0.0.3-dev:wq
b893721 ¯\_(ツ)_/¯
24be0d9 ...
f014a0c ALL SORTS OF THINGS
e648b80 added super-widget 2.0.
3a71628 perfect...
e2a8cb1 Fucking templates.
b08e489 pgsql is more strict, increase the hackiness up to 11

If you don't know how to git clone, can you even call yourself a developer?

No. Just, no.

I hate people who don't value transparent and assertive communication. I'm saying this thinking about an specific client.

This client is a boss of Web agency, and has some contractors working on their projects. I worked for them for a year, doing Web projects from scratch and also maintenance.

Then, one week, the communication stopped. No answers, no feedback, nothing. For months. They ghosted me.

I tried contact a few times with no luck. After 3 months, they started to remove me from slack, git, base camp.

And that's it. I was discarded and it seems I don't even deserved a message to be aware of that.

I don't mind to end business relationship anytime, for any reason. There are lot of reasons a working relationship would not work, and that's OK. We should have partners that are a great fit for us.

But at least say it. Ghosting is something ridiculous and unethical.

12 days of work, 12 fucking days straight and I meet the Friday deadline for this ridiculous sprint of never ending tasks.

There’s no better feeling then bringing everything together at 5pm on Friday, pushing to Git and waking out that door knowing there’s nothing more to do until Monday’s testing!!!!

Now excuse me while I go sleep my weekend away!

No Microsoft Word, I'm pretty fucking sure it's spelled Git and not Gilt.
#Preparing Code Review Docs

Some say you are not a true developer if you haven't accidentally deleted shit and spent several hours restoring that shit!

Okay, no one says that. I made it up. I idioted today. I accidentally rm -rfed my workspace directory and lost all my code.

Now I'm re-syncing stuff back into place from my remote back up.

Git ❤

Worst thing I've seen a Dev do? Blame others even if it shows in the git blame that it is his fault 😂 no equality, ego and hard headed. Wants to show every one that he's always right 😂 well good luck with karma. What an attitude lol

And this, ladies and gentlemen, is why you need properly tested backups!

TL;DR: user blocked on old gitlab instance cascade deleted all projects the user was set as owner.

So, at my customer, collegue "j" reviews gitlab users and groups, notices an user who left the organisation
"j" : ill block this user
> "j" blocks user
> minutes pass away, working, minding our own business
> a wild team devops leader "k" appears
k: where are all the git projects?
> waitwut?.jpg
> k: yeah all git projects where user was owner of, are deleted
> j.feeling.despair() ; me.feeling.despair();
> checks logs on server, notices it cascade deletes all projects to that user
> lmgt log line
> is a bugreport reported 3(!) years ago
> gitlab hasnt been updated since 3 years
> gitlab system owner is not present, backup contact doesnt know shit about it
> i investigate further, no daily backup cron tasks, no backup has been made whatsoever.
> only 'backups' are on file system level, trying to restore those
> gitlab requires restore of postgres db
> backup does not contain postgres since the backup product does not support that (wtf???)
> fubar.scene
> filesystem restore finished...
> backup product did not back up all files from git tree, like none of refs were stored since the product cannot handle such filenames .. Git repo's completely broken

Fuck my life

!student

Principles of Programming Languages teacher:

No one in industry uses git.

The same guy who refused to take semester project submissions as github links.

Also "Python is never pass by reference/id()"

I just got e-mail:

"Sunsetting Mercurial support in Bitbucket

After much consideration, we've decided to remove Mercurial support bla bla bla crocodile tears bla bla..."

So basically, Bitbucket started out as a Mercurial repository hosting platform. After GitHub's rise in popularity, they decided "hey, everyone's welcome, both Hg and Git!" Then it became Git and "okay Hg too, but shhh don't tell anyone". Now they FINALLY completed running it into the ground: "Only 1% of repositories are Mercurial" - yeah no shit sherlock, after actively hiding the fact you support it, people don't find out you support it! Surprised Pikachu! Oh congrats, Atlassian. You're so smart.

Mercurial support was the sole reason I had repositories there. I mean, for Git we already have GitHub, GitLab and others. So what's their unique selling point again? What's that, the sound of crickets? Thought so.

So after that, hopefully they change the name to "Gitbucket". Or preferably "Bitfuckit".

The year is 2019.

C++ is still one of the most powerful programming languages around..............with no centralized package manager that is widely adopted by the community that allows one to sandbox libraries from conflicts with one another.

I ain't hating, just find this funny and I love cpp

Apt get/git submodules it is!!

CEO at work has a Mac elitist as a friend who somehow indoctrinated err I mean convinced him to get apple everywhere, now the most common issue is updating Microsoft products on the Mac.....

Mac elitist guys first name is Steve lol no lie, he also services the Macs which he expects to do so when no one is around, oh and did I mention he wants us to leave our passwords on our desks LOL, he doesn't work for the company and I really really don't trust him, glad I have a git repo, and I hope he doesn't delete anything on my PC (very reluctant to leave my password on my desk, so I may just convince everyone that my Mac is fine, which seems like it's doing it's thing)

TL;DR : do we need a read-only git proxy

Guys, I just thought about something and this potential gitpocalypse.

There is no doubt anymore that regardless of Microsoft's decisions about Github, some projects will or already have migrated to the competition.

I'm thinking : some projects use the git link to fetch the code. If a dependency gets migrated, it won't be updated anymore, or worse, if the previous repo gets deleted, it can break the project.

Hence my idea : create some repository facade to any public git repository (regardless of their actual location).
Instead of using github.com/any/thing.git, we could use opensourcegit.com/any/thing.git. (fake url for the sake of the example).
It would redirect to the right repository (for public read only), and the owner could change the location of the actual repository in case of a migration.

What do you think ? If I get enough ++'s, I'll create a git repo about this.

I was asked to look into a site I haven't actively developed since about 3-4 years. It should be a simple side-gig.
I was told this site has been actively developed by the person who came after me, and this person had a few other people help out as well.
The most daunting task in my head was to go through their changes and see why stuff is broken (I was told functionality had been removed, things were changed for the worse, etc etc).
I ssh into the machine and it works. For SOME reason I still have access, which is a good thing since there's literally nobody to ask for access at the moment.
I cd into the project, do a git remote get-url origin to see if they've changed the repo location. Doesn't work. There is no origin. It's "upstream" now. Ok, no biggie. git remote get-url upstream. Repo is still there. Good.
Just to check, see if there's anything untracked with git status. Nothing. Good.
What was the last thing that was worked on? git log --all --decorate --oneline --graph. Wait... Something about the commit message seems familiar. git log. .... This is *my* last commit message. The hell?
I open the repo in the browser, login with some credentials my browser had saved (again, good because I have no clue about the password). Repo hasn't gotten a commit since mine. That can't be right.
Check branches. Oh....Like a dozen new branches. Lots of commits with text that is really not helpful at all. Looks like they were trying to set up a pipeline and testing it out over and over again.
A lot of other changes including the deletion of a database config and schema changes. 0 tests. Doesn't seem like these changes were ever in production.
...
At least I don't have to rack my head trying to understand someone else's code but.... I might just have to throw everything that was done into the garbage. I'm not gonna be the one to push all these changes I don't know about to prod and see what breaks and what doesn't break
.
I feel bad for whoever worked on the codebase after me, because all their changes are now just a waste of time and space that will never be used.

I took this contract and made the suggestion that we backup to the cloud and create a private repo on GIT. Client said no, local should be fine, they don't want someone stealing their code. I said okay fine.
AC just went out in the server room and they apparently had a leak from the AC to the power supply which they happened to put on top of the rack servers and switches. I'm surprised that place didn't catch fire, might be to early to call it.
All this on a Friday and we were 2 weeks away from launch party.
Not my fault, I clearly said we backup to cloud and use GIT on private repo.

My team is using Teams to share code snippets. And because I know they don't (know how to?) use git remotes, I have to share my code through Teams as well.

We're no strangers to code
You know the conventions and so do I
A full commit is what I'm thinking of
You wouldn't get this from any other dev

I just want to tell you about my problem
Gotta make you solve it for me

Never gonna git you up, never pull you down
Never gonna rant around and rebase you
Never gonna merge your branch, never gonna say $#@*!!
Never gonna risk a cry and build you

I've seen many devs doing crazy things in my entire career till now. But this one dude stands out.
He used to:
- Push binaries to git repo
- Use some old libraries which were used during Indus Valley civilization
- Had no sense of database and used to delete random data from it and call it as TESTING (Thank God! I never gave him prod access)
- And on top of this, he had an ass full of attitude!

Just imagine this dude (ಠ∩ಠ)

auto.self.whatever.rant()

A few years ago, we had a lesson on git and stuff, and we had to create our first repository and push something on it to get familiar with the thing.

Our teacher jokingly said at the end "And always remember, no password in a repository!", and I thought to myself "who can be dumb enough to do actually do something like that?"

Now, guess which piece of shit had to reinstall two of his fucking servers because of security issues coming from not one but github repositories?

When I come back after a week :
Git commit -a -m "changed a lot, no idea of what I changed"

FFS stop squashing commits. If “updated comments” is what the commit was it should show it in git blame. If “fixed null check” is what the commit was it should show it in git blame.

There is no reason to have “ticket-234 service revision” beside 1000 lines of code. How does anyone justify this loss of git info for the sake of “clean history”? Nobody looks at your history and says, “That is bloody clean git history I should write home about it.” People do however look at the code and say, “I wish I knew WTF they were trying to do on that line.”

So ive been messing around with my Google Home.. because having a voice activated weather station is cool and all, but as a developer it needs to be useful no?... and Raspberry Pi, cause you know, we cool kids have those sitting around doing nothing useful.

But back on track, getting these two to actually work together, and that almighty moment you can say "Hey Google, Deploy Project -X- to the Pi" and the Rpi just kicks into gear and pulls down the latest master branch from Gitlab for the correct project is mind boggling.

No more ssh + sudo git pull !!!

Disclaimer: i didn't pay for that Google Home, but its in my house, listening to my TV, so i may as well use the damn thing.

One fine day, at work, I was doing one of my favourite things.

git push origin test:mainline

And it prompted for my credentials. I gave them and continued as per yooozh..

What I didn't realise then was that I had used my personal github credentials instead of my official account's!

Oops.

Day 3 - and no one has noticed yet...

Oh no, we have a git hacker.
haha, I literally just screenshotted this to send to a friend...

Just had a fire at work.
git add, git commit, git push.

No one was hurt. But, the fire was in a server room and the git server is down. At least the halon deployed successfully.

The off site backup should be up in 20 mins. I wonder how often they pull the repo.

Today after working 7 days on a project. My coworker comes up to me and says he pushed everything on the server and that he cleared git to make everything cleaner. When he did I that he forgot to change some vital things. Now we have a black website running and no backup code. I was so passed at him. Luckily a stressbal works really well. I threw it at is head and felt immediately better. Sad part need to do it all over again.

git push origin stupid-long-feature-name
git pull origin develop
*Checks through all changes. No major conflicts. Accepts changes.*
npm test
*4 failing tests, none of them in pieces that I touched for my feature.*
*That's funny. QA was loaded from the develop branch, and everything works.*
*Actual data has dates from today. Expected data has dates from a week ago.*
*examines tests*
Why are all these expected dates hard-coded‽

tl;dr The external development team committed 4 tests that would only ever pass on the day they were written.

One of my colleagues held a very short, literally 5 minutes, interview today. The candidate was looking for an android developer position.

Me: Done already?😕
C: Yep. Had enough.
Me: How come?
C: I asked him if he has any apps on the store? No. Any public git? No. Any apk? No.
C: Ok what experience do you have?
Dude: I worked on a app similar to imdb 4 years ago. I made a page for it.
C: *Page* *triggered* *internal screaming* 😂
C: Ok and since then?
Dude: Nothing.
C; Ok, we'll call you.

Best ot luck in your android dev career mate. Never gonna hear from us.

How can you come to an interview and be so unprepared. Was he delosutional or something?😕

Any doctor here that happens to also know git?
What's with recruiters looking for doctor and git?

Boss: some consultants worked on this feature extending some legacy code
Boss: it's 90% done
Boss: they used FTP. It uses iframes and we fired them when they couldn't get the frontend modules working in sync with the backend.
Me: git checkout -b herewegoagain
git diff-tree --no-commit-id --name-only -r 666w3wl4d
*copy output list of files to sublime text 3; select all lines; add to each:
gitk --follow [filename] > src/.notes/herewegoagain/[filename].diff
*examines....
Me: It's -10% done. you'll know I'm almost done when I enter the fugue state. You'll find me at this address. Give me this USB stick and a 4 pack of redbull and I'll do the merge.

Working on a school project, a teammate created a git repo, gave us all the link, but no push access, told him about it, I gave up explaining.

I still dont have push access after half a day.

Also another team member doesnt know how to write code.

I assumed that people that got accepted in a master that has software development in the title have the basic knowledge or the background at least. Even though there is a separate master especially for that, to teach you software development.

You lousy fucking test class of an ass wipe,

TLDR; it fails and it passes all at the same time.

So during a deployment, one of the pre-deployment test classes fails, not something anyone has worked on so figured I run it manually to see what’s going on, but no the shit of a thing passed second time around.

Now because we can’t deploy without 100% of the test classes passing so I have to organise another deployment which it fails again. Fuck this,

Unprotects master

Git checkout master
Git merge dev
Git push master -f

Protects master

Skrew this!

Well would you look at that, it works now 😰

Stopid mf fat fingers, worked 2 weeks building a design system and 2 hours ago I accidentally shift deleted the scss folder and lost every fcking file, no git, no backup, no nada,guess what, tried to recover the files with 2 Permanently deleted file recovery softwares and from fcking 20 files, 17 were corrupted and weren’t readable, I and my designer friend use a folder sync app, the fcking app synced the delete and she lost the files aswell, fooockiinggg shieeeet, to my don’t know how where luck I managed to recover the copiled javascript chunck from my vue app that had the css styles embeded in the file, you know where I found the js file? iN ThE fcking cache of google chrome. Today I almost broke down to tears, but nonetheless it was a reeee moment for me.

"Tar up your projects as version control."
- CS teacher

I understand git is hard (just the awkward syntax) and not part of a curriculum, but can it at least be suggested? A whole year later, I found out about git and it has made CS projects so much easier.

git commit -a -m "No more tape archiving"

Today the Git for Windows updater asked if I wanted to let Git decide on the naming of my default branch... Hell no snowflakes!

that moment when you were still new to git commands and just typed in random commands while thinking of a stupid dog meme saying I have no idea what im doing then accidentally pushing something in prod and had no idea what to do cause the lead dev was not around... aahhh those were the days

Guys, quick question!
Why do people argue wether it’s „gif“ or „jif“ and no one ever thought of calling git „jit“?

Fucking first rant here:

So we tried to teach Two new colleagues to typescript and git and testing and stuff and we have a SPOC “which claimed to be very technical”. The SPOC’s task is to keep an eye on the work, and today we have had a review...

After two weeks, the created multiple branches into our git, all with one commit of 400 LOC changed, no merge requestet, issue in Redmine set to “closed”.
Well, by the way they were supposed to write Unit tests for our app.
But I thought, ok, we’ll check their branches.

Their tests all passed (cz) but man, the app didn’t and on compilation there were errors, the app is broken. Damn.

Is it really so far off, that even of They wrote tests, that the app should still work?
AND I THOUGHT IT IS COMMON SENSE. Damn!
Guess how needs to fix it

I dont know what to feel anymore.

Got hired directly without an interview into 'Data-analytics' department in fortune 500 company. This is my first job. Got hired because this company want start a website that cost millions.

Even though I am junior, I can see that this company has no idea about software development at all. No git server, no code review, no quality assurance and no proper workflow. No senior developer to guide us (junior dev) too.

There is one 'senior' consultant that work on automation project here but he just focus on his work and don't help us directly too.

The contract is about 1 year. Still got 11 months to go :/

Me: man, who the f*** wrote this?

Dude: No idea.

*Git blame*
(Dude 2016-04-14 12:00:00)

:/

*reverts a layout file to the one in git*

*gradle fails, no components found, electricity goes off, office catches fire, the world ends*

Already hate everything about this job. Not even a week has passed.

PHP5, CakePHP 2, No git, no nothing.

If git was written in english or in ancient greek it made no difference. It's everything counter-intuitive and you have just to learn commands by heart and google the errors. Because nothing makes sense, even if you know how it works and you used it for years

"let's use git for this game jam"

Wait! Don't go! I love git and use it on every project I work on! You'll have to hear me out here.

This was 4 years ago, at my first Global Game Jam. Every jam and game I'd worked on up to that point, I was the only Dev; no need for git, as backups were more than enough. I joined a group with high hopes for the game jam, with three coders and a proper art team.

The entire jam was "1 step forward 2 steps back", as git somehow constantly overwrote code as fast as we could write it.

By the end of the jam we barely had anything to show for our hard work. The takeaway isn't even about git. It's simply to never work with other people. Git is a great protocol but it can't stop people from accidentally fucking other people over. Every jam since, I've worked on my own and had a far better time of it.

So on a scale from 0 to creating a bat script to delete folders and fully re clone the repo's you just deleted because you can't be bothered learning git, how lazy are you?

I'm in the latter...

Spent 5 hours working on a solution for a hash difficulty comparison/scaling algorithm. after a bunch of different iterations and approaches, I find that my problem can be solved by the attached equation. Its such a simple answer but no way in hell would you be able to discern the amount of time and brainpower that was put into it. The git commit is literally 10 lines of code total, but I guess its not about the amount of code, but the time spent thinking about it thay counts?

Doing office work now, no technical tasks... but after working with MS office a while, I'm thinking to add c:\users\me\documents folder to Git.

I had to migrate ~100+ svn repos to git that were "useful" according to the client but found out that there were a lot of projects (+6yrs old) with only one commit message "--no-commit-message" and i'm not even joking...
And then I had to explain to these "devs" how to use fucking git with eclipse (+they all use light theme...) cos' terminal or gui client is too complicated

And then I saw their "Java libs" with ~3k line of spaghetti

Do you even dev bro?

Git pooed

Boss: "we're going to take over a project from another company. that's what we know so far - any other questions?"
Me: "do we get the history (svn/git) or just current source? unit tests?"
Other company: "no history for you. no unit tests - app was only tested manually"
Me: *sigh* :'(

My new co-worker is extremely stressing. I have to give small tasks so he won't forget to do anything. I also have to explain what he has to do in detail, give him the full solution, and show him exactly how he has to do it.

And he has no idea how to use git. He makes a feature branch and pushes all his various, half-finished features into it and makes a pull request.

And then I still have to refactor his crappy code everytime cause he uses variables like $data, $accA, $accB, $accZ and forgets to use the definied color variables in sass.

I literally have to do my work and his as well -_-

Our project at work goes live in 3 weeks.

The code base has no automated tests, breaks very often, has never had any level of manual testing

will not be releasing with any form of enforced roles or permissions in our first release now due to no time to enforce, however there is a whole admin api where you can literally change anything in our database including roles.

We also have teams in various countries all working separately on the same solution using microservices with shared nuget packages and they aren't using them properly.

Our pull requests are so big - as much as, 75 file changes - in our fe app that I can't keep up with it and I honestly have no idea if it even works or not due to no automated tests and no time to manually test.

We have no testing team, or qa team of any sort.

Every request into the system has to hit a minimum of 3 different databases via 3 different microservices so 1 request = 4 requests with the load on the servers.

We don't use any file streams so everything is just shoved in the buffer on the server.

Most of the people working on the angular apps cba to learn angular, no one across 2 teams cba to learn git. We use git so they constantly face problems. The guy in charge has 0 experience in angular but makes me do things how he wants architecturally so half the patterns make no sense.

No one looks at the pull requests, they just click approve so they may as well push directly to master.

Unfinished work gets put in for pull request so we don't know if the app is in a release state since aall teams are working independently, but on the same code base.

I sat down and tested the app myself for an hour and found 25 fe only issues, and 5 breaking cross browser issues.

Most of our databases are not normalised. Most of our databases make no sense. 99% of our tables have no indexing since there is no expertise with free time to do it.

No one there understands css properly. Or javascript.

Our. Net core microservices all directly use ef in the controller actions so there is no shared code there.

Our customer facing fe app is not dry because no tests so it was decided it was better this way.

Management has no idea on code state, it seems team lead is lieing to them about things like having any level of tests.

Management hire devs that claim to be experts but then it turns out they have basically no knowledge of what they were hired to do, even don't know what json is or the framework or language they are hired for, but we just leave them to get on with it and again make prs too big to review.

Honestly I have no hope that this will go well now but I am morbidly curious to watch. I've never seen anything like the train wreck that we are about to get experience.

Well paid java dev. But the HW/SW-Stack is awful.

Monitor: single 1600x1024
5yr old notebook, old i5, magnetic hdd
Forced to use windows 7
No maven server
No CI server
SVN but no git
Eclipse, no intelliJ
No sonar server

There are days where I just can't take it anymore.

We've got this legacy PHP system that doesn't really run anywhere else than on it's server. It's not configured with git, and there's no pipeline. Just plain old SSH. How would you go about managing it?

Client: Please add feature x in "here"
Me: Adds feature x in "here"

Fast forward to QA

QA: Test for feature x failed. Feature was added in "here" but is not in "there"
Me: There was no request to add x in "there"
Client: Feature x was already supposed to be in "there", you might have removed it.
Me: *Checks file where feature would be added.
* Git blame show no changes since received we the project (one major release back)

Lying cunt. I'm sick of your literally incomprehensible tasks giving government fucks, speak human language not overhead driven bureaucracy-jargon

In our company, all devs are using windows notebooks with the brand Schenker.
And they get bluescreens regularly. The bluescreens are currupting git repos and other data. Seems to be caused by some driver issues with trackpad but no fix for that yet. Happening for years now...
If someone hits the table and gets angry, he probably got a bluescreen again...

Long meeting with a coworker presenting a huge, complicated system to track changes to configuration files.

Basically, whenever someone needs to change a config file, this person is supposed to manually enter an entry to a changelog file, and the build system is supposed to give an error if the person forgets to update the changelog.

At the end of the 1 hour long presentation, I raise my hand and say: "we are already using git for our config files, look:

$ git log <filename>

here you can see the list of changes to the file. What you describe is already available, no need to reinvent it."

Long akward silence in the room.

The presenter: "okay, I will look into that. Any other questions?"

Haven't heard about that project since then.

Merge VS Rebase:
- Did you pick a side?
- Practical tips? Like dealing with merge conflicts
- Have you ever regretted using either?

My answer
* My team squash-merges all branches to master so we don't really care what the branch history looks like. Master history should be pretty - but a branch history can be ugly and filled with a dozen commits.
* Practical tip 1: use `git config rerere.enabled true`. rerere stands for "reuse recorded resolution" and this means if you rebase often you don't have to resolve the same merge conflict twice.
* Practical tip 2: use `git commit --fixup oldcommithash` and then rebase with `--autosquash`
* I like using Rebase. But I have regretted the amount of time I've spent on trying to rebase old branches with many commits only to give up and to `git rebase --abort` since I realised I couldn't handle trying to reapply all the commits chronogically as the changes in the 1st commit were no longer relevant.

Me: we should take this project a little more serious, follow the coding standards and please let us use git!

Pal: Oh sure.

//made a new repo and the first commit, sent the link and prepared everything (Granted access etc.)
//2 weeks later

Me: What's up, I already got quite some commits and you haven't pushed anything so far.

Pal: Pushed? what do you mean?

Me: I'm the talking about the git repo, I'm the only one contributing.

Pal: Oh yeah git, I installed it but I have no idea how that stuff works. I opened Git gui but i don't know what I'm supposed to do. I got everything in the Dropbox tho.

Me: ... ... ... FUUUUUUUUU WHAT THE FUCK MATE ARE YOU SHITTING ME, THE HELL DO WE HAVE GOOGLE FOR AND WHY DIDNT YOU ASK, LIKE WTF SERIOUSLY I EXPLICITLY TOLD YOU TO USE GIT.

😣

As a Dev in college working for teams in college, I don't really have a need to use git, since most of 'self proclaimed prestigious programmer child prodigies' I work with have no idea what it is; but I use it anyways as good programming practice and ease of backups.

So I tried using a GUI client after months of the git bash, and even though I looked up a few tutorials (was embarrassed the whole fucking time). I ended up adding, committing and pushing via bash.

Can anyone explain me how is the GUI client helpful in large projects and stuff?

What the hell is wrong with using GitHub, or Git??? A client told me he’s concerned because it’s been, in his words, “compromised” and the admins can “see our code for trouble shooting purposes” and he doesn’t feel comfortable with that…🤨 like…no one wants this code my dude, like the fuck!?! We’re already using a skeleton project from someone else’s git, yet you dnt want this project on there??? Ooooor, is it because you dnt know how to use it??? Nor do you want to take the time to learn it??? 🤨 fuck boy. 😡😡😡😡😡😡🤬🤬🤬🤬🤬🤬🤬

I started my actual gig as CTO of construction group (Innovation Hub) a year ago. And it was a hell of a ride, implementing kind of a scrum-ban for project management, XP, peer-reviews, a git-flow, git commit message formats, linters, unit testing, integration tests, etc...
And it's the fun part because with the CIO we had to drive the board to do A LOT of changes in their IT/Innovation drive.

But in one year there is a lot of KPI that went up :
* Deployment: When I arrived it took three stressful days to deploy a new version of one application, once a month. Today we do it every week, and it takes three annoying hours.
* We had no test. NOTHING! Today we have 85% code coverage for the unit test, and automatic integration tests run by our CI server every day.
* We had almost no documentation. Today our code is our documentation (it automatically extracted and versioned).
* We had 0 add value in the use of git. With commit messages as "dev", "asked task", inside jokes and a lot of "fix" and "changes". Today we have a useful git, and we even use it to create our deploy changelogs (and it's only mildly annoying!).
* More important, the team is happy! They get their purpose, see betterment in their tech mastery. They started doing conception, applicative architecture, presentations, having fun.

There is still a LOT of bad things we are still working on, and trying to solve (support workflow and betterment). But seeing what they already did, I'm so proud of my TEAM! I'm a fucking asshole, workaholic, "just do it" kind of guy. But they managed to achieve so much. Fucking PROUD!!

It's sometimes really anxiety inducing thinking that all data could be gone, if somebody decides to kill/discontinue/crash [see gitlab shitting 6 hours of data due to fucked backup strategy and shitty seperation of servers] your account/service, be it server, git-repos, backups, chrome syncs, games, music, sim card, ..

But there's simply no way of having a backup of absolutely everything (ignore DRM) - especially automated and abstracted away from you, so you don't have to do all that shit yourself

Well... I once accidentally deleted a classmates entire assignment. Basically we were working together on one and we had the code in Github, I had named the repo after the module code.
He was having some weird git issues and I thought it would be easier to just delete and re-clone on his machine. You can probably see where this is going.

Me: rm -rf <DIR NAME> Enter
Him: wait, which folder did you just delete

Turns out he had the repo cloned inside another directory with the EXACT SAME NAME, which also contained his previous assignment, the only copy of it in the entire universe (it was a group project and they did it all on his laptop with no source control, which i found hilarious).
It wasnt so bad since that assignment was already submitted and graded, but a bit of a fail on both our parts.

I've been trying to get my job to start using Git cause they currently don't use any version control. So today I told my supervisor that I was going to set us up our server so we can host our own repositories and he was like no need we will just set your computer up so you can vpn in from home. I'm like wtf? why go through so much trouble to set that up? That still doesn't solve the problem of accidental file overwriting.-_-

So I just was invited to look at an internal issue at a company that has modified BEM styling rules for their website, because the website started looking very weird on some pages..

I instantly knew that someone had to have fucked with them, because theres no way margin--top-50 all of the sudden isn't working.

Looked at their git history and apparently a senior approved a juniors styles change, where he modified things like margin--bottom-0 to be 500px or block--float-left to be float: right in specific containers with an id like "#uw81hf_"

WHY DO YOU APPROVE THIS GARBAGE WITHOUT CHECKING IT?! AND HOW DID THIS PASS A SECOND CHECK?!!! WTF

Just met a startup that has a programmer intern but no IT supervisor. I felt so sorry for her that I decided to show her a few cool tools that she can use in her work.

She was still using Xampp, Google Chrome, command prompt and paper trails (for all of the passwords she had to manage to different accounts)

Shown her how to use Docker, Git Bash and WSL, FireFox Developer Edition, VS Code (if she decides to not use that unregistered Sublime Text editor) and LastPass (personal preference).

Best of luck!

A rant from git,

Why do developers always PUSH and PULL me around. I mean they don't just do it once or twice. No they COMMIT to doing it over and over. I try to REBUILD myself, but it is hard getting pushed and pulled constantly. I don't know the ORIGIN of where it started, but gosh I wish the bullying never started!

When, for the 100th time, you see the git commit comment:
"All work and no play makes Jack a dull boy"

So.. I'm giving one of my employers webapps a visual refresher, new company branding and whatnot.

And then I stumbled onto a check that is not returning what anybody expects, and, well , I'm busy fixing things, yeah..? so I go digging.. 🤔

```
function isDefined(obj) {
return !(typeof obj === "undefined") || obj !== null;
}
```

Here's the fun part, these particular lines have been in the code base since before 2017, which is when my Git history starts, because that's when we migrated projects from Visual SourceSafe 6 over to Git. Yes, you read that right. They were still using VSS in 2017.

I've begged and pleaded with my last 3 bosses to let us thrown this piece of shit out our second story window and rewrite it properly. But no, we don't have time to rewrite, so we must fix what we have instead.

I lost 4 hours of my life earlier today, tracking down another error that has been silently swallowed by a handler with its "console.log" call commented out, only to find that it's always been like that, and it's an "expected error". 🤦

Please, just fucking kill me now... I just, I can't deal with this shit anymore.

Pro of not using Git

* No git conflict

Love my new job but fuck they are way behind in any kind of modernization.

Just saw a demo over zoom where someone was showing the team how to change the margin on an error page.

They literally changed the HTML directly in prod using the VIM. So first of all no web modernation because there was no build, no deployment, not git, no pipeline - NOTHING!

This project went from 40 people to around 200 in 6 mos. You can't have all these people in prod just making fucking changes.

If this job did not pay 110k a year I would bail.

So I did a code review for a colleagues pull request and I've noticed that he hasn't written the PHPDocs for a lot of the classes and functions. One minor thing I wrote is to add the author for the class.

About 2 mins after writing that comment he came over to tell me why should he write the author in the comments when people can just go look at the git commit logs. I was like WTF? I asked why would he do that, his answer was that if there's an issue, we can just use git blame to identify the author. To me that makes no sense as git blame isn't supposed to be used like that.

It's guys like these are the ones who don't document anything whether in an online document or even in code. And they just make work harder for the rest of us.

Alright ladies and no so gentle men...

The time has come for me to ditch dropbox (Because fuck wanting to use ext4 and also have some spare CPU usage when syncing a single fucking file) and migrate everything from my art storage to some old prototypes into private github repo's...

Prepare to see a shit tonne of rants about me forgetting how to git and all that kinky shit...

Wish me luck *salutes*

Aws Lambda and serverless framework. Yes FaaS is cool. Love it. But it is pain in ass when you have the only way for you deploy is zip the fucking code with all the dependencies. Comm'on AWS you can do better. Look at azure functions. Please give me a git deployment support. Please I beg. Each test iteration takes like for ever. Also no proper local emulator. Fuck you AWS. Fuck you serverless.

I may have convinced my boss to start using Gitea to manage our git repos! 😆

Right now we have a NAS with bare repos, so we have no access rights, no overviews, no forks, no issues, no pull requests, nothing! 🤐

Now it's time to pray to the gods for his decision. 🤞

No wonder why Google Chrome takes up alot of RAM when running, I've just seen chromiums dev requirements:

System requirements

- A 64-bit Intel machine with at least 8GB of RAM. More than 16GB is highly recommended.

- At least 100GB of free disk space on an NTFS-formatted hard drive. FAT32 will not work, as some of the Git packfiles are larger than 4GB.

- An appropriate version of Visual Studio, as described below.
Windows 7 or newer.

So... My boss is "hard working", meaning that she'd rather edit and upload a html file every morning at 5am for the last 5 years and manually send a push notification notifying the user that the new file is up than learning a little bit about automation (cron? IFTTT?) and even after letting her know about those options she has "no time"

She'd rather keep source code (pug, sass), manually build on local computer and upload to live servers instead of learning git and letting me setup once and for all CI/CD

SERIOUSLY!?!? NO TIME!?!? But there's time to do things at a turtle pace like in the 90s... 🤦‍♂️

When you start a new project and you think that you will no longer have problems with git.... after one week you see yourself sending classes to your colleagues via mail to push them for you. Shit man

Hmm. This code needs refactoring.
*recodes on Local and uploads*
Works on my branch.
*git push origin master and merge*
Works on Dev.
*deploy to Test*
Works on Test.
*deploy to Live*
Doesn't work.
*compares Live to Test, Dev, and Local*
No f$@%^%%$# difference!?!!

*quits development and lives under a bridge*

Have you become a replacement tool doing manual and menial IT work to bridge the lack of a proper IT process and streamlining?

I've worked for such companies and it's super annoying.. companies that zip projects to Google Drive instead of using a VCS.. not even having a drawing board or proper office chairs.. not even a cafeteria.. companies using Subversion instead of Git, no project management systems nor software, no JIRA, shit written down on printed paper,.. the list goes on.

A nightmare, really. Like developing in the 90's..

JUST DO GIT!

Git on VS doesn't want to ignore the files I've added in the .gitignore.

Still no shell for command line.

Well, looks like my changes will be filled with DLL files.

Last job I was in, dev boss would ask to send him snippets of code through email for review...

...they used no git or source control

I quit after two weeks.

macOS fuckup continued. Today I used a camelcase name for some new file and a directory. Later I didn't like it and wanted to change to lowercase. Pushed it to bitbucket: now I had both versions! Hold my goji berries, what's going on? Maybe some git config screw up? After a bit of fiddling I remembered an old Linus' rant on Apple's file system when they wanted to adopt case insensitivity. So wait, did they actually do that shit? I thought I was on a unixoid, bastardized BSDish system, that apart from all the oddities that Apple bestowed on it, that there was still some sanity left... But, no there isn't. AFP really defaults to case insensitivity.
I have no words.
So switched to my Debian, where I resolved the duplication in two secs. Now Linux feels even much more comfy and home.

GIT LOG VERSION 110
---------------
a9c2934 I don't believe it
fb8d2e6 I am Root. We are Root.
6be9078 FINALLY FIXED THE FUCKING BUG IN THE CODE, DO NOT EVER EVER FUCK ME AGAIN YOU MARON
3d08a88 THIS IS THE FUCKING WORKING VERSION
013faed THIS IS NOT WHAT YOU ARE LOOKING FOR, GO TO A PREVIOUS COMMIT
af5d013 We'll figure it out on Monday
49e238b de-misunderestimating
a40351b happy monday _ bleh _
a5f345d Fixed unnecessary bug.
485a26a pay no attention to the man behind the curtain
c4fcbde s/import/include/

Am I the only developer in existence who's ever dealt with Git on Windows? What a colossal train wreck.

1. Authentication. Since there is no ssh key/git url support on Windows, you have to retype your git credentials Every Stinking Time you push. I thought Git Credential Manager was supposed to save your credentials? And this was impossible over SSH (see below). The previous developer had used an http git URL with his username and password baked in for authentication. I thought that was a horrific idea so I eventually figured out how to use a Bitbucket App password.

2. Permissions errors
In order to commit and push updates, I have to run Git for Windows as Administrator.

3. No SSH for easy git access
Here's where I confess that this is a Windows Server machine running as some form of production. Please don't slaughter me! I am not the server admin.
So, I convinced the server guy to find and install some sort of ssh service for Windows just for the off times we have to make a hot fix in production. (Don't ask, but more common than it should be.)
Sadly, this ssh access is totally useless as the git colors are all messed up, the line wrap length and window size are just weird (seems about 60 characters wide by 25 lines tall) and worse of all I can't commit/push in git via ssh because Permissions. Extremely aggravating.

4. Git on Windows hangs open and locks the index file
Finally, we manage to have Git for Windows hang quite frequently and lock the git index file, meaning that we can't do anything in git (commit, push, pull) without manually quitting these processes from task manager, then browsing to the directory and deleting the .git/index.lock file.

Putting this all together, here's the process for a pull on this production server:
Launch a VNC session to the server. Close multiple popups from different services. Ask Windows to please not "restart to install updates". Launch git for Windows. Run a git pull. If the commits to be pulled involve deleting files, the pull will fail with a permissions error. Realize you forgot to launch as Administrator. Depending on how many files were deleted in the last update, you may need to quit the application and force close the process rather than answer "n" for every "would you like to try again?" file. Relaunch Git as Administrator. Run Git pull. Finally everything works.

At this point, I'd be grateful for any tips, appreciate any sympathy, and understand any hatred. Windows Server is bad. Git on Windows is bad.

git commit --amend --no-edit
git push -f

Dear git, why are you lying, there's no changes in that file, you say that yourself...

Can a sysadmin start Node web design?

I'm a Linux automation admin, and I always look at my friends developing nodes websites with poor UI and UX. I'd love to fix that but have no idea where to start from.

Any idea or git project / advice on where to start from?

Cheers!
~ exit

Made this amazing discovery in my project. Made sure to commit the code in Git to show a demo to the manager.

Could not find the code at all when it was time for the demo. Checked all the commits to find out, nope, no luck.

Later realized I committed that code to special branch :/ And I totally forgot about that :(

Tl;Dr Im the one of the few in my area that sees sftping as the prod service account shouldn't be a deployment process. And the ONLY ONE THAT CARES THAT THIS IS GONNA BREAK A BUNCH OF SHIT AT SOME POINT.

The non tl;dr:

For a whole year I've been trying to convince my area that sshing as the production service account is not the proper way to deploy and/or develop batch code. My area (my team and 3 sister teams) have no concept of using version control for our various Unix components (shell scripts and configuration files) that our CRITICAL for our teams ongoing success. Most develop in a "prodqa like" system and the remainder straight in production. Those that develop straight in prodqa have no "test" deployment so when they ssh files straight to actual production. Our area has no concept of continuous integration and automated build checking. There is no "test cases", no "systems testing" or "regression testing". No gate checks for changing production are enforced. There is a standing "approved" deployment process by the enterprise (my company is Whyyyyyyyyyy bigger than my area ) but no one uses it. In fact idk anyone in my area who knows HOW to deploy using the official deployment method. Yes, there is privileged access management on the service account. Yes the managers gets notified everytime someone accesses the privileged production account. The managers don't see fixing this as a priority. In fact I think I've only talk to ONE other person in my area who truly understands how terrible it is that we have full production change access on a daily basis. Ive brought this up so many times and so many times nothing has been done and I've tried to get it changed yet nothing has happened and I'm just SO FUCKING SICK that no one sees how big of a deal this. I mean, overall I live the area I work in, I love the people, yet this one glaring deficiency causes me so much fucking stress cause it's so fucking simple to fix.
We even have an newer enterprise deployment. Method leveraging a product called "urban code deploy" (ucd) to deploy a git repository. JUST FUCKING GIT WITH THE PROGRAM!!!!..... IT WAS RELEASED FUCKING 12 YEARS AGO......

Please..... Please..... I just want my otherwise normally awesome team to understand the importance and benefits of version control and approved/revertable deployments

OH GOD WHY???

Why is there `git stash pop` but no `git stash rock`? Come on, man!

Follow up to the follow up rant: ubuntu broke.

I tried searching for my git client I had installed: not found.

: Git status
Command not found (even though I’d used it less than an hour earlier)

*restart to see if that fixes it*

My laptop: STEP RIGHT UP STEP RIGHT UP LADIES AND GENTLEMEN, TAKE A LOOK AT THIS WONDERFUL TTY LOGIN SCREEN WITH NO GUI WHATSOEVER. THANK YOU THANK YOU VERY MUCH.

Why use git, do it simple, send me your changes by email and I will merge it.
Why split split source code (js) into different files, use one so we will no have trouble about load order.
Use the same user account for github/gitlab/bitbucket/etc. So we will no worry to setup access permisions.
Use Dropbox/Drive for version control.
We will test the whole system until the end when all is finish.

A few years ago I worked at company specialized in Magento(eCommerce) and Magento was changing their licensing model. At the time they had 3 Versions. Community(free), Pro and Enterprise.

They decided to ditch Pro and either make all migrate to Enterprise(with a discount) or go community which wasn’t really compatible. So some shops were in need of a more or less complete rewrite.

My hdd crashed literally the day before but hey no big deal everything is 99% done and on staging. So I had a Trainee at that Time and thought the last few crappy things could be done in pair programming so he can learn a few things.

But fuck him! That motherfucker! He managed to WIPE the staging server and no that was at a time without gut and no SVN. That dipshit just deleted 2 months of work because he thought it was a good idea to SYNC his empty project to the staging system.

Oh god I nearly stabbed him. He did that shit out of his own mind even though I told him a dozen times what would happen... we had to do the whole thing again with me sitting next to him watching every stroke he made.

Guess he learned something while inward silently raging the next weeks.

the "advantages" of being ignorant about version control

Updated my personal site to use bulma CSS framework last night. Pushed it all up, then realised github pages doesn't do npm install before it builds the site. So there was no CSS for a bit.

The only way around was to commit node modules folder to git repo. Feels wrong but better than having no CSS.

I guess that's what happens when you use a free service 😁

incompetent fucks giving no shit about agreed git flow

merging directly to master
complaining about conflicts and not willing to solve it themselves

Until today, I had assumed deploying stuff to prod would NOT be one of my responsabilities in this company. Apparently that's not the case.

Had to deploy my code and pray it didn't break anything. Why is this a big deal at all?

Well you see, there is no repository. At all. No git, no svn, not even duplicate folders. No tests, no pipeline. Just a bunch of CPanels.

Had to manually copy files and folders from the development site to the production site and partially copy a database. "Just drag and drop" were the instructions I was given.

As if using CakePHP2, PHP5 and having to parse fucking Excel files wasn't bad enough, now I have to deal with one of the worst ways to deploy code.

Fuck it, I'm switching on the looking-for-job flag on linkedin.

Studiying CS in Germany, learning about CVS, SVN and clearcase....but no fucking word about git!?
Anybody using clearcase today ? Never Heard about it before