cooperative-software-development icon indicating copy to clipboard operation
cooperative-software-development copied to clipboard

Productivity: Clarify learning barriers

Open amyjko opened this issue 4 years ago • 0 comments

There are two aspects that I'd like to mention about the article. The first is a really small nuance, but it was during the section about barriers that programmers come across when learning new languages and frameworks. That section reads very much like a list, and its formatting as a paragraph made it a little harder to read in my opinion. I think a list, though space inefficient, would have made each barrier easier to separate and identify. The second thing is about the last paragraph talking about inequities that could result in reduced performance. While I understand that the series is focused on programmers, these same issues plague other industries and even roles within an engineering team. It's just a small detail, but mentioning that would help bridge this article even better to the previous article about what makes a great team and a great engineer. There is a paragraph that discusses six different types of content that are challenging in the process of learning a new programming language. I hardly understand this paragraph and need to be better explained in terms of wording. For instance, there is a sentence, "People need to overcome selection barriers". In this sentence, I don't understand what does selection refer to here as it is too vague. Another sentence says "People need to overcome use and coordination barriers", I do not understand what is meant by use and coordination here. In my opinion, it would be nice if there was a more detailed explanation of these words since it still seems too vague right now.

amyjko avatar Oct 20 '20 18:10 amyjko