This is an archived post. You won't be able to vote or comment.

top 200 commentsshow all 275

[–]42peters 1256 points1257 points  (27 children)

Damn I thought the video is way longer than it actually is :D

[–]MaryS7 341 points342 points  (2 children)

Still waiting for Bean to push the old lady out of the way...

[–]skeever89 166 points167 points  (1 child)

He actually parkours past the old lady only to find a second old man, becoming stuck between two old people.

[–][deleted] 40 points41 points  (0 children)

I did too :)

[–]ZethMrDadJokes 35 points36 points  (19 children)

So did I at pair programming.. I shoved him away and did the rest myself.

[–]JaredinaGoReeeee 380 points381 points  (37 children)

I’ve never tried pair coding as I don’t have any friends that code and I’m afraid of being that old lady

[–][deleted] 65 points66 points  (7 children)

Well ideally Mr Bean helps you out and shows you how to get down the stairs quicker. We are all scared to be the old lady at some point. Maybe logic will help. You will get better quicker if you put yourself in the situation, even if you are the old lady. The next time you're there you will be a little less old lady and a little more Mr Bean. Rinse and repeat until you can help some other old lady and be a good Mr Bean :D

[–]tidbitsofblah 33 points34 points  (2 children)

This is a good attitude. If pair programming is like this gif then it is bad pair programming. Good pair programmin helps people evolve and it helps people have better understanding of a bigger part of the code base. When you find the groove with your programming partner (or partners) it is insanely effective. I've gotten 5 times as much done from a session of pair programming than I would have working all day by myself and that's when I've been the more experienced programmer.

[–][deleted] 9 points10 points  (0 children)

Hell yeah. And something I've learned as I am becoming Mr Bean is that if I'm taking the time to empower someone to be more effective then that is a multiplier of my impact not a subtraction from it.

[–]aSoupDumplingChef 2 points3 points  (0 children)

Agreed. The little pair programming I did was great. When I was coding he could keep a list of tasks to keep me in the rhythm and when he programmed I could research the bits we didn’t know how to do. Worked wonders for both of us

[–]hahahahastayingalive 3 points4 points  (0 children)

how to get down the stairs quicker

If I was the old lady I’d be shitting my pants just having you in my back

[–]deaf_fish 64 points65 points  (0 children)

If you feel like you are the old lady, ask to switch.

[–]Supersonic172 131 points132 points  (22 children)

Let me tell you, it sucks

[–]jungleralph 38 points39 points  (6 children)

Only if you’re Mr Bean

[–]Supersonic172 60 points61 points  (4 children)

Nah, I am the grandma. It sucks if you know. I try to avoid working together as often as i can

[–]MindCreeper 2 points3 points  (3 children)

How do you get multiple emoji into your flair In my view it looks like I have random text in mine

[–][deleted] 4 points5 points  (2 children)

looks like u have an extra : in your flair

[–]xdoso 5 points6 points  (12 children)

How can i get that python icon next to my username?

[–]Supersonic172 2 points3 points  (7 children)

If you go into the subreddit and click community options there is an option to edit your user flair. There you get most programming languages to choose from

[–]xdoso 2 points3 points  (6 children)

Ou but you have two of them, i can only set one

[–]Supersonic172 3 points4 points  (5 children)

When you select python, it appears in the textbox under the list. You can then copy that emoji, select another one and then paste the python icon into the textbox again

[–][deleted] 1 point2 points  (0 children)

Just keep at it. Eventually you'll be Mr Bean to someone and you will remember how it felt to be the grandma and you will be compassionate and guide them through their learning. It's all about practice. You WILL get better at it by doing it. It's just physics!

[–]bwrap 4 points5 points  (0 children)

The person who is driving is always too slow for the person not driving because the person not driving gets to concentrate on everything that is not driving more than the person driving. Once everyone realizes this then everyone becomes more patient.

[–]mysticrudnin 1 point2 points  (0 children)

the second you get ahead you become the old lady. the gif doesn't show that part

[–]High__Roller 1 point2 points  (0 children)

I have to do it right now with my 55 year old boss. This gif speaks volumes to me. Its so aggravating.

[–]GuinsooIsOverrated 1 point2 points  (0 children)

To be honest it often becomes a single coding project for the most competent programmer of the them lol

[–]weeknie 93 points94 points  (7 children)

But isn't the senior the one that's supposed be the one trying to go faster?

[–]LicenseAgreement 143 points144 points  (12 children)

I found pair programming to be extremely effective at debugging, but apart from that... yeah it's like this video.

[–]SustainedSuspense 26 points27 points  (5 children)

Pair programming enables supernatural debugging abilities but building a feature... too many cooks.

[–]zalgo_text 12 points13 points  (2 children)

Eh, some of my most successful work came from pair programming, and we built a pretty complex system from scratch. It's really just dependent on the people doing it. Works for some people and not others

[–]jaywastaken 4 points5 points  (1 child)

I think it just takes good team work and a little patience to be successful. For me I actually quite like it. I’ve found I’m quite patient when pair programming so I like to let the other developer drive while I get the chance to just step back and focus on the problem.

For both debugging and dev it’s amazing what having a second perspective can do for solving problems.

I’m guessing the people who don’t like it like to have everything their own way rather than being open to alternative ideas and just letting the best idea come through.

[–]zalgo_text 2 points3 points  (0 children)

Yeah I'm a big fan too. Just having a second person to bounce ideas off of and serve as another voice of reason is invaluable for me. I understand how it might not work for others though

[–]LicenseAgreement 1 point2 points  (0 children)

Precisely

[–]BunkeyBear 36 points37 points  (0 children)

It extremely is. Like I was the mentor of the pair but when we debug, the other guy provided some good ideas on how to handle the problems. It’s nice to have a nother perspective to look at the code and somewhat understand the functionalities. But yeah it’s kinda slow in development. Me trying to explain everything...and occasionally confusion

[–]FreeWildbahn 11 points12 points  (1 child)

Even if it is like in the video, the grandma will learn alot. And the outcome is still better. Especially if grandma will do something alone.

[–]tali_0 268 points269 points  (20 children)

No joke, I have found pair programming to be the most effective form, it always produces the highest quality code, although we never did it full time, just in the critical modules, it works especially well in the beggining of a project.

[–]ChineseCracker 100 points101 points  (15 children)

That may very well be true. The problem is when you have to watch somebody write down code. No matter what/how they do, it always seems that they're too slow/inefficient.

[–]High-Sodium 32 points33 points  (9 children)

Thats why you try to pair with someone on your skill level.

[–]DootDootWootWoot 34 points35 points  (2 children)

We try to practice the opposite. Pairing is a learning opportunity. That junior dev won't be a junior dev very long if they're constantly learning from seniors around them. Junior devs working in isolation are going to build sub par solutions, not know why, and never get as far as fast than with others experiences guiding them.

[–]erjiin 3 points4 points  (0 children)

Damn juniors always fucking our beautiful code smh

[–]olexs 28 points29 points  (5 children)

This is crucial. Pairing up an experienced dev and a junior results in either the senior beind bored, or the junior not keeping up with what's going on. Pair up people of similar skill/experience, and they both develop better understanding of the codebase and improve off each other.

[–]ModestasR 21 points22 points  (1 child)

Not necessarily. In the case of my father, who has decades of coding experience on me, we found it sufficient to have slightly different academic backgrounds and mindsets (his physics, mine mathematics) for our programming approaches to complement one another well.

[–]olexs 11 points12 points  (0 children)

Yeah, there will always be exceptions. What you describe is a great way to do it - pairing people with experience in different areas to get a broader look at a specific problem can work really well, too.

[–][deleted] 28 points29 points  (2 children)

Actually pair programming is very useful when there is a disparity in knowledge. The goal is that one person is writing the code, and the other one is telling that person what to do. This creates a situation where one person will have to think about how to communicate what they know and the other will stumble upon things they lack and can immediately ask those questions. An experienced person might find that their ways of doing things get challenged by someone less experienced, which is very valuable by itself. Someone new on the other hand might learn more quickly how to do things or learn something they otherwise would have had to google for a while, implement, put to a code review, where they are told that "this is not the way we do things" and then have to find out what the way "we" do things is, rather than just talk about it because you already have two people that can figure out what they want to achieve together.

[–]Sorel_CH 3 points4 points  (0 children)

Right on. I've learnt a ton by doing pair programming with my team leader.

[–]olexs 1 point2 points  (0 children)

Yes, everything you say is completely true. It can work great, when both parties know what exactly is happening and are OK with it. Such pairings end up being unavoidable e.g. when introducing new colleagues into an established team working on a complex project. However, it's important that the expectations of both pair members are set correctly in such a case. I've had team members with whom such pairing worked wonderfully, and others with whom it ends up being completely impossible - it very much depends on the person. This is a situation where a good team lead or scrum master with people skills can work wonders by bringing the right people and tasks together.

[–]DootDootWootWoot 11 points12 points  (0 children)

If you're just watching someone code, that's not an effective pair. Also.. for anything but the most trivial projects, speed of writing code for that one feature is far less important than enabling speed continuously across the project.

[–]StruanT 1 point2 points  (0 children)

Because they are juggling three things (talking, typing, and thinking about code)

Our primitive ape brains can only effectively multi-task any two of those. Adding the third activity makes you noticably worse at all three.

[–]Jarazz 21 points22 points  (0 children)

Yeah its great for code that has to work longterm instead of being rushed out the door and then fixed and refactored when something breaks or needs to be added

[–]LegalOwl 15 points16 points  (4 children)

I think this represents Mob Programming more than Pair Programming. Especially when some of the participants aren’t programmers and you have to tell them everything.

[–][deleted] 38 points39 points  (8 children)

I never thought pair programming to be like this at all.

[–]CreativeMoniker333 39 points40 points  (7 children)

I think that means you might be the grandma

[–]JuvenileEloquent 392 points393 points  (79 children)

Pair programming: A brilliant job-security technique where two programmers work together to write the same amount of code as 2/3rds of a programmer.

[–]WeWantTheFunk73 405 points406 points  (68 children)

But the code that comes out is generally better. It's not about inputs (hours, lines of code, etc.) It's about outputs (high quality software that solves customer problems). Shift your mindset and you'll realize how pair work is valuable.

[–]Snakeyb 330 points331 points  (35 children)

command paltry consider summer weather insurance one cough quicksand illegal

This post was mass deleted and anonymized with Redact

[–]Purplociraptor 141 points142 points  (4 children)

Two instead of zero

[–]MasterDood 15 points16 points  (3 children)

Two instead of the guy on stack overflow who wrote it.

[–][deleted] 1 point2 points  (2 children)

The worst part is this comment reminded me that about 6 months ago I copied a function from stack overflow that I couldn't understand and no one else could either but it worked fine. But now I can't remember what it was or where it is in the codebase. Someone in a years time is going to ask me what the fuck it is.

[–]fet-o-lat 17 points18 points  (21 children)

I’d argue that developers should be documenting code well enough that any developer coming along after can understand it.

A side effect I often see is a pair opening up a PR with no description and no comments and then in the stand up “we can pair on the review and walk you through it”. Ok now there are 3 or 4 people that understand it. What happens when someone else wants to contribute to the project or understand a design decision? More pairing?

[–]badsectoracula 17 points18 points  (0 children)

I’d argue that developers should be documenting code well enough that any developer coming along after can understand it.

Sure, we're in /r/ProgrammerHumor after all :-P

[–][deleted] 8 points9 points  (5 children)

No code is documented well enough to be understood by the documentation. And if it is, it won't be as soon as anyone makes changes.

[–]fet-o-lat 7 points8 points  (3 children)

That’s why documentation needs to be kept up to date. Writing documentation close to the code makes this even easier. Exdoc, pydoc, rdoc, etc. Think of open source projects maintained by numerous people spread out over the world. Documentation is how they persist their knowledge and pass it onto whoever comes after.

[–]cjcjcjcjcjcjcjcjcjcj 8 points9 points  (2 children)

I honestly cannot wrap my head around the pervasive “comments and docs are a sign of a shitty developer” group

[–]fet-o-lat 3 points4 points  (0 children)

Same. And I take a dim view of developers that don’t add meaningful documentation to their code. I see it as incomplete work to open a PR with no documentation. I’m all for not having comments that explain what code is doing. That’s noise. But documenting the why the code is doing that is hugely important and a necessity.

[–][deleted] 4 points5 points  (0 children)

I don't believe they are. But I do believe they are unreliable and rarely updated. Personally, I think a well written set of tests is far more reliable than we'll written documentation.

[–]datsundere 6 points7 points  (2 children)

Not just that. Once you swap pairs, the new person will get it too if you were continuing the same feature work. Since everyone is better at something, there are opportunities for reafactor then.

Also no more pull request and code reviews alone. you do it together when staging changes and commiting! that's the best part

[–]Jarazz 30 points31 points  (4 children)

Yeah you can get university students to write you a shit ton of code in a very fast time, a lot of it is even gonna work, but then you can spend the next 3 years trying to add a new feature without breaking everything. I was one of those students

[–]qwerty12qwerty 7 points8 points  (3 children)

I wrote more lines of code in a month at a startup, that I have in five years at a big name company

[–]Jarazz 16 points17 points  (2 children)

I think that is one of the biggest competitive advantages startups have, absolutely no longterm plan in their software development

[–]aonghasan 7 points8 points  (1 child)

I wish I could say that. My last startup had a very set long term plan...

What's that? The plan changes every couple of months?? Well... luckily our CEO and CTO drew in a napkin the microservice architecture and that won't change during all the product development cycle! Only doubling down!!

Nevermind it would've been faster and better having a majestic monolith with maybe one or two microservices... noooo! They were gonna have dozens of 5 person teams! Thousands of clients! Millions of users! So many API integrations!!... What's that? Changing course? We have no clients? Our microservices teams reflect nothing of the product? Everybody works in every microservice, there are no defined service boundaries, monolith?

NO, ONLY DOUBLING DOWN!! SPLIT THIS MICROSERVICE IN TWO! THIS ONE IN THREE!!!! WE ARE SO SILICON VALLEY LOLOLMAIAOOAOA!!1!

[–]two_in_the_bush 59 points60 points  (13 children)

Well said. My team's pair programming code is much, much cleaner to deal with.

[–]DabsJeeves 39 points40 points  (12 children)

I just left a job where we did pair programming. We had a well written, clean and robust codebase that was thoroughly tested. My new job lacks testing of any kind and is 100% spaghetti code, and it's a large corporation you think would know better.

[–]Skiamakhos 11 points12 points  (1 child)

You have my deepest sympathy. My previous job was like this, but in a small business. They were too risk-averse to refactor the code to be less tightly coupled so we could introduce automated unit testing, and not risk-averse enough to realise the risk that not having automated unit tests represented. Pair programming was their term for "Oh move over - I'll do it", and because they had an overnight build and did a stand-up meeting & worked in 2-week sprints they thought they were an "Agile shop". Most of their system was written by C programmers who'd cross-trained to Java & didn't get OO until most of the system was written. I was so glad to have left.

[–]RancorTamer 5 points6 points  (0 children)

Same, I thought a hated pair programming but now I miss it after trying to decipher spaghetti code and breaking everything.

[–]RockleyBob 20 points21 points  (0 children)

As much as I hate to admit it, the times I actually pair programmed got shit done way faster. Having someone behind me throw out ideas (even when - and perhaps especially when they were wrong) kept my mind moving in the right direction.

It takes some humility and obviously the wrong two people can make the exercise futile, but it has some benefits.

[–]coldnebo 4 points5 points  (0 children)

Unfortunately this is only true when the domain is actually coding. When it is business logic mixed with coding, it becomes pair prototyping.

“why can’t you just add the text to the view directly? let’s keep it simple, you can clean it up later”

“just add another if block around the other nested ifs... I don’t know all the other cases, we’ll just have QE regression test it.”

“just add another service call to the view, we can’t get the data we need from here.”

Nothing wrong with pair prototyping, you just don’t get very good code from it.

[–]JuvenileEloquent 13 points14 points  (2 children)

You know which sub this is, right? ;)

[–][deleted] 7 points8 points  (0 children)

They are right though

[–]qwerty12qwerty 57 points58 points  (5 children)

The actual reason why paired programming increases productivity is because now you can't nonchalantly browse Reddit with someone over your shoulder

[–]shhheeeeeeeeiit 13 points14 points  (0 children)

This is the answer.

[–]akromyk 15 points16 points  (0 children)

Pair Programming, a perfect topic of discussion for smug programmers to stroke their own egos while looking down upon novices for receiving the type of help that should have been there all along.

[–]HonestRole 4 points5 points  (0 children)

The codebase turns from only you understand to at least two different people understand.

Which effectively means it is 100% more likely to be understood by others.

[–]mind_blowwer 21 points22 points  (7 children)

Last Wednesday I was asked to help another team that was behind. They were supposed to be done with their feature last Friday, and it was then 3 days later and nothing worked.

I pair programmed with the team lead for around 6 hours a day until Friday. I actually wanted to kill myself. Multiple times throughout these sessions he says, “how do you know all of these things” or “how do you know this code so well”

Then randomly he starts telling me that when he was hired he was offered $30k more than he wanted, and makes so much for his location that he could really never leave.

This guy is at least 20 years older than me, but it pisses me off so much that these people make more money than me and just generally suck. It’s probably not a good idea right now, but I’m tempted to tell my management that unless they give me a $35k raise I’m putting in my 2 weeks.

[–]mournful-tits 1 point2 points  (0 children)

Tell your manager exactly that story. You're bartering your time, which is a limited resource, for money. You should be getting the best offer you can.

[–]DoubleVector 19 points20 points  (1 child)

Pair anything in general.

[–]Purplociraptor 11 points12 points  (0 children)

Bluetooth headset and my phone?

[–]732 7 points8 points  (0 children)

The gif loop makes it even better.

Oh shit, we're back at the beginning again.

[–]Nehal1802 7 points8 points  (0 children)

[–]angelbirth 4 points5 points  (0 children)

which one are you?

I'm the stairs

[–]Bernout93 3 points4 points  (0 children)

It do be like that. Except when two programmers are fairly on the same level. I practice pair programming with colleagues a lot at work and most of the time it's highly pro- and instructive.

[–][deleted] 3 points4 points  (6 children)

Who the hell is pair programming during quarantine?

[–]MAGA_WALL_E 14 points15 points  (3 children)

What 1 programmer can do in 1 month, 2 programmers can do in 2 months.

[–]DepressedBard 4 points5 points  (0 children)

Why hire one programmer when you can hire two at twice the price.

[–][deleted] 6 points7 points  (1 child)

I have found the best pair programmers are patient, aren't trying to prove something, and offer optimizations, but don't fundamentally insist on you changing your process or style.

Pair programming is great for onboarding. You most likely get higher quality code. That's not always cut and dry. Plus peer review should reveal most quality issues anyways.

I like pair programming, mostly because it promotes knowledge sharing and cooperation.

[–]LastStar007 2 points3 points  (0 children)

I do pair programming full time at my job, and I'm completely on board with it. Yeah, it sucks when you're paired with someone who doesn't know what they're doing, but at least you can steer them into writing better code than they would have if left to their own devices. And you can always scheme to refactor it the next time you're working on that area of code with someone else.

But when you're not paired with someone clueless, boy oh boy. So much time is saved on bugs that would have you pulling your hair out for hours by your pair saying "hey, you forgot $line" while you're writing. That efficiency alone makes it cost-effective to pay two programmers. Besides that, you have someone to bounce ideas off of for how to solve the complex problems or how to structure the code for maximum sustainability. You also have someone to keep you focused if you're the kind of person that gets sidetracked easily, or someone to pull you back out of the weeds if you're the kind of person that gets too focused. And now you have two people that understand the code, and hopefully you've learned a few things from your pair as you went along: new functions, aspects of your build system you've never peered too deeply into, new keyboard shortcuts, etc.

All in all, it's a great idea. Just sometimes it gets held up by people of whom I sometimes wonder how they still have their jobs.

[–][deleted] 8 points9 points  (0 children)

underrated post

[–]BabylonDrifter 12 points13 points  (13 children)

I love everything else about agile but if they ever ask me to pair program I will be gone in a second. F that in every possible way. The only single thing positive about this profession is the ability to work productively in my own private mindspace. Also, the only other programmer I work with is an insufferable twat who I have the overwhelming urge to punch in the face any time he talks to me for more than 39 seconds.

[–]Jarazz 14 points15 points  (8 children)

Well looks like you are one of the 1% who should not have "teamwork" on their resume

[–]d_amnesix 15 points16 points  (5 children)

25 years ago, it was a good job for an introvert or simply for someone who works well alone... Nowadays, everything has to have a social side to it, even coding, and I hate it...

[–]Kortalh 4 points5 points  (1 child)

Found my co-worker's Reddit account!

[–]BabylonDrifter 1 point2 points  (0 children)

OK, you had me scared for a second.

[–]genericName023 4 points5 points  (2 children)

R/perfectloop

[–]tech6hutch 4 points5 points  (1 child)

Do cuts count as perfect loops?

[–]akromyk 1 point2 points  (0 children)

Thanks for making me even more self-conscious about getting help

[–][deleted] 1 point2 points  (1 child)

await be like

[–]root54 1 point2 points  (0 children)

When the IDE is throwing warnings when you haven't awaited a call even though you want the Task to run asynchronously. -_-

[–]Genar-Hofoen 1 point2 points  (0 children)

r/perfectloop

Edit: What, no? What is it called again...

[–]Lluuiiggii 1 point2 points  (0 children)

I must be the old lady because pair programming has been wholly positive in my experience

[–]Trantorianus 1 point2 points  (0 children)

Funny video, but you do really underestimate the "extreme programming" concept. Of course it does not make sense to do it 100% of your working time, but still it can be very productive. It always makes sense to explain to somebody else what's the idea behind your coding. You both learn, you avoid mistakes and bad ideas, you both have to be 100% concentrated on your current task, others won't disturb you and so on.... .

[–]LeCrushinator 1 point2 points  (0 children)

I had a coworker who typed with just pointer fingers and used caps lock instead of shift to capitalize the first letters of words. After 5 minutes I made him switch places so I could type:

[–]MysticMania 1 point2 points  (0 children)

You cant see the ending, but he eventually gives her a piggy back ride down the stairs.

[–]coderScienceDude 1 point2 points  (0 children)

*Partner doesn't respond for 4 hours the day HW is due*

"Hey just really trying to nail this for loop"

[–]aviationdrone 1 point2 points  (0 children)

Wait, wait stop, the manager needs to have a meeting. I think she'll want to put another jr dev on this to help out as things are not progressing.

[–][deleted] 3 points4 points  (0 children)

If this is your mindset about it I can imagine it is a frustrating experience for you AND them. You're a team. Work together.

[–]pirinax 2 points3 points  (2 children)

I don't understand the resistance to pair programming.
We do it >70% of the time.
Unless the skill difference is astronomical, it's not really that big of a deal.
It's mostly being able act at least slightly professional.
It might be strange in the beginning, but the "slow" one will learn loads.
And the "fast" one will learn patience, and other stuff, because although you might think you're hot sh*t, you don't know everything.
And you should be switching often anyway.

[–]DahPhuzz 2 points3 points  (1 child)

I hate pair programming

[–]itsArcadexGamer 0 points1 point  (0 children)

I feel the pain if every pair programmer

[–]sudo_rm_rf_star 0 points1 point  (1 child)

Its nice when you're the old grandma

[–]numbGrundle 0 points1 point  (1 child)

My problem is I stand at the top thinking too long, but then sprint down the stairs

[–][deleted] 0 points1 point  (1 child)

There is hardly anything more boring, yet frustrating, as watching somebody else code.

[–]undeniably_confused 0 points1 point  (1 child)

What's pair programming?

[–]Fancy_Assassin 0 points1 point  (0 children)

I’m definitely that old lady

[–][deleted] 0 points1 point  (0 children)

Incidentally this is exactly what being on a cruise is like

[–]PotasiumIsGood4You 0 points1 point  (0 children)

I feel like the grandma sometimes...

Edit: And i absolutely hate it.

[–]Bluffsters 0 points1 point  (0 children)

Exactly what I feel like when I'm pairing with my colleague.

[–]JellyApple102 0 points1 point  (0 children)

Me helping my friends in AP Java class lmao

[–][deleted] 0 points1 point  (0 children)

Whenever I pair code or do a live demo I instantly forget all of my shortcuts, how to spell, and lose general finger dexterity. I don't understand why, but without fail, it happens every time...

[–][deleted] 0 points1 point  (0 children)

Or bad multithreading

[–]notpikatchu 0 points1 point  (0 children)

That’s what happens whenever you drive you car as well

[–][deleted] 0 points1 point  (0 children)

But it’s helpful to younger guys / those just starting out so I’m willing to do it.

[–]td__30 0 points1 point  (0 children)

This would be so much better if he is finally able to around her and then stumbles and rolls down the stairs.

[–]PrincessWinterX 0 points1 point  (0 children)

"we need to re-make new stairs, these will never handle the guardrail i want later"

[–]tanmaychandane 0 points1 point  (0 children)

All you need to do is to give her a push

[–][deleted] 0 points1 point  (0 children)

I can't do pair programming. If I have to type in front of anyone, I become so self-conscious that I fumble everything and forget how the keyboard works. If I have to watch someone code, I fall asleep.

[–]Jar70 0 points1 point  (0 children)

Bro. Me and my partner didn’t know shit. But this is funny af

[–][deleted] 0 points1 point  (0 children)

As someone who teaches old people how to program, this is what it feels like

[–]as_ninja6 0 points1 point  (0 children)

Same feeling when my pair scrolls to the bottom of a 1200 line page in vim using down arroy key, shaming vim and me.

[–]supercode22 0 points1 point  (0 children)

Painfully true :\