Hard work vs. Long work (2011)
seths.blog
Hard work vs. Long work (2011)
1–10 of 62 posts
Re: Hard work vs. Long work (2011)
#2Re: Hard work vs. Long work (2011)
#3Important point: "Hard work" doesn't mean it has to be feel hard for you to do it.
If you have fun setting up a K8s cluster, that's still hard work.
Re: Hard work vs. Long work (2011)
#4Somewhat related, from Andy Matuschak whose notes were on here earlier today, on the feeling of progress when doing open-ended work:
https://blog.andymatuschak.org/post/159979927467/satisfactio...
Re: Hard work vs. Long work (2011)
#5Important point: "Hard work" doesn't mean it has to be feel hard for you to do it. If you have fun setting up a K8s cluster, that's still hard work.
One thing I've found interesting is that the first time I do something related to tech as long as it isn't mind boggling frustrating cough Oracle cough I enjoy learning it. The second and third times it's tolerable, but if I have to keep doing something repeatedly the only way I can enjoy it any longer is by listening to an audiobook while doing it or by automating it.
As soon as I set myself to automating I realize that I like it again because now I am interacting with it in a new way.
Re: Hard work vs. Long work (2011)
#6Re: Hard work vs. Long work (2011)
#7I prefer the labels "predictable" vs "unpredictable" work. For example, I've been experience the difference between research and back-end web dev work lately, and the main difference is that for research you don't know if it will pan out, while for back-end work you're almost always making incremental progress towards the end-goal. But I wouldn't necessarily call research "harder", it's just different. It's usually more difficult conceptually, but there's also way less stuff you need to keep in your head at the same time.
Re: Hard work vs. Long work (2011)
#8Important point: "Hard work" doesn't mean it has to be feel hard for you to do it. If you have fun setting up a K8s cluster, that's still hard work.
Not sure setting up a k8s cluster qualifies as "hard work" the way the author describes it. It seems by "hard work" he means work requiring novelty, creativity or insight, not simply intellectual work.
Re: Hard work vs. Long work (2011)
#9Important point: "Hard work" doesn't mean it has to be feel hard for you to do it. If you have fun setting up a K8s cluster, that's still hard work.
yes I think that's key, I imagine a typical 2 axis analysis for this, where one axis is hard/long and the other is passionate or not passionate about it.
But I think there are more dimensions to it, as the article points out sometimes we shy away from hard work, because it's uncertain and your identity is on stake, you can fail, and I agree it takes that leap.
I'd say it is a leap of faith, because sometimes you don't know if it is hard work that is relevant, and worth, or not, I've never been an academic, but I guess many PhD feel that way ?
Re: Hard work vs. Long work (2011)
#10Using his definitions, I hate long work.
I avoid long work, I'll take hard work always.