People are free to draw inferences about how it would be to pair with this programmer and why they are rarely paired.
In a good pairing environment everyone is learning from everyone. You didn't explicitly say you were looking to learn for others though you also didn't explicitly say you weren't. As far as I'm concerned, in the best pairing environments everyone is always pairing with everyone else, not just seniors with juniors. There is the idea that seniors can actually learn from juniors too since juniors will question things seniors haven't thought about in a long time and are living with "I do it like this because it's the way I've always done it" syndrome.
PS, love the username :)
Well that's the thing. The only reason I'm in a senior position at this company is because I never stopped asking questions and I still don't stop asking questions and learning from people more knowledgeable than me. I used to spend hours sitting at one guys desk just asking questions and listening to rants and just gathering knowledge.
I learned that this was the fastest way to progress and get better at the job, but I'm not finding that juniors and other less experienced devs are doing the same thing because they're worried about wasting people's time. And people are less likely to encourage this behaviour because they have high priority work. I got away with it when I joined the company because the rate of change was so much lower and so things generally just took longer.
I'm pretty jaded by it all. These days I work for a company whose primary business isn't technology and I'm much happier.
I disagree.
>People are free to draw inferences about how it would be to pair with this programmer and why they are rarely paired.
you could. but there's not much to work with. could be helpful but "too valuable" to be a mentor compared to a director or pitching sales or doing conferences. Could be overly pompous and makes things worse. Could simply be office culture and pair programming for more than 15 minutes isn't a thing (like all my previous jobs).
All are extreme assumptions that aren't productive to talk about. Personally: I don't know if I'd want to be in those cultures that enforced pair programming X times a week, but I wouldn't mind , say, a day a month where I could shadow a lead or vice versa and get some intimite knowledge, be it in correcting some pitfalls in my coding or seeing how a more experienced mind ticks. But the chance hasn't come up yet.
I wonder how often I've made a comment and gotten no engagement. This quote seems to have gotten more engagement than the original comment. And quite emotive engagement.
Makes me wonder what that means. Is it genuine curiosity? Or is the quote saying something that the original commenter couldn't see themselves? It's interesting they suggested if I was insinuating something negative about them.
Importantly, they did not ask me. They told me. That too tells us something about what pairing experience with them would be.
The word for that is "trolling".
> Importantly, they did not ask me. They told me. That too tells us something about what pairing experience with them would be.
I asked and you avoided answering. What does that tell us?
Oh that is fascinating, so highlighting a verbatim quote, in context can be trolling?
What that makes me think of is that people are in denial about what the quote tells us and have displaced those feelings on to me! Amazing stuff.
> I asked and you avoided answering. What does that tell us?
This is interesting because no you didn't ask me what it tells us. You asked if I wanted to say something and I answered that the quote stands alone.
Really interesting stuff in this thread!
But at the moment I have work to do and deadlines to meet, so it's a hard sell to suggest stepping back from active development and focusing more on incubating our less experienced devs. Even though it's better in the long term, and my manager would even agree on that, important short term projects just take priority.
I don't actually say it though because I don't know how to express it.
Which senior manager is this, out of interest?
Mentorship is hard, regardless of management buy in :/
- code isn’t changing in code review except for really good reasons
- people who need help are reaching out
- projects that need help get additional help brought in
what else are you looking for? this example is about as pair programming as it gets at most places. they’re called silos when people don’t like them and layers of abstraction otherwise but they’re the same thing: no team will have 100% shared info on all parts and knowledge transfers on exits are a decent step to bridge this
if you want to teach the team more, teach them more. usually the best way to do this is in code review. it’s direct comments on code. write a good review you want more people to see? post it in the chat. set up additional time to share ideas with the team. all of these things you can do as an IC while producing code
sorry but this post comes off as “i’m smarter than everyone.” i’m guessing the reason management hasn’t gotten your message is the message isn’t clear. what exactly do you want to do? and what do you need their help for?
Now, as a reviewer your spidey sense tingles and you get the feeling there's a better way. But now it's significantly more effort to pull that change apart or start from scratch and experiment with a new approach, then write this all up on the pull request with the caveat "but what you've written works, so in the interest of time we can merge this".
Pair programming would get you on the right track from the start. You are able to assist an inexperienced dev and guide them through the process step by step. Imbuing your knowledge, raising questions, suggesting fixes. This is exactly what the blog post describes. The developer was seen as unproductive because their time was spend pair programming rather than directly doing the work themselves.
I don't see how my post comes across as "I'm smarter than everyone". I know things that less experienced developers don't know, and that's a fact I know from talking to them and reviewing their code. But the culture just isn't there to be able to spend significant portions of my day effectively being their teacher (which I would love to do!). Instead it's often "the blind leading the blind" while the more senior members of the team are off delivering important projects and not having the capacity to imbue their knowledge onto the less experienced members of the team.
It's a culture thing and I wouldn't say it's a good environment for nurturing new staff. Spending 2 hours in a Teams call or at someone's desk is uncomfortable for both parties in a company that doesn't encourage this sort of collaboration. And so there's a sense to not "waste someone's time". The person you're helping sees themselves as a burden rather than seeing themselves as a student. And as a teacher, you're conscious of the other work you're supposed to deliver because it's not expected for you to be spending significant parts of your day pair programming.
this is your issue. you’re approving prs due to perceived time constraints that you wish you could say no to. are these time constraints real? even for significant prs of 1-2k lines responding to a comment of rewrite another way only takes 1-2 days. code review isn’t about finding the best solution. it’s the best solution given the current trade offs. things to ask yourself are
- are the time constraints real?
- does the team agree on the “right” way?
if there’s time constraints sure i get it. these are external commitments. public deadlines. it’s hard to ask for additional work like this. but in my experience these are rare. usually management is smart enough to avoid external deadlines
does the team agree this is the right way? are you pushing your own narrative? if it’s a team strategy, it’s very easy to tell people to rewrite an entire pr for. if it’s your opinion but you can defend it, make your case, and if it’s strong you can still get someone to write it. is this so bad it’s going to be rewritten soon?
> the more senior members of the team are off delivering important projects and not having the capacity to imbue their knowledge onto the less experienced members of the team
i thought you were saying you are this senior engineer?
i don’t get this. you want to spend more time helping people but think it’s uncomfortable to be on a call with someone for 2 hours getting through a problem. you want to pair program and feel this way about a shared coding session? i’ve spent literally 7 hours on zoom screen shares. if you’re actually helping people they appreciate it
you say the culture isn’t there to support this but then list examples of good places you could create this culture and choose not to
if you truly are this smarter, better engineer that should spend all your time helping your team, why aren’t you doing these things on your own?
You can me ask "why don't you do X". And the answer is that the culture does not support it. I have work to do, work I've been given because as senior members of the team we are pushed into bigger and more important projects. The less experienced members of the team just have more time to do things.
For me to spend 7 hours a day sitting in a call with someone would mean 7 hours of not delivering work that my manager and project managers expect to be delivered. No person in the business is going to want to spend 7 hours on a call because the culture does not encourage it. This is why I said it is uncomfortable for both parties. Taking hours of someone's time isn't seen as a good thing, it's seen negatively. Of course the person you're helping appreciates it. But the culture makes them feel guilty for asking.
Should that be the case? No. Is that the case? Yes. Am I working toward that not being the case? Yes.
I don't know why you think I'm not trying to change the culture. I've literally listed all the issues and ways to fix it. It's not an overnight switch.
I was on a team that paired all the time and it's sort of ruined me for anything else. We switched pairs daily and everyone would pair with everyone else (on the team). When a junior joined the team they would very quickly lose their junior status.
The important part of pair programming isn't really the programming per se, it's the discussion.
It also requires some amount of conversational art. As for being self conscious about things, you would have poor coworkers who make you think that or some unfounded worry. A good pair programmer can have a discussion without making you feel like an idiot - much the same as a good code review.
Copilot is as much a pair programmer as stack overflow is... So not at all
But it's usually contained to someone like a junior calling me up and saying "can you help me?". The answer is always "yes of course!" and I share as much as I possibly can. But it ends there.
I just want to sit down and show them things. Teach them in a way that makes things "click" the way I found they clicked with me. But I don't think management really values this approach. We get siloes of knowledge and then when someone leaves it's all hands on deck to transfer that knowledge.
I'm often brought onto projects as a firefighter because I'm seen as productive. But I think the more important thing for the team would be to have me upskill everyone else below me. But for whatever reason, it's hard to get that point across to management. I can see myself in a few people and that they have potential, they just need encouragement.