4 ms·

This seems very similar to the premise behind "So good they can't ignore you" by Cal Newport [0]. I haven't got around to reading it yet, but I'd be interested

by J-dawg 8y ago

This seems very similar to the premise behind "So good they can't ignore you" by Cal Newport [0]. I haven't got around to reading it yet, but I'd be interested to know if anyone here found it useful. [0] https://www.amazon.co.uk/Good-They-Cant-Ignore-You/dp/0349415862 https://www.amazon.co.uk/Good-They-Cant-Ignore-You/dp/034941...

rpeden 8y ago
I read it, and I found it very useful. In particular, I used the advice in the book to help me stay motivated when working on code bases that old, large, occasionally crufty, and once in a while downright nasty. Over time, I've grown to actually enjoy this kind of work. And as it turns out, it's pretty useful to enjoy the 'dirty jobs' of programming. Companies don't run big old code because they're on love with it. They do it because the code is making them money. And because it's making them money, and they know it, they're not afraid to pay to improve it. And the neat thing is that when working on this kind of code, you often get to work with fun newer bits of tech, too. For example, there's no reason you can't use React to spice up an old ASP.NET Web Forms site, as long as using React is the best/fastest way to deliver value for the task you're trying to accomplish. I'm not sure if any of that it useful, but at least it's one bit of data indicating that the book motivated someone to push through the pain and become good at (and enjoy) something that wasn't a passion at the start.
theLotusGambit 8y ago
I'm a big Cal Newport fan. Compared to other authors I've read, his books seem to have a good mix of practical, technical, and high-level advice. "So Good They Can't Ignore You" in particular is absolutely worth the time to read
FormFollowsFunc 8y ago
I’ve just finished reading it. He comes up with a series of rules and backs them up with anecdotes though I don’t think they are thoroughly tested. But they do help you think about it more deeply. It helped bring these different ideas I’ve heard before into a more coherent form. Though personally I think you should follow what you’re interested in or suited to as it makes it a lot easier.
skadamat 8y ago
I help people get data science jobs for a living (and I'm an otherwise annoying career advice giver to others) and this is the ONLY book I recommend everyone to read. I've read it probably 10 times and it's a quick read, finds a good balance between stories and developing his framework further, but much harder to implement the advice. But he installs a powerful mental framework for thinking about careers and gives you a new way of looking at the world. You may not see "results" immediately, but it really helps you focus on how to determine what work traits are meaningful for you and the types of career moves you should make to match. Deep Work is an excellent follow up on the tactics / daily practice, and also a must read for knowledge workers.
jarrettch 8y ago
Didn't read the article yet, but this is the premise behind that book and a lot of the writings on his blog. I highly recommend this book as well as Deep Work if you're a knowledge worker. One of the bigger points he makes is putting in the hard work and eventually you'll get to a place where that thing develops into your passion and affords you lots of free time, flexibility, autonomy, respect, etc...

by J-dawg 8y ago

rpeden 8y ago

I read it, and I found it very useful. In particular, I used the advice in the book to help me stay motivated when working on code bases that old, large, occasionally crufty, and once in a while downright nasty. Over time, I've grown to actually enjoy this kind of work. And as it turns out, it's pretty useful to enjoy the 'dirty jobs' of programming. Companies don't run big old code because they're on love with it. They do it because the code is making them money. And because it's making them money, and they know it, they're not afraid to pay to improve it. And the neat thing is that when working on this kind of code, you often get to work with fun newer bits of tech, too. For example, there's no reason you can't use React to spice up an old ASP.NET Web Forms site, as long as using React is the best/fastest way to deliver value for the task you're trying to accomplish. I'm not sure if any of that it useful, but at least it's one bit of data indicating that the book motivated someone to push through the pain and become good at (and enjoy) something that wasn't a passion at the start.

theLotusGambit 8y ago

I'm a big Cal Newport fan. Compared to other authors I've read, his books seem to have a good mix of practical, technical, and high-level advice. "So Good They Can't Ignore You" in particular is absolutely worth the time to read

FormFollowsFunc 8y ago

I’ve just finished reading it. He comes up with a series of rules and backs them up with anecdotes though I don’t think they are thoroughly tested. But they do help you think about it more deeply. It helped bring these different ideas I’ve heard before into a more coherent form. Though personally I think you should follow what you’re interested in or suited to as it makes it a lot easier.

skadamat 8y ago

I help people get data science jobs for a living (and I'm an otherwise annoying career advice giver to others) and this is the ONLY book I recommend everyone to read. I've read it probably 10 times and it's a quick read, finds a good balance between stories and developing his framework further, but much harder to implement the advice. But he installs a powerful mental framework for thinking about careers and gives you a new way of looking at the world. You may not see "results" immediately, but it really helps you focus on how to determine what work traits are meaningful for you and the types of career moves you should make to match. Deep Work is an excellent follow up on the tactics / daily practice, and also a must read for knowledge workers.

jarrettch 8y ago

Didn't read the article yet, but this is the premise behind that book and a lot of the writings on his blog. I highly recommend this book as well as Deep Work if you're a knowledge worker. One of the bigger points he makes is putting in the hard work and eventually you'll get to a place where that thing develops into your passion and affords you lots of free time, flexibility, autonomy, respect, etc...