4 ms·

I know Chris well enough from his writing and some conversations that I can vouch that "resume-driven development" is absolutely _not_ his motivation here. Chr

I know Chris well enough from his writing and some conversations that I can vouch that "resume-driven development" is absolutely _not_ his motivation here. Chris is one of the most thoughtful and insightful engineers I can think of. He has a love of actual programming, but also deeply cares about how programming and technology have an influence on us as programmers and the rest of the world. Given that, this post is him expressing his interest in learning technologies because they look interesting and potentially useful, but also giving reasons to _keep_ learning over the course of your career rather than getting stuck in a rut.

hahahacorn 2y ago
I probably didn’t even need the personal vouch to realize I likely read this with a lens of heavy disdain for rdd. I whole heartedly agree that it’s important to keep learning over the course of your career. And I believe you that the author is aware of the nuance. But I think it’s also incredibly easy to read this piece as “add rust to your .net shop because it’s good for your career”. I don’t know the author. But if I had to pull numbers out of thin air and take a guess, I’d venture 95% of .net shops where an engineer said “let’s do this new thing in rust” was overall a terrible decision for the team and a good decision for the individual engineer, everyone else be damned. It’s wholly unfair of me to criticize the author specifically without knowing the context of the problem he was solving. My original comment was not worded well, but it was not as directed towards the author as it reads as, but more as a general counter commentary to the point the author was making.
- chriskrycho 2y ago
  I think you read into the article some things that weren’t there. The question from the colleague was why I was even interested in learning something we all knew (me included!) we wouldn’t use there. At no point did I propose using Rust at that .NET shop! The whole point was that I was curious about and enthusiastically learning—on the side, on my own time!—a technology that was totally unrelated to my job. Pretty sure the closest that shop ever got to Rust was when I shared interesting bits about it in the company’s wide-open tech talk series, but that series also included folks sharing things like “this cool thing I did with a Raspberry Pi” and “look at what cool hacks you can do with Amazon Alexa” and so on. Long story short, you’re not even responding to what I actually wrote, but to something else that you (probably for good reasons in your own experience) get button-mashed by! (Me too, for what it’s worth!)

hahahacorn 2y ago

I probably didn’t even need the personal vouch to realize I likely read this with a lens of heavy disdain for rdd. I whole heartedly agree that it’s important to keep learning over the course of your career. And I believe you that the author is aware of the nuance. But I think it’s also incredibly easy to read this piece as “add rust to your .net shop because it’s good for your career”. I don’t know the author. But if I had to pull numbers out of thin air and take a guess, I’d venture 95% of .net shops where an engineer said “let’s do this new thing in rust” was overall a terrible decision for the team and a good decision for the individual engineer, everyone else be damned. It’s wholly unfair of me to criticize the author specifically without knowing the context of the problem he was solving. My original comment was not worded well, but it was not as directed towards the author as it reads as, but more as a general counter commentary to the point the author was making.

chriskrycho 2y ago
I think you read into the article some things that weren’t there. The question from the colleague was why I was even interested in learning something we all knew (me included!) we wouldn’t use there. At no point did I propose using Rust at that .NET shop! The whole point was that I was curious about and enthusiastically learning—on the side, on my own time!—a technology that was totally unrelated to my job. Pretty sure the closest that shop ever got to Rust was when I shared interesting bits about it in the company’s wide-open tech talk series, but that series also included folks sharing things like “this cool thing I did with a Raspberry Pi” and “look at what cool hacks you can do with Amazon Alexa” and so on. Long story short, you’re not even responding to what I actually wrote, but to something else that you (probably for good reasons in your own experience) get button-mashed by! (Me too, for what it’s worth!)