3 ms·

The author sees technology as something mutable but doesn't consider humans/relationships to be that. He can either work with inflexibly, unalterably "good" or

The author sees technology as something mutable but doesn't consider humans/relationships to be that. He can either work with inflexibly, unalterably "good" or "bad" people (as measured by skill or motivation). I would hope that understanding people would mean seeing them with a bit more depth. (Also, he doesn't really make a case for his thesis.)

mooreds 4y ago
Author here. Thanks for the feedback! I think that different people can be good or bad in different roles, organizations and times in their lives. Sorry if that didn't come through. This is a blog devoted to new devs, and one thing I've seen new devs focus on (myself included) is technology as a solution to all the problems. I was hoping to illustrate through this post that the technology matters less than people (their problems, their strengths).
- catiopatio 4y ago
  New developers have the most to learn about technology. Teaching them that technology is less important than “people” is counterproductive and harmful unless you anticipate them moving to a PM, managerial, or technical sales track. Furthermore, as someone who just replaced a roof, “I did not care one whit about the shingle type” is frankly insane. As a homeowner, you are your only advocate. If you don’t care, you will be taken for a ride — either by someone actively malicious, or purely incompetent. Applying the point more broadly, somebody trusted in a position of authority must understand the technology, or you’ll get poor technology. Developers are supposed to be that somebody trusted in a position of authority. I looked up your title — “Head of Developer Relations”. Of course people matter more than technology for you — you’re not a developer! People are literally your job!
  - mooreds 4y ago
    > Teaching them that technology is less important than “people” is counterproductive and harmful unless you anticipate them moving to a purely PM or managerial track. I intensely disagree with this statement. Of course technology is important, but so is (for the vast majority of tech jobs) working with people. I'm not talking about managing people, I'm talking about understanding customers and/or team members. Teaching new developers that they need to not only be concerned with the tech they are using, but how they are using it and to what (human focused) goals, is critical to people's careers. > Furthermore, as someone who just replaced a roof, “I did not care one whit about the shingle type” is frankly insane. Different strokes for different folks. I found someone who'd done work for others that I could ask about, checked his references, and trusted his advice. I don't want to have to become an expert on everything, I want to delegate that (as other comments mentioned). > Applying the point more broadly, somebody trusted in a position of authority must understand the technology, or you’ll get poor technology. Absolutely agree. But you can also say: "Applying the point more broadly, somebody trusted in a position of authority must understand how to apply the technology in such a way as to benefit people, or you’ll get poor results and unused technology." That's my core point. As technologists we have a deep rooted understanding of the importance of technology. But we (myself included) often lose sight of the actual purpose of the technology and its use.

mooreds 4y ago

Author here. Thanks for the feedback! I think that different people can be good or bad in different roles, organizations and times in their lives. Sorry if that didn't come through. This is a blog devoted to new devs, and one thing I've seen new devs focus on (myself included) is technology as a solution to all the problems. I was hoping to illustrate through this post that the technology matters less than people (their problems, their strengths).

catiopatio 4y ago
New developers have the most to learn about technology. Teaching them that technology is less important than “people” is counterproductive and harmful unless you anticipate them moving to a PM, managerial, or technical sales track. Furthermore, as someone who just replaced a roof, “I did not care one whit about the shingle type” is frankly insane. As a homeowner, you are your only advocate. If you don’t care, you will be taken for a ride — either by someone actively malicious, or purely incompetent. Applying the point more broadly, somebody trusted in a position of authority must understand the technology, or you’ll get poor technology. Developers are supposed to be that somebody trusted in a position of authority. I looked up your title — “Head of Developer Relations”. Of course people matter more than technology for you — you’re not a developer! People are literally your job!
- mooreds 4y ago
  > Teaching them that technology is less important than “people” is counterproductive and harmful unless you anticipate them moving to a purely PM or managerial track. I intensely disagree with this statement. Of course technology is important, but so is (for the vast majority of tech jobs) working with people. I'm not talking about managing people, I'm talking about understanding customers and/or team members. Teaching new developers that they need to not only be concerned with the tech they are using, but how they are using it and to what (human focused) goals, is critical to people's careers. > Furthermore, as someone who just replaced a roof, “I did not care one whit about the shingle type” is frankly insane. Different strokes for different folks. I found someone who'd done work for others that I could ask about, checked his references, and trusted his advice. I don't want to have to become an expert on everything, I want to delegate that (as other comments mentioned). > Applying the point more broadly, somebody trusted in a position of authority must understand the technology, or you’ll get poor technology. Absolutely agree. But you can also say: "Applying the point more broadly, somebody trusted in a position of authority must understand how to apply the technology in such a way as to benefit people, or you’ll get poor results and unused technology." That's my core point. As technologists we have a deep rooted understanding of the importance of technology. But we (myself included) often lose sight of the actual purpose of the technology and its use.