I'm shocked you made it 3 years. I did a stint trying to do what they call "mob programming" and felt borderline suicidal. I couldn't think because I was consta

I'm shocked you made it 3 years. I did a stint trying to do what they call "mob programming" and felt borderline suicidal. I couldn't think because I was constantly vocalizing what I was doing. Nothing added up and every ticket felt like it was just a hodge-podge of different ideas with no real flow. Lord help you if someone wanted to disagree. Now you have to completely stop your worker thread and handle that. There was no art to it. Its just one robot and two guys standing behind you ordering you to do this or that. I found it impossible to reach a flow state and produce actual good work. I left every session feeling like I accomplished nothing for myself. I am not attached to my code, but I am attached to my accomplishments. When all your work is atomized between people you are effectively no one. In this case, I believe, it's better off to leave. Pair programming in moderation can be enlightening. Much like traveling to a different town as an artist to learn from other artists. Too much of it and you lose your identity. It is completely possible to remain detached from your work but still desire to work mostly alone on your own tickets. Code ownership is a silly concept. On one hand everyone suggests being detached from your work. Yet everyone simultaneously realizes having your name in a PR matters. I make a habit of crediting people who worked with me in the PR message. It's pretty simple.