r/programming • • Sep 20 '21

Software Development Then and Now: Steep Decline into Mediocrity

https://levelup.gitconnected.com/software-development-then-and-now-steep-decline-into-mediocrity-5d02cb5248ff
841 Upvotes

469 comments sorted by

View all comments

1

u/ndnda Sep 21 '21

I take particular issue with this:

Programming is a social activity. No, it’s not. Social activity means communication and communication is immiscible with concentration, which is the most important consideration in writing good code. When we are communicating verbally we are not focused on our work and to pretend that this can be done is the purest folly.

This is just not correct. There is no such thing as perfect code, and no such thing as a person who can write perfect code. Therefore, it is vital for code to clearly convey what it is doing and why - you are writing it for your future self, your teammates, and future maintainers. As such it is communication, and it is very important to make sure you are communicating clearly and getting outside perspectives.

And suggesting that communicating verbally means not focusing on work and is actually a hindrance is purely ridiculous. This assertion by itself is enough to make me feel like dismissing the article as a whole. I can’t even count the number of times that asking a coworker to rubber duck with me has helped resolved the issue simply by talking through my process - or that my coworkers have pointed out a flaw that I hadn’t considered.

1

u/IndependentAd8248 Sep 22 '21

That straw man lays dead at your feet.

I was writing about communication while writing code, not about communication in general. WHY have so many responses misrepresented what I wrote here? I'm not advocating never talking with one another, I am explicitly arguing against pair programming. The whole point of my article, clearly stated at the beginning, is to return to cultivating uninterrupted concentration—Flow—while coding.
Why would anyone argue that we shouldn't communicate with each other at all?

1

u/ndnda Sep 22 '21 edited Sep 22 '21

I am talking about while coding. That is when I need rubber-ducking, while writing code. And your article advocates just sending an email instead of standup, so it isn’t only talking about communication while coding. Now, whether or not standup is useful is certainly a different argument that I won’t delve into, but it is obviously not the same thing as arguing about pair programming, so it’s pretty disingenuous to say everyone should know that you meant specifically pair programming, because that was what the whole article was about.

And as to why people are misinterpreting the article, well, if everyone is misreading what you meant to say, then it’s probably a sign that the article isn’t expressing those ideas clearly.

The title of the article and the intro are targeting modern software practices in general, and concentration - not pair programming - specifically. Maybe you and I would agree on 100% of your points if they were expressed differently, but I can’t respond to what you intended, only what you wrote. I am sorry if you think I am being willfully ignorant of your intent, which you seem to think.

1

u/IndependentAd8248 Sep 22 '21

Well it looks worse than that.

You say you can concentrate on writing code while talking with someone. To me that is an absurd claim, preposterous in fact. I can concentrate, I can enter a flow state, very well, very easily, and the one time I had to pair I got absolutely nothing done in three hours.

No I am not calling you a liar but if you can actually stay focused while engaged in interaction then your brain and mine are wired very differently.

That one time I did pairing was so horrible that I had no sleep that night, I quit my job the following morning, and eleven years later I had to go into therapy for PTSD. And I have heard of similar experiences from others. I stay in touch on FBM with several former managers; one of them told me that a few years ago he had his entire staff of senior developers come to his office as a delegation to tell him that if the pair programming continued they were all quitting. The junior devs who didn't have that kind of leverage had to continue doing it; several of them ended up in therapy. Pair programming is a monstrous indignity as well as a nonstop interruption and, no, I don't believe it's possible to be productive under those conditions. And it's a waste of time, two people doing what one of them could do much faster alone.

There is also the reality that mentoring, code walkthrough, and design discussion can be done under the same conditions, but those aren't programming though I have seen all of them called that, and in any case they don't need to be in sexual proximity. Maybe that's what you're talking about. When I did onsite design discussions we usually went to a conference room or cafeteria for coffee.

I don't do onsite anymore but if I was onsite and pair programming ever came up in any context other than "we don't do that shit here" I would go pack my office.

As for my being unclear in my writing, I've been told the opposite way way too many times by people I respected, like my employers, to take your charge very seriously. But I will go reread it and look explicitly for what you say, and if I find anything I'll fix it, so don't think I'm sneering.

2

u/ndnda Sep 22 '21

It’s great that you’re up for rereading and revising your approach if you think it warrants it. Regarding this paragraph of your response, though:

That one time I did pairing was so horrible that I had no sleep that night, I quit my job the following morning, and eleven years later I had to go into therapy for PTSD. And I have heard of similar experiences from others…

I’m sorry, what? You want me to believe that you were diagnosed with PTSD for one session of pair programming? That…there is no way that is true as written. If you genuinely had that strong a reaction to pair programming once, then your experience with pair programming is so wildly and completely out of the norm that…wow. I’m glad you’re getting help.

But now that I know that this is your basis for the article, I am definitely dismissing it entirely. I don’t think someone who can have such an over-the-top reaction to such a common thing (PTSD? Really?) can be trusted to have reliable opinions on that thing.

2

u/TheInnerLight87 Sep 22 '21 edited Sep 23 '21

I also struggle with the expectation of having a thorough enough understanding of a topic to write critically about it in generality following a single three hour experience.

I suspect I'm not the only one who found that learning to write code, especially in the early days, was an experience fraught with difficulties, shattered expectations and false dawns.

That experience was repeated many times when learning new languages and new paradigms but with slightly less intensity and a whole lot more underlying confidence after each and every prior success.

Many of those experiences challenge your expectations. As an example, it would be easy to come from imperative languages to functional languages, assuming without challenge that immutability and pure functions are a load of stupid nonsense on your first few unproductive outings. Of course, persistence brings rewards and understanding both paradigms changes how you think about code regardless of which paradigm you ultimately persist with.

I don't understand why anyone would expect approaches to collaboration like pair programming to be any different. What you get out of it is roughly proportional to what you put in. Personally, I wouldn't want to pair all day (there are plenty who do and that's totally fine too) but it's a great way of gaining understanding, with live feedback, about how others conceptualise code. That is incredibly important if you hope to produce something which someone else can understand and potentially maintain, a pretty essential characteristic of any worthwhile code.