It’s to give women the opportunity to claim credit for their male counterparts’ work.
It’s to give women the opportunity to claim credit for their male counterparts’ work.
Programming in pairs was invented when programming was a profession of white males, with almost no exceptions. In large projects, 20% of the workforce is invested into building new stuff, 80% in hunting the errors. Having somebody watching over the shoulder helps detecting errors before they get hidden in millions of lines of code.
Edit: Today, you don't place two programmers before one terminal. Instead, we have source code repositories, code reviews and software to temporary share screens. If there is a "programming in pairs" culture today, then it may be really just a measure to keep diversity hires occupied.
Programming in pairs was invented when programming was a profession of white males, with almost no exceptions. In large projects, 20% of the workforce is invested into building new stuff, 80% in hunting the errors. Having somebody watching over the shoulder helps detecting errors before they get hidden in millions of lines of code.
Edit: Today, you don't place two programmers before one terminal. Instead, we have source code repositories, code reviews and software to temporary share screens. If there is a "programming in pairs" culture today, then it may be really just a measure to keep diversity hires occupied.
Perfect analysis. I'm now in charge of a group of coders. You are spot on. Git code reviews is how we detect errors and Teams is how coders collaborate. I often help my team resolve issues via screen sharing. We do not do pair programming as such, except when one person needs help once in a while.
My biggest problem is with good coders misunderstanding what we want to achieve and they simply do the wrong thing. My team is pretty talented but if I don't watch them often enough, they do the wrong thing.
Perfect analysis. I'm now in charge of a group of coders. You are spot on. Git code reviews is how we detect errors and Teams is how coders collaborate. I often help my team resolve issues via screen sharing. We do not do pair programming as such, except when one person needs help once in a while.
My biggest problem is with good coders misunderstanding what we want to achieve and they simply do the wrong thing. My team is pretty talented but if I don't watch them often enough, they do the wrong thing.
Sometimes I could use an extra hand. But the company is small. The chief technical officer once reminded the president of the company that I am just one guy at a meeting at one point, when discussing who is responsible for what in the new project.
That's okay, still designed/built the hardware and wrote the software for both the MCU and the PC, by my damn self, in a year.
Sometimes I could use an extra hand. But the company is small. The chief technical officer once reminded the president of the company that I am just one guy at a meeting at one point, when discussing who is responsible for what in the new project.
That's okay, still designed/built the hardware and wrote the software for both the MCU and the PC, by my damn self, in a year.
This should generally only happen with noobs or if you are explaining a repository to a new employee.
I am on a team of 3 in a company of about 100. I know the code that my counterparts will produce before they send me the PR because we have been working together and reading each other's code for so long.
There is no time for two people to do one person's job. If I struggle with something I make a branch, pass it to my coworker and they see if they can fix it while I work on something else. The idea of two people opening a new branch, declaring new classes together just sounds wasteful to me.
However, I peer coded with my wife yesterday . She is learning React and I thought I could help. I hate react now.
This should generally only happen with noobs or if you are explaining a repository to a new employee.
I am on a team of 3 in a company of about 100. I know the code that my counterparts will produce before they send me the PR because we have been working together and reading each other's code for so long.
There is no time for two people to do one person's job. If I struggle with something I make a branch, pass it to my coworker and they see if they can fix it while I work on something else. The idea of two people opening a new branch, declaring new classes together just sounds wasteful to me.
However, I peer coded with my wife yesterday . She is learning React and I thought I could help. I hate react now.
Oh JFC I had to look this trash up. What a waste of money. It could just as easily be a way for programmers to get black sidekicks. IDK. It's nonsense but I don't see it as exclusively 'feminization'.
Oh JFC I had to look this trash up. What a waste of money. It could just as easily be a way for programmers to get black sidekicks. IDK. It's nonsense but I don't see it as exclusively 'feminization'.
Understandable. I wish I'd learned a trade. On black programmers, it wouldn't surprise me. It seems like a great way to hide mediocrity.
Understandable. I wish I'd learned a trade. On black programmers, it wouldn't surprise me. It seems like a great way to hide mediocrity.
Programs which can only be understood by their creator are doomed an early death.
Programs which can only be understood by their creator are doomed an early death.
(post is archived)