"Whenever I see a door that says push I pull first to prevent conflicts"

Me and my wife are software engineers
Started dating while doing a project together
I guess you could say that we...
MERGED WITHOUT CONFLICTS

A brand new day, a brand new idiot!

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

I forced my friends to use git(hub) as vcs because their project was in a usb-to-usb state, which was unacceptable for me. So I offered them my help and uploaded it (with a little bit of a forced consent) to github, to end this misery. Of course I helped them the basics of git. Now they automatically use git(hub) as vcs and to share their code.

I feel proud for this :)

I'm a simple man, I want to:
- get along with everybody
- be able to depend on my coworkers
- use whatever editor I want
- have vcs (preferably git)
- listen to music while coding
- work with people who share my hobbies (optional)

This is a small project, I don't need to use git on it...

ALWAYS use VCS.

Today I learned Slovakia is in fact a version control system, not country.

Things you find on Wikipedia these days.. 🤔

Let the student use their own laptops. Even buy them one instead of having computers on site that no one uses for coding but only for some multiple choice tests and to browse Facebook.

Teach them 10 finger typing. (Don't be too strict and allow for personal preferences.)

Teach them text navigation and editing shortcuts. They should be able to scroll per page, jump to the beginning or end of the line or jump word by word. (I am not talking vi bindings or emacs magic.) And no, key repeat is an antifeature.

Teach them VCS before their first group assignment. Let's be honest, VCS means git nowadays. Yet teach them git != GitHub.

Teach git through the command line. They are allowed to use a gui once they aren't afraid to resolve a merge conflict or to rebase their feature branch against master. Just committing and pushing is not enough.

Teach them test-driven development ASAP. You can even give them assignments with a codebase of failing tests and their job is to make them pass in the beginning. Later require them to write tests themselves.

Don't teach the language, teach concepts. (No, if else and for loops aren't concepts you god-damn amateur! That's just syntax!)

When teaching object oriented programming, I'd smack you if do inane examples with vehicles, cars, bikes and a Mercedes Benz. Or animal, cat and dog for that matter. (I came from a self-taught imperative background. Those examples obfuscate more than they help.) Also, inheritance is overrated in oop teachings.

Functional programming concepts should be taught earlier as its concepts of avoiding side effects and pure functions can benefit even oop code bases. (Also great way to introduce testing, as pure functions take certain inputs and produce one output.)

Focus on one language in the beginning, it need not be Java, but don't confuse students with Java, Python and Ruby in their first year. (Bonus point if the language supports both oop and functional programming.)

And for the love of gawd: let them have a strictly typed language. Why would you teach with JavaScript!?

Use industry standards. Notepad, atom and eclipse might be open source and free; yet JetBrains community editions still best them.

For grades, don't your dare demand for them to write code on paper. (Pseudocode is fine.)

Don't let your students play compiler in their heads. It's not their job to know exactly what exception will be thrown by your contrived example. That's the compilers job to complain about. Rather teach them how to find solutions to these errors.

Teach them advanced google searches.

Teach them how to write a issue for a library on GitHub and similar sites.

Teach them how to ask a good stackoverflow question :>

Replacement for git VCS 😂

Been looking for a part time game dev job to pass the time during summer break, got a reply from a guy.

This part came up some time in the middle of our conversation:

Me: So, do you have a version control system in place?

Him: Excuse me, a what?

Me: A Version control system, like Git.

Him: Ow, what's that?

Me: It is a way to host projects in a more productive way for two or more people. It allows us to share our work more easily and work on the same file without overwriting and losing data.

Him: Ow, like Dropbox?

He was developing the game solo thus far and no idea such thing existed.
:/

I think what would help is to teach them these things:
- awareness for security in code
- how to use a fucking VCS like Git and how it works

"We don't use a VCS like git, what are you opinions on this?" This is great in my opinion. You get to see some people sheepishly agree and say it's fine and try back it up, or people put valid points why they think it's wrong. You can start to gauge a person's personality after a few of those kinds of questions.

Not separating different changes into different commits, and just adding "a few tweaks" when I can't be bothered to list changes.

git commit -m "Added x, updated y, renamed z, and a few other tweaks"

I like, that many code hosting sites are shutting down (Google Code, Codeplex). This does not mean those sites are bad.
The ones I like and use are GitHub, GitLab, Bitbucket (and most personal ones like Gogs or GitLab CE).

Here is my list of the sites I don't like:
- Sourceforge
- SF
- sf.net
- sourceforge.net

Dear git,

FUCK YOUR FUCKING FUCK SHIT .GITIGNORE FILE! WHY CAN'T YOU JUST FUCKING REMOVE THE IGNORED FILES FROM THE VCS? EVEN GIT RM --CACHED --FORCE DOES NOT WORK WTF

TL;DR
"git" your shit done.

Yours sincerely
Scrumplex

First company:

- being sat at an office that didn't have chairs with proper back support. It would kill my back every day. Like sitting on a bar stool coding.
- not having access to basic resources (cafeteria, salary bonuses)
- being seriously underpaid ($200 under)
- not having an IT process pipeline (yeah, this is a huge one): no JIRA, no git, no VCS, no continuous integration, etc. I fucking spend 45% of the time fixing coding-unrelated shit.

Second company (very aggravating):

- dumb frontend bitch and privileged colleague who both kept telling me months on end to shut up and who wouldn't listen to my advice on anything, while my advice would actually help the company advance in productive ways. The key here is being told to shut up while stagnating. i.e. dead end job.
- people advancing in the company based on nepotism and favoritism, based on having tits and ass, rather than skills and independence.

- pointlessssssssss meetings where decisions are made solely based on the opinion of Mr. favorite senior dev. The rest just sits there like a bunch of sad saps and yay-nodders. Incompetent PO's who "would like to hear your input" but then when you give it, they completely dismiss you.

- pointlessssssssss monthly meetings with stakeholders, where the dev teams do nothing but clash and act like pussies in front of the PM just to get in his favor, but behind scenes continue to make the same mistakes and telling the CEO everything is fine. Goodness, how can it get more unproductive.

- completely antisocial and nepotistic 'colleagues' who won't even talk to you, let alone smile at you or be friendly. You saying good morning and them pretending you're vapor that doesn't exist. Go go company atmosphere! Especially during lunch, those are the worst times. Imagine sitting at lunch where everyone looks like you killed their dog and the rest is huddled up in little high school groups.
What else? The incessant and pointless smalltalk that makes me want to bang my head against the wall. Talking about dogs, kids, what show was on tv last night. The fuck man, do you have a brain?!

Third company:

- HR bitches who think they are the shit and developers are antisocial, helpless misfits, but they work with computers and they don't even fucking know what a status bar is! The irony!

- forced socializing and stigmatization for the opposite. Imagine coming into a company and you don't say good morning. Should that be a problem? No. Instead, everyone starts dogging on you and hating you just because you didn't smile in their faces and said: hiiiiiiiiiiii how did you sleep? Did you feed your dog? Fuck you.
Elliot (Mr. Robot): "Wouldn't it be awesome if there was a mute button for life?" -boop, boop, boop, boop...- Ahh.. there.. that's much better."

- CEO's sucking up to you but when it comes to salary increase, they say shit like: "Ahhh ya know, it's kinda difficult." Yet another dead end job.

What is a git?

My new mobile development teacher just admitted he has never learnt git or any other VCS, I asked him what he does when shit happens and he just said,

"I just have a folder for each version backed up to Google Drive"

This is the guy that's teaching us? Surely as a teacher you should be setting a proper example and using good practises....?

my job is to build to spec and get things working

NOT to fuck around with git's exotic features so the fucking commit history "looks nice"

its called a version control system for a reason. SO YOU CAN CONTROL YOUR FUCKING VERSIONS

IF YOU WANT A NICE PLOT, GO READ A BOOK OR WATCH A DRAMA MOVIE AAAAAAAAAAAAAAAAAAAA

I know that this will bring me many new enemy's but I'll just say it.

I like Mercurial more than Git.

The one skill I know that I am really proud of is GIT.

Put me into trouble with merge conflicts.
Saved my life with its version control.
Always had an adventurous ride with Git. Hope to have many more such rides and get to learn more about you.

Git: the occasionally frustrating, dangerous, and infuriating VCS you can't believe you were living without.

Just needing somewhere to let some steam off

Tl;dr: perfectly fine commandline system is replaced by bad ui system because it has a ui.

For a while now we have had a development k8s cluster for the dev team. Using helm as composing framework everything worked perfectly via the console. Being able to quickly test new code to existing apps, and even deploy new (and even third party apps) on a simar-to-production system was a breeze.

Introducing Rancher

We are now required to commit every helm configuration change to a git repository and merge to master (master is used on dev and prod) before even being able to test the the configuration change, as the package is not created until after the merge is completed.

Rolling out new tags now also requires a VCS change as you have to point to the docker image version within a file.

As we now have this awesome new system, the ops didn't see a reason to give us access to kubectl. So the dev team is stuck with a ui, but this should give the dev team more flexibility and independence, and more people from the team can roll releases.

Back to reality: since the new system we have hogged more time from ops than we have done in a while, everyone needs to learn a new unintuitive tool, and the funny thing, only a few people can actually accept VCS changes as it impacts dev and prod. So the entire reason this was done, so it is reachable to more people, is out the window.

sometime its more difficult to control version controlling system than whole application

When you check out your personal project at work on lunch... to find that you forgot to push.

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..

I realised, that Git now has the same problem as Windows:
Its widespread because its widespread.

There are, especially for smaller projects, few reasons to actually use Git instead any other VCS.

Look at the landscape of free repo hosting.
There are hundreds, if not thousands of free Git hosters.
A handful of free Mercurial hosters,
Launchpad for Bazaar and I didn't even find a free SVN hoster.

Everyone uses Git, because there are Services for it, and there are Services for it, because everyone uses it.

So I just spent a 7 fucking hours recreating a feature just to find out that I already did it once. Don't forget to checkout the correct branch fellas.

Who else thinks commit messages in lower case look more neat?

The moment you realize that your dev colleague has just totally given up on the project (and you get why)...

We've got a big legacy app which we have to rewrite. The current client applications are only working on XP(!). We have to move the clients to the browser so we can finally get rid of all XP vm-s. The db schema is complex but still 1000+ stored procedures and functions and about a hundred tables with 13 years of data.
So I ask the guy responsible for maintaining the DB code. (he is ~25 years older than me)

me - Where is the source of the database. Which project?
he - Where would it be? It's in the db.
me - So we've got a huge db without VCS, upgrade/downgrade scripts, etc?
he - Yes. I don't get why young developers always want to use shiny new tech like git just because it is cool. It has nothing that an external usb backup drive can't do.
me - VCS has been around since the early 1980's...
he - If you really want, you can put it under git or whatever, so you can sleep better, but I still think it is stupid and a waste of time.

I get that it's hard to keep up, but getting personal...

Ansible and mountain dew

Hello, my name is Linus Torvalds and I pronounce SVN as git

Those moments when you get up hoping that you don't screw up your day but then end up bugging your code rather than debugging it and then Git/other VCS comes to your help.

markdown is not good enough! the tools aren't there for non-devs and there's no concordance on moving forward *compatibly* for anything other than headers and __possibly__ lists.

md has been around for years and still no consensus on comments, meta data, css, data imports, etc.

i could never in good faith recommend to a non-dev to use markdown, even though every academic and professional writer from legal to journalism should exclusively be using markdown to write and store their documents. the data portability and ease of search, retrieval, collection, distribution, etc of markdown compared to pdf or docx is enormous. markdown is the hex format of text, the perfect layer of data and visual so that the user and the computer can both operate on text as blocks of data rather than weirdly styled paragraphs that need to be reformatted BY HAND for citation-style or journal format, or paper size. FOR EACH SUBMISSION. Academics literally rewrite their 100-page papers to accommodate up to 10 different submission requirements.

They could be clicking MLA vs Chicago and/or using a journal's stylesheet to recompile for its styles.

Today there is some support from zotero et al to take away some of the pain, but it makes ZERO SENSE for writers to have to keep and store and keep up to date, multiple versions of the same document. Git pull does not exist for them. But the worst part is that git isnt the solution to their problem. They need a compiler more than they need version control. But they also desperately need vcs. They ALL literally have a million files named "dumdum.dumFINAL-3084_lastversion \2020, this one.dum".

They dont have git or anything like it, because they need a line-by-line solution like markdown for git to become effective.

All of writing is basically mired in the fact that people cant even roll up their paragraphs and see what the fuck it is theyre saying. Most writing reads like a long scroll through some nonsense that goes nowhere. Like this rant. but the point is that markdown and line-by line editing actually produces more logically sound writing. You start to think in terms of defining ideas in blocks, ... like code.

So we (group of 3) were out to a tech guy who was out sourcing some project. During the meeting we mentioned VCS, upon hearing this the guy was like "this is used by big companies". we left the meeting then and there.

Everytime I use Linux and Git I wish in the Linus's time there was more crappy tools and he would make an alternative for these too.

Good code is a lie imho.

When you see a project as code, there are 3 variables in most cases:

- time
- people / human resources
- rules

Every variable plays a certain role in how the code (project) evolves.

Time - two different forms: when certain parts of code are either changed in a high frequency or a very low frequency, it's a bad omen.

Too high - somehow this area seems to be relentless. Be it features, regressions or bugs - it takes usually in larger code bases 3 - 4 weeks till all code pathes were triggered.

Too low - it can be a good sign. But it should be on the radar imho. Code that never changes should be reviewed at an - depending on size of codebase - max. yearly audit. Git / VCS is very helpful here.
Why? Mostly because the chances are very high that the code was once written for a completely different requirement set. Hence the audit - check if this code still is doing the right job or if you have a ticking time bomb that needs to be defused.

People
If a project has only person working on it, it most certainly isn't verified by another person. Meaning that only one person worked on it - I'd say it's pretty bad to bad, as no discussion / review / verification was done. The author did the best he / she could do, but maybe another person would have had an better idea?

Too many people working on one thing is only bad when there are no rules ;)

Rules. There are two different kind of rules.

Styling / Organisation / Dokumentation - everything that has not much to do with coding itself. These should be enforced at a certain point, otherwise the code will become a hot glued mess noone wants to work on.

Coding itself. This is a very critical thing.

Do: Forbid things that are known to be problematic in the programming language itself. Eg. usage of variables in variables, reflection, deprecated features.

Do: Define a feature set for each language. Feature set not meaning every feature you want to use! Rather a fixed minimum version every developer must use and - in case of library / module / plugin support - which additional extras are supported.

Every extra costs. Most developers don't want to realize this... And a code base that evolves over time should have minimal dependencies. Every new version of an extra can have bugs, breakages, incompabilties and so on.

Don't: don't specify a way of coding. Most coding guidelines are horrific copy pastures from some books some smart people wrote who have no fucking clue what you're doing and why.

If you don't know how to operate on people, standing in an OR and doing what a book told you to do would end in dead person pretty sure. Same for code.

Learn from mistakes and experience, respect knowledge from other persons, but always reflect on wether this makes sense at this specific area of code.

There are very few things which are applicable to a large codebase on a global level. Even DRY / SOLID and what ever you can come up with can be at a certain point completely wrong.

Good code is a lie - because it can only exist at a certain point of time.

A codebase should be a living thing - when certain parts rot, other parts will be affected too.

The reason for the length of the comment was to give some hints on what my principles are that code stays in an "okayish" state, but good is a very rare state

Lesson learned. As a newbie to git and vcs in general, always verify a rebase to make sure you didn't accidentally delete your last days work before force pushing and overwriting the company repository. Also, don't get into a situation where you need to do that in the first place.

'I'll fork you'

Anyone know of some Git puns?

I'm tutoring a group of students (university) on using Git effectively in a team. Anything to make it more humorous would be awesome :)

I have to confess: I don't use a version control system. But, as of today, I'd like to change that.

I have a few questions for the community:
What VCS are there and what are the differences? I've heard of Git, but are there any others?
Can you recommend any hosting services? I know of Github and Bitbucket. Are there others? Which is better?
Are there any tools you use? Or just the command line application?
Finally: Can you recommend any tutorials for using these VCS?

Thank you in advance,

Somebody who probably should have done this ages ago (me)

The designers kept changing the layout for a web app every week and refused to use a version control system so they sent the new files by slack every release

Is anyone out there using Mercurial in a commercial environment still? I always preferred Mercurial over Git back in the day but I find it hard to understand why anyone would still be using it other than out of stubbornness.

Sourcetree: "It would be a shame if you commited all those changes to head instead of main..."

Change is truly a difficult thing. I've been trying to introduce my group colleagues to GitHub, I even gave them some tutorials that I used. I'm not saying I know everything about Git or GitHub but the pros of using it or any VCS outweigh using Google drive, zipping and email each other the code and many other creative ways of sharing work. Let's just say two months have passed there haven’t been any change ☹

I hate VCS integration in IDEs. No I do not want to add the new fucking file to Git, IntelliJ. Urgh

I am uneasy with these VCS integrated editors. I feel like not everything is gonna be added. I still use git bash when on windows.

#Reviewing Commits

WHY? In hell's name will you open a tag and not close it???!

I might sound stupid, but why don't solo-developers use things like dropbox for active file history that keeps track of every change and also gives diff options and up to 1 year log - instead of git?

Don't get me wrong, git is amazing when you have to work with a team or multiple people in general, but it's simply a pain in the ass when working alone and having to keep track of every state yourself.

When you havent pushed in ages and have to tediously 'git status' followed by 'git diff <every fucking file>' to figure out what the hell you've even been doing since the last push and can maybe figure out another commit message than "Various bugfixes"

Anyone here who created a team in Bitbucket but the only member is their self? I know it may be a silly question but I just want to create projects so I can organize my repositories

Has anyone used version control as bad as AccuRev? Manual backups don't count.

My company will change the VCS to git. Now the though part is: GitHub or GitLab?

Leaving things out of VCS. My usual folder structure is like this:
- Project name:
|-- env (virtual environment)
|-- Project name (git repo)
\-- (keys, credentials, etc.)
It makes sense, but after a while, more and more important stuff starts piling up in the outer folder (not version-controlled).

I have a technical job interview via phone call later today and would like some advice on what to prepare for.

The role is Junior Web Developer and here is what's expected of me:

- Good knowledge of HTML and CSS
- Some knowledge of Javascript
- Some experience with a PHP framework such as Laravel
- Some experience developing themes for content management systems such as WordPress
- Basic familiarity with Git or other VCS

Those are fairly low requirements and I meet or exceed them individually but just want to ensure I prepare properly.

What can I expect?

My boss asked me how to make a new branch with git...we've been using git for 3+ years.

Am I the only one that prefers HG to Git?

The VCS I love is Git with GitLab.

The way client code reviews is via email pointing outline number for explanation and expects to send the zip file of the entire project via Google Drive.

why the fuck git exists??

Hello, I am doing master in Pharmacy, but I like programming and consider to switch or connect somehow industries. I could write simple scripts and small programmes in Python, but I want to write code with good practice from beginning.

So my question what should I know and put in use, maybe some resources if someone has them or just terms for further search. At this moment I use gitlab for VCS (my commits sucks and my whole usage of Git sucks, but at least I use branches), I am trying to separate control from model (MVC but I guess I do it poorly), also I use keepchangelog rules for changeling, and semantic versioning for versions, PEP8 and Pokemon names for my variables and functions as it helps read code later.

Almost all the company uses git, I even took a training about git and how does it integrate with internal tools.
In my team they use mercurial.
fml.

First boss introduced me to VCS., so I PUSHed my self --HARD was very COMMITed, but I still don't GIT it

!Rant
So...GitKraken. Using PhpStorm, why would I use it?

I don't know much programming languages. I know some but I am not good at them. Going through the post here I came to know about VCS and git. I learned it, now I know git however I have nothing to implement that knowledge on as I know very few language.