"Don't use git, it is too complicated and we don't have time for this."

2 days later the same person made changes directly on the FTP which I later unknowingly overwrote.
Take that you imbecile!

Things I regret immediately after doing it:
1) Masturbation
2) Overeating
3) git commits

*Overhearding Convos*

A : "Dude, have you tried vim? It sucks!"

B: "I know right, why do they have to make it so hard to use..."

Me whispering : Git Gud Boi...

My fellow coworker's commit history of last 24 hours. And my boss was surprised when I told him I'm leaving the company..

Guy from work: "I have a messy coding style ¯\_(ツ)_/¯".

No, you have a bad coding style. Your repetitive uncommented spaghetti code isn't an artistic expression of your quick imaginative mind jumping from thought to thought. It's a horrible mess that shows me that either you can't do any better or you don't care.

My designer made this after overhearing a conversation DEVS were having.

You can hate me: as a 34 year old php developer, i've never used git in my workflow...
I plan to start today using it on one of my personal project (only because i have arrived at "backup-49.rar")(yes i develop on windows).
Finger crossed

3 Easy step to learn and use git :
1. git commit
2. git push
3. git gud

Working on a group project for uni and this dude asks me "why would you ever use github instead of google drive?" because git gud you cunt

Some devs like to write meaningless or too general commit messages.

Stop it. Get help.

Call 0800-GITGUDBOIII where real experts talk version control.

Git gud...

Seriously, get comfortable with Git, it'll make your life a lot easier.

I tell a colleague, "Hey, could you make your commits more meaningful? A commit message of '.' helps nobody.".

He then uses 'no message' for his commits.

Also, commits every 30 seconds. I know commit often... But is that really necessary?

Why.

what you gits
^_~

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.

You know, one of my fav ranters constantly shits on one of my main languages :P which is Java. But shit I would lie if I said that I have not learned something from what he has to say. Truth be told I am aware of the pitfalls and bad design decissions of a lot of my favorite langs: Python, PHP, JS, Java, Go etc. And I think it is benefitial to everyone to understand the things that our fav stacks fail at doing in order to become better devs.

So lets give a round of applause to those angry mofockas that make us see the shit that is wrong with what we use and learn more from each other.

Just turned off the PC and realized i forgot to commit and push

I have 99 problems but a merge conflict ain't one of 'em

"Hello sir, do you have time to talk about...."

Shut the fuck up. Sit the fuck down. Name your stack. I know how to fucking work with it. If I did not select it it is because it was not the right choice. I did not spent 4 years teaching myself to code AND later on obtaining a B.S in Computer Science(another number of years) as well as obtaining industry grade experience for you to tell me what I should use.

I've now for months been lurking on this awesome app and I love the community. I've been trying to self learn coding but kept hitting a wall. But now i'm starting in school to learn coding and i'm so exited to learn it and be a part of this awesome community.

*cracks knuckles*

Boy was I happy to see this when I opened devRant up.

So for starters, more group projects are necessary. Many reasons why. To begin with, it allows for more complex programs than getting some input and printing some shit out. It also develops interpersonal skills (I hate people too, but when you go out to look for work you'll be with them, so better get used to it soon). If a platform like GitHub is used, it's easy to track who did what, and see what each person in the group did, so it should be fairly easy to discourage lazy asses.

Beyond that, stop giving us half completed assignments and asking us to fill in a function/method. Yes, it will take longer. But one doesn't learn to program by doing the minimum required work, you've got to crash and burn a lot in order to git gud. So ffs, let us do all the work. We're like AI, we learn through reinforcement learning.

Stop giving us a spec to follow. We'll do plenty of that in the future, right now we need to make mistakes, not be held by the hand all the way. Let us do dumb shit so you can fail us and tell us our code is repulsive, and this other way was better. Explain why. That's how people learn, not by telling us what each function should return, what can and can't be used, etc. And if you can't come up with a scenario in which what you're teaching is useful, then maybe you're not teaching us the right material.

I'll leave it at that for today... But I'll be back 😈

fuck u aws

all that money and u can't read idiot proof documentation for me to have SQS connect to a VPC endpoint to read a message

also fuck u search algorithms for not handing me an easy bake solution to what is a not a novel situation

also fuck me for being unable to git gud

Sooooo ok ok. Started my graduate program in August and thus far I have been having to handle it with working as a manager, missing 2 staff member positions at work, as well as dealing with other personal items in my life. It has been exhausting beyond belief and I would not really recommend it for people working full time always on call jobs with a family, like at a..

But one thing that keeps my hopes up is the amount of great knowledge that the professors pass to us through their lectures. Sometimes I would get upset at how highly theoretical the items are, I was expecting to see tons of code in one of the major languages used in A.I(my graduate program has a focus in AI, that is my concentration) and was really disappointed at not seeing more code really. But getting the high level overview of the concepts has been really helpful in forcing me to do extra research in order to reconnect with some of the items that I had never thought of before.

If you follow, for example, different articles or online tutorials representing doing something simple like generating a simple neural network, it sometimes escapes our mind how some of the internal concepts of the activity in question are generated, how and why and the mathematical notions that led researchers reach the conclusions they did. As developers, we are sometimes used to just not caring about how sometimes a thing would work, just as long as it works "we will get back to this later" is a common thing in most tutorials, such as when I started with Java "don't worry about what public static main means, just write it up for now, oh and don't worry about what System.out.println() is, just know that its used to output something into bla bla bla" <---- shit like that is too common and it does not escape ML tutorials.

Its hard man, to focus on understanding the inner details of such a massive field all the time, but truly worth it. And if you do find yourself considering the need for higher education or not, well its more of a personal choice really. There are some very talented people that learn a lot on their own, but having the proper guidance of a body of highly trained industry professionals is always nice, my professors take the time to deal with the students on such a personal level that concepts get acquired faster, everyone in class is an engineer with years of experience, thus having people talk to us at that level is much appreciated and accelerates the process of being educated.

Basically what I am trying to say is that being exposed to different methodologies and theoretical concepts helps a lot for building intuition, specially when you literally have no other option but to git gud. And school is what you make of it, but certainly never a waste.

I have been working with git for years now, and I could never work on a project (regardless if big or small) without it. Its great.
However, just a couple of days ago I learned about the git flow branching model.
Even tho I also worked with branching on a daily basis for years, I did not know about this model. And I have to admit: Its awesome.
If you don't know it, I highly recommend you to look it up. It really improves the already organized workflow with git even more. :)

Our site ran into a cache stampede which took down the site for awhile. While people were helping out, I just stayed out of their way since I knew nothing about it -_-

I realise I need to git gud but I can't help feeling inadequate and useless at times like this.

Is perseverance, experience, and passion to keep learning and bettering oneself the only way to being a master?

I still don’t understand git completely ,sometimes the error messages are so hard to understand I just make a new repository and push all my new updates there using GitHub desktop.

Git is good. Even when I do stupid things like reset a commit I wasn't supposed to, it gives me the chance to fix those mistakes.

(Oops. !rant)

Ok so some of you have probably seen my previous rants about my computer science teacher and our project but I'm just going to summarize all of them and share with you more of my pain.

1. He edits in the production environment. Its a laravel project and he is creating test database migrations IN THE PRODUCTION ENVIRONMENT AND SWITCHING BACK AND FORTH FROM MASTER AND DEV.

2. He edits in vim and doesn't follow codestyle even though I printed him off a piece of paper and emailed it to him.

3. He doesn't have any ethic when it comes to more complex things like laravel homestead.

4. He doesnt want me to release features even though he takes really long to do them.

While I love vim and it is my editor of choice, some things should be done in an ide. This is really annoying me and I'm really just considering handing him the project if he can't follow basic outline.

Today I did 'git reset --hard'

Didn't go se well. Time to install BackInTime

Me and the lead developer of my team gave a long and detailed explanation to our manager entailing the current state of a budge program our workplace uses.

This app has been bugging him for a while, he did not write it and has not been given an opportunity to rewrite the damned thing. Its a really...really messy application, and whilst it is a functional one it most certainly is NOT an efficient one since adding or moving things only incites more spaghetti mess.

We were laughing while giving our report, but both of us were crying inside. The main thing is, we both love PHP and the things he has built are very well structured and efficient, he has good technique, but will admit at certain caveats regarding the way he structures his dbs stating that he always has to do changes, which hey, its the nature of the beast, dbs change all the time. But our issue with php is the same: it lets beginners write monstruosities that are harder to do in other environments.

It really is a permissive language. But I reckon thay such lax nature is better left at the hands of the more experieced developers that know what they are doing.

Either way, we will restructure this motherfucker taking advantage of the new standards (which both of us are well versed in) and applying a more structured approach with a nice frontend interface (we be looking at Vue.js and React although we are considering Angular as well)

Gon be some good times.

My response, as a gamer and developer, when yet another guy tries to explain how "mercurial is so much easier to use":

Git gud

So I thought I knew source tree, apparently I do not... Lost a week's worth of work, went to history, saw someone removed it with a commit, and now I'm getting blamed for my own work 'disappearing'. The reason I am being told I am to blame is how I control my branches... So how I do it is that I keep a local copy of the master branch, I keep it updated and monitor it for changes regularly (meaning fetch and pull cause double tap..) before I do a merge, I check for any new code on master again, then using the local copy of master, which I just updated, I pull the master changes into my branch, deal with any conflicts, build and done. Then I request my changes into master once I am happy everything is good.

My question is, clearly there is something wrong with the way I do things, so please source tree users, what is the most fool proof way to pull latest from master so that I don't loose code? 😔

Learned git, decided, imma use this while I make a little game in Java, couple days later, I find out that net beans has git INSIDE of it... :/ ....

Late night git fixing
I will never commit two different features into the master branch

That moment when you realize that normal people dont use increment and decrement in normal speech syntax...

Finally got the opportunity to work as fullstack more oriented to backend as a side gig and I fucking love it.

Now I can say with all my heart that I hate my main frontend job and designers so much. I hate every small task like:
- change this arrow
- change this button
- change this color
- well this is not accessible.
- well this doesn't pass contrast check ( as if this is my fucking job and not the stupid fuck designer who mixes up colors )

Now I'm just trying to consider a reconversion and git gud .

Where can I find a good simple tutorial/course for learning the basics of git?

Use
git branch --merged
to get, you guessed it, all the branches you have merged.

Use
git branch -d <branch-name>
To delete a branch if it has been merged (use -D for forced)

And Use,
git branch --merged | egrep - v "(^\*|master|dev)" | xargs git branch - d

To delete all the branches that you have merged (but not anything with master/dev in their names)

Sorry for the formatting, I don't know how coder formatting works on DR..

Fighting to get a code repository up and running at my current company.

There is no central repository at all; people use their own local files and hope nobody else made changes. At least one product had to be retired because nobody could find the firmware source. I didn't even bother with git, I set up an SVN and showed them how basic and easy it was to use. They all agreed it was simple, and then continued to not use it. Facepalm.

I didn't understand why people always tell me "git gud"...didn't they know svn exist as well.

Anybody have advice about figuring out how you learn and how to have discipline doing things you don't like (everything related to being a codemonkey) so I can git gud?

you guys ever

> git instaweb

Git gud with TypeScript, do some mobile or some web dev. Also find a full time remote job so don't have to work in a office the rest of my life

Spend half an hour with the "git remote add ..." yada yada after setting up an git repo on a vps where I failed to create the home directory with the user and had to do it manually.

As I was against making a trash commit to win against the Schrödinger repo I begun torture myself with the PowerShell SSH compatibility.

I gave up at the end and made an commit with some libs I am going to use. After a last SSH port fight with git got everything up and running.

Lastly installed the new magical windows git credential manager and I am hoping to see some fairy dust in the next days.

Tl;Dr:
If(windows&&SSH&&git){
throw new EverythingWrongException("Git gud");
}