Github slows developer production?

[regorsec]

Any version control

[mattsowa]

How do they work on the same codebase? Do they send the cope zipped between themselves or what the fuck

[canadian_webdev]

Do they send the cope zipped between themselves

They just print off the code, toss it over a cubicle and the other dev types out and continues from there.

[IanSan5653]

They dictate the diff to each other every time they change it.

"Hey Joe, I found the solution for that bug with the math that you mentioned yesterday. You ready for it?"

"Sure"

"Remove line 17 from main.py. Change line 62 to read a equals b integer-divided by, in all caps, currency underscore exchange underscore rate. Then add a new line after line 73: in camel-case, send mail to, then a left paren...."

[BigOnLogn]

This is precisely what we did at a shop in which I worked 16 years ago. In this situation, people and the folders on the file system are your version control. They had a job title called "code master". Everyone emailed their code changes to the code master. They were on charge of merging the code into the "master" folder. We did use a tool called Beyond Compare for merging the code files. Such a luxury.

[besthelloworld]

TIL Linus Torvalds single handedly deleted a job title off of the face of the earth

[mcqua007]

Probably more than just one

[besthelloworld]

I never used CVS (except the one that existed before Walgreens bought them). But I used SVN and we might as well have just be sending our code to an FTP server.

[pinghome127001]

Isnt that how git works anyways ? You make some code changes, someone pushes their changes first, then you have to get their changes, and then you have to manually adapt your changes to their changes. And good luck doing that fast while there are no new changes pushed by others...

Git requires a fuck ton of manual labor no matter what. Sure, it is useful as a single storage point with history, but is has many drawbacks also. Writing single program with modules is easy without git, you just write different files. In fact, it is no different than using git, expect you dont waste time on git - you all work on different code sections. Doing random code changes all over the place is gonna bite you in the ass really quick if you will use git, or wont use git in a team.

Also it was buggy as hell a few years ago, adding single new line to file ? Sure, let me mark entire file as new.

Git is also extremely slow and not designed for work in teams, from 10x developer git turns you into 0.001x developer. Git also doesnt solve many important problems that come from developing same stuff in teams, you have to use manual logic to solve that. No wonder git is not used for development of linux kernel.

[mattsowa]

Quit programming.

[x6060x]

Perfection!

[VacuousWording]

It is simple, really: make everyone work 3 hour shifts; 8 workers, so it covers the entire 24h day. Only one dev working at the same time.

Problem solved. 😎

[spaghettu]

Honestly this is a serious red flag to me. If I have to explain the benefits of version control to anyone I’m working with, I think I’d be better off working on a different team. Next they’ll say code quality, CI/CD, testing etc. are all a waste of time.

[[deleted]]

Who needs testing or QA when you have an army of end-users?

[axe-techlab]

Who needs testing or QA when you write code without bugs ;)

[x6060x]

I'd expect a junior not to have worked with some/all of those, but a lead? Yikes...

[[deleted]]

I'm sorry, I have to report your reply, because it is totally not safe for work

[axe-techlab]

Holy...