> there is an important distinction between “working hard” and “maximising the number of hours during which one works”. In particular, forcing oneself to work even when one is tired, unmotivated, unprepared, or distracted with other tasks can end up being counterproductive to one’s long-term work productivity, and there is a saturation point beyond which pushing oneself to work even longer will actually reduce the total amount of work you get done in the long run
Worth highlighting, for those of you that are skipping through.
Great point. I like to compare work capacity to exercise capacity. Too much exercise will actually harm your fitness rather than improve it. However, reasonable exertions, combined with appropriate rest, will improve your fitness over time.
Like exercise capacity, one's ability to work hard can also be improved through practice. This doesn't mean pulling all-nighters and chugging caffeine to override the sleepiness, though. It means setting incremental goals to try a little bit harder and then following up with proper rest and recovery.
For example, if you install time tracking software and measure that you spend 3 hours in your code editor every day (a reasonable amount for someone working an 8-hour day, due to time spent reading documentation, in meetings, and other activities), it would be a mistake to set a goal to spend 6 hours in your code editor. You'll get burned out and hate it.
However, if you set a goal to spend 3.5 hours in your code editor every day, you can likely find low-impact ways to make that happen. Maybe you're more efficient with transitioning from meetings back to coding. Or maybe you cut down time spent reading articles on HN or Twitter by 30 minutes and apply it to coding instead.
Over the course of a 5-day work week, that extra 30 minutes per day adds up to almost 3 hours extra work. If your starting point was 3 hours per day, you've basically added an extra work day to your week without giving up much.
"However, if you set a goal to spend 3.5 hours in your code editor every day"
I would be careful trying to set up such metrics for yourself.
I can stare for hours at code and not getting anything done. Then away from the screen on a walk or sitting down with pen and paper I solve the problem and implement it in 15 min in code.
My point is, I would focus on a tasklist. Clear things to do at once. (Or in parallel if they are trivial.)
Getting things done, not spending time doing things.
Some days you will quickly burn through six tasks on your list because they turn out to domino or all be easy or something else. Sometimes, a single item will take three days even with honest effort and deep work.
If "tasks done" is your metrics, you will get just as burned here.
As with all long-term habit building, I think the key here is identity forming. Be convinced that you are a person that (for example) cares about exploring their field with side projects and then ask yourself: "What would this person do?"
If you believe yourself, you will then both fight through your tasklist or do X hours of honest works and find that the actual system does not even matter that much.
I've had it pretty negatively affect my experience of using macOS due to hyperlinks taking seconds to open throughout the OS. Uninstalling it fixed the issue. I still haven't found a good alternative and am a bit sad about it.
Hey, Daniel here, the founder of Timing. I haven't had reports from other customers about Timing slowing down URL opening. In fact, as an engineer myself, I spent a _lot_ of time optimizing Timing's tracking to be as efficient and unobtrusive as possible.
If you'd like to give Timing another shot, would you mind reaching out via https://timingapp.com/contact with details on the OS version and Timing version you used, as well as the apps the problems occurred with? If you need a new trial to reproduce the issue, just let me know and I'll set you up with one.
Seconded, I tried to push harder on too many fronts and overloaded my brain/memory to the point of physical pain (if that makes sense)
Patience, sensitivity and regularity is my best bet now. Also, it's fairly well known that a lot of ideas and understanding comes outside/after workouts.
ps: this is also true in music (which blends physical and intellectual sides)
I think there's an important point here too that cuts against a lot of memes: it's important to keep working hard right up until this point. A lot of people presume that if they put in a solid day's work they're going to do just as well as someone who is a "work-a-holic." That's not a great mental model, if the work-a-holic is working more but not so much they are hitting these problems mentioned. There's a fairly wide margin between underwork and overwork.
edit: Lo and behold my sibling is taking on one of the memes I mentioned. :) If you're working less because you feel it's doing too much in the favor of your employer, and not because you're otherwise going to start becoming less productive because of it, you're probably underworking in the sense outlined here.
> A lot of people presume that if they put in a solid day's work they're going to do just as well as someone who is a "work-a-holic."
There are two kinds of workaholics - the ones who enjoy work and those who suffer from their work.
The article hits on the first kind in the passing
>> Of course, to work hard, it really helps if you enjoy your work.
Working hard when you enjoy your work is easier and might look like workaholism to someone who is definitely not. If work is play, you might play longer & that gets a lot done, because mistakes you throw away don't feel like wasted time.
The workaholic that people knock are the ones who work because it gives them positive feedback they lack in the rest of their lives - from an inattentive parent, disrespectful spouse or demanding children.
My work environment is extremely gamified and well designed to give me great feedback to improve, excellent rewards for performance and throw in some respect of my peers. The home life is Sisyphean in comparison - cook dinner today and it doesn't lie on a progression towards cooking less tomorrow.
It's easy to get sucked into that and work on a death-march, because it feels like progress on a daily basis. That "How we built Internet Explorer" tweet felt very familiar to me, because I would definitely get sucked into a mission like that.
> >> Of course, to work hard, it really helps if you enjoy your work.
> Working hard when you enjoy your work is easier and might look like workaholism to someone who is definitely not. If work is play, you might play longer & that gets a lot done, because mistakes you throw away don't feel like wasted time.
Exactly, and it's a misnomer to call that hard work. When someone enjoys their work, the work is easy. They are not "hard workers". You falsely believe they are hard working because you personally would not enjoy doing that work and would therefore not be motivated to work as much. But that only means that the work is hard to you, it doesn't mean it's hard to them.
I would disagree with this. Many professional athletes love their work, but that doesn't make training, recovery, and competition a walk in the park...professional athletes are the pinnacle of hard work because many of them have to utilize the 24 hours in near perfection to stay at the top.
Also, often the reason that someone enjoys their work is directly because it IS difficult. And the payoff from solving hard problems can be amazing and worth it. Alternatively, people who are pigeon holed into mundane or uninteresting work in their career will find dissatisfaction, even if the tasks are incredibly easy.
I feel in general by "hard work" people imply "putting in the time and effort". And I still contend, people who do put the time and effort into something probably find it easier to do so than those who don't.
Let's say that "putting in time and effort" is the key to success, aka, "hard work" is the key to success. Alright, now what if you're finding it hard to "put in the time and effort"?
I would say if you find it hard to put in the time and effort, you need to either find ways to make it easier, or find something else which you find easier to put in time and effort into.
I'm not sure if my point will land, but see, for me, the real trick to success is to find something that is easy for you to put in time and effort into. And I think a lot of successes are attributable to that, yes successful people did put in time and effort, but it was easier for them to do so, and that's why they are successful at it.
I get that. I think the definition of success obviously varies a lot as well, but if we talk about the upper echelon of anything, eventually everyone is putting in the time and effort, but there are people who are still above and beyond everyone else in that upper echelon. So the question becomes, whats the difference?
It's mostly luck most of the time, and that includes the amount of motivation you have to go beyond in that venture.
This is mostly my opinion, but the evidence I've seen over the years lead me to conclude this too.
How motivated you are at one thing, and how exclusively focused your motivation is, from what I've read, is mostly luck. But beyond that, there's a lot of factor purely driven by luck, your genetics, your environment, the time and place of your efforts, etc.
> it's important to keep working hard right up until this point
As a pretty hard worker who is very far from workaholic, I strongly disagree. Work hard. It's super important. Put the time in or else you won't progress. But you don't need to go right up to the edge. If you put in solid work reliably for years, other factors will matter so much more than whether you go right up until that point.
> it's important to keep working hard right up until this point
I'm not sure there's any real empirical evidence for this in the absolute way you stated it.
There are plenty of highly productive creative people who do 4 hours of highly focused work a day and then spend the rest of their time walking around a garden. If your goal is to produce great lasting work that seems to be a formula that works a lot.
Working up to your limit is useful for other scenarios, like where you want to crank out much more routine work. If you want to get promoted in a structured environment like a big tech company, then this strategy works well.
There are definitely cultures that value working long hours. You see it both in business and in academia, and I'm not aware of any evidence that it's better than the system where you empower workers to focus on as they need to and then take the time they need to recharge.
This really is important. Exhortations to work hard seem a bit tone-deaf right now. I'm a person who's been self-employed and therefore self-motivated, driven, and devoted all hours of day and night to realizing ideas and products for the past 20+ years, organizing my own time in ways I've always noticed 9-5 friends find difficult to understand. Once I get into an idea or a big piece of code, I can get lost for days, forgetting to eat or shower. But that's always been balanced by an active social life, travel, exercise - things that help me maintain a psychological equilibrium while helping me structure my own time. Covid has upended the outlets I depend on for sanity to the point where it's very hard to get into the flow of work and research I need to commit myself to in order to accomplish long tasks. So I'm really trying to be gentle and easy on myself when I don't want to work up to the breaking point... or even of days where I don't want to do any serious work at all. Maybe this is a bad thing, but before lockdowns I never felt like I had to make myself work at all... I just wanted to, and nothing could take me away from it. Usually one big night out would be enough to motivate me to spend the next week happily locked indoors of my own volition. But without that balance... you just have too much time.
Because working hard can mean skimming articles or delegating it to someone else to get you the gist of it. I don't have time to read every single interesting sounding article I come across. Well maybe I do, but then I wouldn't have as much time for commenting :)
It does also apply to companies who demand that their workers have bums on seats in an office 8-9 hours a day...
Companies often don't seem to understand that loading employees with meetings and bureaucracy, then wondering why productivity isn't higher, is fairly foolish.
This is a very important distinction. I realized over time that what I wanted out of work was not a job where I lived at the stupid office, but not one where I was twiddling my thumbs all day either. I really want to put in serious work, but then go home.
I'm glad you posted this as it goes against the "hard work cult" that seems to have gripped popular imagination. Hard work isn't just time spent on completing a task; this interpretation is maybe the easiest to understand and benefits employers the most.
If there's anyone I'll listen respectfully to about the value of hard, diligent work, it's Terence Tao.
Reminds me of Richard Hamming talking about his professional envy of John Tukey:
One day about three or four years after I joined, I discovered that John Tukey was slightly younger than I was. John was a genius and I clearly was not. Well I went storming into Bode's office and said, ``How can anybody my age know as much as John Tukey does?'' He leaned back in his chair, put his hands behind his head, grinned slightly, and said, ``You would be surprised Hamming, how much you would know if you worked as hard as he did that many years.'' I simply slunk out of the office!
TIL Bode, Hamming, Shannon, Tukey, et. al all worked at Bell Labs around the same time. Wonder what the culture must've been like, those are all household names in signal processing, control, information theory.
Richard Hamming wrote a book, "The Art of Doing Science and Engineering", which - despite its name - is more or less a memoir of his own scientific career. It's a fun read if you're interested in that culture.
From the preface, "After many years of pressure and encouragement from friends, I decided to write up the graduate course in engineering I teach at the U.S.Naval Postgraduate School in Monterey, California. ...In this series of lectures I try to communicate to students what cannot be said in words—the essence of style in science and engineering. ...I have found that the personal story is far, far more effective than the impersonal one; hence there is necessarily an aura of “bragging” in the book that is unavoidable."
You can watch him giving that 31-lecture course in 1995 here
Enjoy! It's wonderful. (The last lecture is the famous "You and Your Research" that he gave many times.)
I've really enjoyed his books too, from Numerical Methods for Scientists and Engineers to Methods of Mathematics Applied to Calculus, Probability, and Statistics. They're all drenched with experience.
He wrote eloquently about one of his failures in grad school iirc because he simply didn’t work enough nor seriously enough. Even though he is a genius there is quite a lot of work required.
Off-topic, but why is it that Terry Tao's blog attracts such low-quality comments? When I look at SSC/ACX, Shtetl-Optimized, Marginal Revolution, etc. the comments are mostly constructive, engaged, and well-informed. With Tao, it's a huge proportion of random people asking for generic life advice, or fanboy-ism.
This seems counter-intuitive, because Tao's blog is by far the least accessible of those above 3 blogs on a technical level. There's almost no reason to visit Tao's blog if you don't have a graduate maths degree.
This is true, his video on gaps between prime numbers had over 2 million views. People find his genius fascinating even if they don't understand his work.
All blogs attract low-quality comments. Whether you see them is a function of how much effort is put into moderation. I'm just speculating, but Terry Tao probably has better things to do with his time.
Tao has gotten a lot more public media attention for the most part (Netflix, shows, TV, news, etc.) than any of the others which remain more niche. I'd guess as a result the audiences of the others are better selected to lean more high quality.
Also there's plenty of shows and news about MU, SSC etc. I'm also surprised that Tao's rather specifically niche blog attracts such comments. Is it possible that the other blogs are just better moderated and Professor Tao doesn't need or care to?
large foreign readership , so English is not a primary language. probably also a lot of spam comments that get through.
Those other sides also tend to have a fair share of low quality comments as well. A lot of troll bait or off topic stuff. I just don't read the comments, often I find that I am not missing out on much by not doing so.
I'd second what the other poster said - your best bet are recommendations of blogs you like already.
Looking at my RSS feed, I'd also endorse Andrew Gelman's blog (applied stats), A Collection of Unmitigated Pedantry (history), and Applied Divinity Studies (rationalism à la ACX).
It's probably good advice, and maybe my dissent is just due to my burn out, but...
I'm tired of hearing "work hard". Very often, working hard does not lead to success. It sure as shit didn't work out that way for me. There are many people who do not work hard and make tons of money in things like NFT, crypto, securities, office politics, scams, etc. It seems like luck is the shared variable... of which I have none.
> If you wake up in the morning full of vim and vigor, bounding out the door and into the world to take your shot, you didn't choose to be that way
Your coworkers that come into work early ready to crush through the workload in anticipation, and when the day is over, can't find the will to stop working, because frankly there is nothing outside their work that they are more passionate and excited about so they keep working. Well they are not finding it hard to do so, it's the opposite in fact, they'll find it hard to not work and do other things.
In your case, I think the conclusion is important as well:
> What if you've been unlucky in life? There should be consolation in the fact that studies show that what is important in the long run is not success so much as living a meaningful life. And that is the result of having family and friends, setting long-range goals, meeting challenges with courage and conviction, and being true to yourself.
Success is overated, and I've known people where success actually hid a deeper loss of enjoying life without self-judgement and constant comparison to others.
> And that is the result of having family and friends, setting long-range goals, meeting challenges with courage and conviction, and being true to yourself.
You need luck to not have broken families and friends. Sustaining a family is so fragile these days.
The way I look at it, luck is a very important variable, but it's one outside your control almost by definition, so it's not worth writing about how to change it.
So if you can't load the dice what can you do to get those high rolls? Well, maybe you can roll the dice more often (try more avenues, work harder), maybe the dice aren't all equal and you can observe many dice and pick the ones that happen to be paying out higher than you would expect if they were truly fair (market research), or something else.. I think people write about all those things not to claim that the dice rolls don't matter but because there are things that are both controllable and matter.
I agree with the burnout though, it can be hard to keep playing when you feel like a high roll is "due" but can't get one. I feel like some part of this is how we are wired, to solve the multi-armed bandit problems that life present us.
But what do I know, my rolls haven't been very high. I wish you luck in beating the burnout.
I have come to the conclusion that working hard is basically rolling the dice. You can roll your dice in a single game or change games or even multiple games simultaneously.
The thing is it is impossible to know if will be lucky or not. So the only way to know the truth is to roll the dice.
He also mentions setting realistic expectations. So, not "work hard to get rich" or "work hard to have a breakthrough scientific finding" (as there's too much involved there) but perhaps "work hard to be appreciated enough to make very good money" or "work hard so that I can make an non-trivial addition to my field of study" etc.
Also, if you're not really motivated by anything working hard can get you, then there's no point in hard work. Most people hate hard work and it's not worth it for them, hence they coast doing the minimum that doesn't get them fired. It's a perfectly valid life strategy, although the American religion of workoholism treats it as heresy (while millions of people practice it, feeling unnecessary guilt doing it).
I would love hard work if it actually resulted in something. I'm not making very good money. I'm not making meaningful contributions to my field. I'm not even in a position to do either. The problem is, hard work is rarely rewarded beyond some words. If it's not rewarded and I'm not in a position to make an impact, then there's no point.
Have you ever considered that in the worst case scenario you could move to Colombia or South Africa or Thailand and have an immediate boost in your social relevancy?
His advice isn’t for how to get rich in crypto, it’s for how to succeed in academic mathematics. I can’t imagine that anyone has ever “lucked” their way into that.
- Your genetics
- Your intrinsic abilities
- Your intrinsic tastes
- Your parents
- The teachers you had
- The time you were born in
- The environment you were born in
- Etc.
So for example for mathematics you'd assume you need some predisposed genetics, you need some good education towards it, access to books and material, you need to be someone who loves doing math, you need to be in a position to have the time to dedicate to math (so access to food, shelter, etc.)
Since all these things are out of your control, the question becomes, what if you bad lucked in all of them, can you still, through sheer hard work, make a valuable contributions to the field of mathematics (and not by luck of hitting your head, or stumbling randomly on a key fact), but simply from your constant effort towards it?
But I'd say I think the author presupposes you've been mostly lucky already, and is talking about how to go beyond that luck, and achieve even more gains with what you do have control over.
Well if you take that all as “luck” then certainly your predisposition to hard work is also “luck,” at which point you’ve denied free will, which might actually be true but isn’t very actionable.
What if looking for actionable things related to working harder is a useless waste of time?
It might be better then to look into medical, genetic and environmental aspects, and focus on that instead of trying to find tricks to work harder.
For example, trying to change your environment might help more than busting your a$$. Can you move to a place with better access to education, books, or people with expertise? Can you find places that support some of your needs that enable you to focus on taking a course or other? Can you find programs that can fast track you into a new discipline that's paid for? Etc.
Another example is that if genetics plays a big role, than working hard is counterproductive, instead you'd want to find something that plays to your genetic, whatever that is. Find something that is easy to you, and focus on doing that. Don't waste time trying something you find really hard that you don't have the genetics for.
Now the medical aspects I would say is more in terms of where we invest, instead of paying for self-help pseudo science books and talks. Should we invest in ways to medically address deficiencies in motivation, intelligence, judgement, perception, sleep, etc. This might be a long shot, but I think better understanding the role of genetic, the brain, and all that with regards to accomplishment will help us find actual mechanism that might really work, unlike "hard work".
Personally, I tell people to focus on "easy work". Forget hard work, your goal is to make it so the work you do is as easy as possible. You can achieve that by finding something you have a natural aptitude for, or for which you have the right environment to succeed at. Focus on choosing the right people and place to surround yourself in for whatever the work is you are trying to do. Focus on something that motivates you, and feeds into your reward mechanisms.
Finally, don't consider yourself a failure if you fail, because if you think hard work has nothing to do with it, its just bad luck, so don't be too hard on yourself ;)
All what you describe requires the precursor of you throwing the dice to see what happens.
>You can achieve that by finding something you have a natural aptitude for, or for which you have the right environment to succeed at.
Again to explore this requires you to throw the dice and you will stumble upon it. Also aptitudes change with time and to explore the next aptitude requires you to throw the dice. You should also be lucky that you will get to throw the dice.
Yes, luck plays a big part of it, so it's important to redefine your perspective so you don't value dominance over others or class or such things, because that can be a lost cause. You were given a hand of card at random, and while there is some wiggle room in terms of how far you can make it given the cards you were given, a bad hand is still a bad hand, and can only let you do so much.
Focus on your personal growth, but understand your circumstances and where you start from, and recognize how much you managed to optimize and accomplish relative to that.
And in my opinion, there's no place for hard work within this framework. The feeling of hardship is your body telling you your circumstances ain't cut out for this thing. You also have the ability to reason, so you can reason that some hard things are worth pushing through the pain, like say for a life saving surgery. But sometimes I think people reason that they will be able to push through something, yet fail consistently to be motivated to do so. That's when you need to realize, hold on, ok, this ain't gonna work for me, I need to find something else that's easier. And no, the people who made it where you failed didn't do so because they just pushed through that same hardship, generally it just wasn't as hard for them to find the motivation to push through.
>a bad hand is still a bad hand, and can only let you do so much.
Very true. I had realized this during and after graduation some 15 years back. Exposed to the internet I saw people doing amazing things on open source and wanted to do the same but simply didn't have the infrastructure in my country to do it. I spent all my life struggling to be the best but my environment simply isn't conducive enough to recognize my effort. Now I think it was just a waste of time and I should have just lived and enjoyed the moment. There was also a talk by Linus Torvalds who said he is incredibly lucky to get to do what he is doing which really started the questioning process as I was always told to put hardwork when I was young and achieve things discounting the support for it.
>And no, the people who made it where you failed didn't do so because they just pushed through that same hardship, generally it just wasn't as hard for them to find the motivation to push through.
This sentence makes a lot of sense. Thanks! I have been exposed to a lot of wrong signals saying "I have done the hard work to achieve it and you should be doing it too or you are just lazy" without them not acknowledging the circumstances.
Picking the right problems to work on is also necessary, and difficult to get right. Worming in on a hard unsolved problem that is eventually incredibly important is the scientific equivalent of winning the lottery, and we know lots of examples of this. Recently, mRNA vaccines, neural networks, and the twin primes conjecture come to mind. But there are doubtless many, many other examples of people working on a possibly-fundamental problem which never actually break through, and we never hear about it.
But I would argue it's still worth making a concerted effort to identify good problems to solve, and specifically thinking about what makes a good 'hard problem.' It's much easier to make progress in an under-studied area, simply because the low hanging fruit haven't been eaten yet. The danger, of course, is that understudied things may be understudied for a reason: they're not actually relevant to anything else, or there's some secret impediment and many others have already failed.
By contrast, cracking away at ridiculous subproblems from the last generation of academics is almost always a dead end, imo; you're competing with people who already know the field extremely well, the low hanging fruit has been picked, and the obvious roads to relevance have probably already been well-explored. Unsolved problems in a long-standing discipline are often unsolved because the right tools are missing or it's impossible within the existing paradigm... Or the problem is just irrelevant, relative to the amount of effort needed to solve it.
It's not luck alone. You can still work hard in math and fail. Didn't get the grant you needed - tough luck. Want tenure? Better be ready to play politics. Etc
Working hard for money, or even recognition, doesn’t always end well. The generalization of what he said from my perspective is that one should work hard to better themselves and do things they want to do, well.
It can be math, biology, coding, music, woodworking, anything. If you’re convinced that you’re quite good at what you’re doing and you only work 9-5 on your skills and projects, then it means you’re either developing crud apps, or you’re ignorant of what you actually don’t know. Again both are perfectly fine if that’s all you want from your career or hobby, but if it comes to questioning working hard in a generalized sense at the least you should preface it with your choices in this regard.
I don't really know if I believe in hard work. I feel more inclined to see things from the motivation school of thought. When you're motivated, all work is easy. The "hard" feeling comes from pushing through doing something you are not motivated to do.
And the thing is, I don't know if anyone is successful at that. I feel most success comes from people who had the motivation for it. Can you force yourself or others through work that they're not motivated to do and actually expect it to deliver on breakthroughs?
I'm fairly confident that when the article says "hard work", it just means "a lot of work". The article later mentions that more motivation will help you work harder.
The point is that motivated or not, high quality output requires a lot of work. Working a lot on a particular thing is still going to be easier for some and harder for others.
Ya, I agree with you 100%. But I think this is the problem with calling it "hard work". If working a lot on thing X is something I don't struggle with, and in fact I enjoy and find fun, and am really motivated to do, than it's actually pretty easy for me to put in a lot of time and effort into it. Isn't it weird then that I'd go and tell others I'm a "hard worker"?
I just find it a bit deceiving. Like people can hear that and think, damn, this person is able to work through something they hate doing, have no motivation to work on, and where there are other things they'd rather do, yet somehow they can power through using raw will and focus on putting tons of time and effort into it? Well damn, I must be a weak minded person then.
Personally, I think that second interpretation is common, and it does more harm than good in my opinion. Every time I have put a lot of time and effort into something, I either really enjoyed the thing, or I was really motivated by the outcome. In both cases, that made it pretty easy for me to put in a lot of work.
I actually believe the complete opposite. People who rely on motivation to get them through to the finish line in long term situations probably never make it there. Motivation is a very fleeting feeling unless you find something that utterly sets your soul on fire, and I would almost say it is a crutch for many. Sometimes you're going to get up in the morning and you're just going to have to push through. And there will almost always be small/medium/large pieces of work that are simply not fun(and you can't always delegate). The people who succeed will be the ones that have developed a mindset of resilience and just doing what needs to get done.
Might depend what you mean by motivation. I'm using it to mean both your enjoyment of the work and your desire for its outcome. So I see it as a function of that. Having more of one could offset the lack of the other, but ideally you'd have plenty of both.
If you really like doing something, you'll get good at it, and some stuff might not involve other work you might not like. For example, there's a game I really like playing, I'm quite good at it, I don't care for any outcome, just like doing the work, so putting in time and effort to get good was pretty easy.
Other things, I really want the outcome, I'll go out of my way, do things I don't really like doing, because I'm motivated by the result, still feels easy because of that.
Now, okay, sometimes there's some things you really hate doing, but it's needed for something you want. I think those are the tricky one, because you need to remind yourself of your goal, how much you want it, and all that, but what you're doing there is motivating yourself. So ya, in my view, motivation is key.
That’s exactly what Terry advices against. Not because you owe the company or anyone else that, but it’s possible you might regret not doing so yourself. My advisor described it as “being too smart for your own good.”
It's also a lot easier to work hard when you are handed access to every academic resource on the planet before you hit puberty. His life story is the most blatant counterexample to this article imaginable. Sounds like a case of deep denial.
No ones saying anyone here has had the privilege of being born with a mind comparable to Terry’s, but a charitable (at the least) reading of his thoughts would be about working hard to better yourself, wherever you are today. If you’re just a programmer writing good code, you can work hard (not necessarily for your boss) to get better at it. Or not. Your choice. But given the day and age we live in you cannot keep insisting about the lack of opportunity if all you’re talking about is getting better yourself.
I don't really think you or Terry knows what hard work even looks like. We hold this conversation about personal advancement from positions of extreme privilege while billions live without running water. If you want to limit your view to only those of us with access to all the delights of modern society (and none of its externalities) I'm sure you can find plenty of evidence for the meritocracy.
You can personally thank my grandparents, all four laying dead in their graves before the age of 60, for your opportunity to "work hard" in America.
I've got a friend who is in industrial maintenance. I just can't understand how they put up with the working conditions. 12 hour shifts working around furnaces and covered in grease all day, forced overtime on a regular basis. This guy works harder than I ever have and makes a fraction of the income that I do. He has been injured multiple times at jobs. He's in his early 30's and has a more difficult time walking than many senior citizens due to a back injury. To your point he's still better off than many folks in similar situations in less developed nations. There's a lot of detail left out of the "work hard" narrative.
Maybe an article he wrote called A Close Call: How a
Near Failure Propelled Me to Succeed [1] might be of interest to you.
"After many nerve-wracking minutes of closed-door de-
liberation, the examiners did decide to (barely) pass me;
however, my advisor gently explained his disappointment
at my performance, and how I needed to do better in the
future. I was still largely in a state of shock—this was the
first time I had performed poorly on an exam that I was
genuinely interested in performing well in."
"In retrospect, nearly failing the generals
was probably the best thing that could have happened to
me at the time."
Is this supposed to be a tale of overcoming adversity, almost failing some exam? The stakes are so low I can barely identify the conflict in the story. Actually failing something of actual importance and then overcoming the odds to succeed anyway would be a little less boring.
He sounds like he's lived his entire life in a university basement and mistook the petty challenges of academia for real life.
The original poster made a comment about grinding to get a math PhD. You said Terrence Tao is a blatant counter example to that. I posted (I'll concede that I probably didn't display great quotes from the article or provide enough context) an article about Terrence Tao almost failing his PhD generals exam, which I thought would lend some evidence to the idea of grinding for the PhD, which is the original point under discussion. Since he passed the generals and he didn't prepare very well for it, may be you're right and that is weak evidence. I think the article does provide some evidence that others who were studying for their PhD in math at Princeton while Terrence Tao was studying for his were not relying solely on intelligence alone. Perhaps I'm wrong on that point too.
However, I don't think you're trying to criticize the article as bad evidence in relation to achieving a math PhD. You're going on about academia having low stakes and academia not representing real life. If I'm mis-characterizing this, then I apologize. I do believe you're moving the goal posts in this discussion. The original article posted is about math graduate school. That's all. It's not about real life. The first two sentences in the article establish this point.
> Relying on intelligence alone to pull things off at the last minute may work for a while, but, generally speaking, at the graduate level or higher it doesn’t.
> One needs to do a serious amount of reading and writing, and not just thinking, in order to get anywhere serious in mathematics;
Reading alone would take some serious hard work.
To make any meaningful contribution in any field you have to do some serious reading (and understanding) to bring yourself up to date with the field.
I've held for a long time that you must know the rules quite well before you're "allowed" to break them, and I think this reinforces my opinion on that.
Additionally, I think the obsession over "intelligence" and "natural ability" is vastly overstated, in general. It absolutely helps, and it compounds, to be smart, but a person who "works hard" is infinitely more valuable to their colleagues than a smart person who doesn't, and tries to rely on raw intellect.
My problem, and I wonder if others have this issue as well, is how hard it is to know these things intellectually, and also apply them to my life. I just cannot, for the life of me, maintain a "work hard" mindset. I'm still trying, but I very often fail at this, and its frustrating because I know how valuable it is to being good at what I do.
It's kind of a double edged sword- I've worked with a few people that "work hard" and "get things done", only to find out once they leave (or go on vacation) that now we have to untangle a 600 line bash script that's integral to production.
I'm being a bit hyperbolic here, but the gist of my point is: not everyone who works hard is worth keeping around, especially if their hard work leads to an un-managable mess in the future.
I used to think like this too, but now-a-days, it's more like "What a luxury to be in a position where you get paid to untangle a 600 line bash script"
That is, usually these few hard workers are typically the ones responsible for getting a company to profitability precisely because of their GSD attitude. Now that the company has some runway, the architecture and refactoring can proceed.
I never felt luxury when our service didn’t scale to meet the goals of higher-ups because the code was over engineered with hacks piled on top. It doesn’t matter how good of an MVP you built if it is so inflexible that it has to be thrown away and rebuilt to meet tomorrow’s needs.
Managers tend to reward those who complete tasks today as minimally as possible at the expense of the product tomorrow.
I think scrappy MVPs have their place,it's just knowing when to use one. If you're a very early stage start-up and you're trying to validate your idea, the quicker you can see if that idea is valuable is better than risking time building a clean code architecture.
I can assure you, when shit is broken in production and customers are knocking at the door threatening to cancel it is not a luxury to find out these types of things...let alone start untangling the web.
And window repair customers wouldn't exist if it weren't for broken windows! If Bastiat were alive, he'd have a field day with the computing industry and its Freakanomics-like underpinnings.
Anything is possible. Better to focus on what is likely. Did you stop using google over any of their outages? Most people didn't. These things matter, but people in software overstate them.
Software for automatic trading, dosing radiotherapy, controller for moonshot etc will have different requirements on correctness than ordering of search results.
Ignoring these things can have people killed/ruined and they have.
There is no shortage of software jobs. There are plenty of opportunities to work with a relatively clean codebase, capable and experiences colleagues, unencumbered by the VC runway bullshit.
Every company begins somewhere. If you want new companies to make it, allowing for there to continue to be 'plenty of opportunities' in the future, then accepting that there are times when repairing the ~sins~ necessities of the past is reasonable.
600 line bash scripts are not always necessary for new companies to make it. Sometimes, sure. Often, even, on the way to understand what is actually needed.
Many new companies spend too much time perfecting the wrong thing.
But messy code is NOT a requirement to make it.
Messy code, in and of itself, does not help.
Messy code might be a sort of inevitable step on the path to product/market fit. However, it is most certainly not a goal, and dealing with messy code is not a luxury. It is more likely a sign that the early tech people weren't very good.
Yeah, this is probably a different kind of "hard work" than what the author is talking about. There's some people who work hard for the sake of results (hitting certain numbers, clearing tickets/stories, etc).
There's a different sort of hard work involved in achieving deep mastery over something. Reading, researching, building and testing ideas... it takes hard work to become an expert at something, but I guess you're far more likely to see the former type of hard work than this.
Why not rotate their assignments as a matter of policy. They might do a deep dive and fix something no one bothers to fix on a similar assignment. But then it is due dilligence to have another look at their work. I know this sounds theoretical compared to practice, but it seems to be on the level of separating conceptual or design breakthoughs from production-izing code.
How is that hyperbolic? 600 lines is pretty short for a (longest-involved-in-this-project) un-managable mess of a production-critical bash script. I've seen several well upwards of 6000 lines.
The obvious question is why this wasn’t caught and rectified in code review? This seems to be as much a failure due to lack of oversight as opposed to the failure of the person who created the mess.
There are no code reviews when we have to keep churning features quickly and continuously, with always changing requirements in the next meeting with the client.
I've been learning to draw lately. It's amazing how much of what we presume to be natural ability is "just" the product of endless work. During my day job, I do math and it's the same. People say "I'm not a math person," but that's as stupid as "I can't draw." It's self fulfilling.
Personally, I prefer "work diligently" over "work hard" because the most useful mental model for me is that it's a marathon, not a sprint. The idea is to go far, not fast.
Additionally, I think the obsession over "intelligence" and "natural ability" is vastly overstated, in general. It absolutely helps, and it compounds, to be smart, but a person who "works hard" is infinitely more valuable to their colleagues than a smart person who doesn't, and tries to rely on raw intellect.
That may be true for something like digging a ditch, but IQ is needed to make those necessary logical leaps for more abstract matters. Only hard work is like adding 1+2+3....n. Having a high IQ is knowing the shortcut to sum it instantly.
So, so little of most people’s work is deep abstract thought like that. I used to have this research assistant - she was from an entirely unrelated arts major, and was a bit… well, let’s say not terribly book-smart (which she was very upfront about). We ended up with her due to some last minute issues with other candidates. But holy smokes could she ever focus. She could sit down for hours and hours and process way more material (reviewing data, publications, participant communications) than anybody else because she didn’t get sidetracked. What she didn’t know she knew to ask and get clarification on. She would work circles around many “smarter” RAs because of her amazing work ethic. And this isn’t digging ditches, this is honest-to-goodness academic research.
Outlier strengths in one area can make up for weaknesses in others. She had extreme focus, which pushed her past where her intelligence would normally go. Imagine if she had great focus and great intelligence.
They're related, but you can isolate them. Raising stakes and immediacy will bring up focus more than intelligence. (but it also might bring up anxiety!)
The whole point of the submission is that even when high IQ is required, you also need to "work hard" to do anything substantial.
The common thread is "work hard", not "be smart", but people obsess over intelligence/natural gifts, and consistently underestimate the "ditch diggers".
Jobs was a ditch digger.
Gates was a ditch digger.
Musk is a ditch digger.
PG is a ditch digger.
Tao is a ditch digger.
Jordan was a ditch digger.
Woods was a ditch digger.
Carlsen is a ditch digger.
Some (all) of them also are naturally gifted, but their success is due to their ability to "work hard", or at least that's what I've read them say over and over again. Maybe I and they are all wrong about it, I'm open to that possibility, but theres a consistent theme that every successful person I can think of repeats when asked, and it's some variation on "work hard".
That is not a problem. The problem I see is touting the value of hard work to people who may not have the requisite IQ to go along with it for their desired outcome (Best in the world in their field, for example).
You said, Additionally, I think the obsession over "intelligence" and "natural ability" is vastly overstated, in general".
I think it's actually understated in general. Telling people who don't have the mental horse power to, "work harder", is cruel.
Would you tell someone with an IQ of 100 to "work harder" if they wanted to be a Software Engineer/Lawyer/etc?
While I agree there is a certain threshold of skills below which one can't really function as a lawyer/software dev, after passing that threshold your IQ matters less.
There is the top 1% or even 0.01% of performers out there and then there is the rest of us. The difference between a software dev with an IQ of 115 or 125 doesn't sound that big to me. A lot in their careers will depend on their people skills and work ethics more so than on their IQ.
This is especially true for jobs like lawyers or even doctors, but if we go back to software development - a lot of it is quite repititive and actually favors well people with strong work ethic. Unless you work on cutting edge algorithmic computer science stuff (which isn't really software development), we all keep building classes and models and glueing libraries together; or we gain some deep knowledge in some mobile platform or even some embedded programming. Even stuff that sounds super complex to a web developer like Kernel development probably gets repititive after awhile.
Wow, I expected broken money systems to twist people's minds but not to this extent.
Of course, in a broken money and work system there is a cutoff point for IQ at which corporations decide who to hire.
The inverse position is that money isn't wealth. It's work and the product of our work that is wealth. Therefore willingness to work should be proportionally rewarded with work. Of course, since corporations hire whole individuals no such thing happens. Instead, work that could have been allocated to two people fairly is allocated to one person.
Now employers have to think of hard to cheat measures to determine the person who the work will be allocated to. The IQ cutoff point is the result. The chosen one then gets to feel superior because he both has the intellectual, moral and financial upper hand while he simultaneously gets to chastise the lazy, stupid, poor hobo. It is so easy to rebrand this process as "personal responsibility".
This is not really what I meant or how I view this, though I completely agree with this:
> The chosen one then gets to feel superior because he both has the intellectual, moral and financial upper hand while he simultaneously gets to chastise the lazy, stupid, poor hobo. It is so easy to rebrand this process as "personal responsibility".
Regardless of whether companies have their own cutoff point, competition amongst people will create a natural cutoff point.
If there are a limited number of jobs, people will have to compete for those jobs. Sought after jobs will attract more people and have fiercer competition. More intelligent people will generally outcompete less intelligent people for these jobs, and so a natural IQ cutoff will form.
There is no requisite IQ, and I absolutely would tell someone with a definitionally average 100 IQ to "work hard" to become a software engineer/lawyer, as they could be in the absolute top of their field if they did.
There's probably a limit to how much "work hard" can make someone competent/successful in any field, and it'd guess it's around 85, or 1 standard deviation lower than average.
If IQ is important to you, I think you'd be quite alarmed by the number of successful doctors and lawyers who don't meet the 100 IQ bar you're setting here.
Sources + people's estimates place the average IQ of a doctor well above 100.
You seem very out of touch if you think that there's a large proportion of doctors and lawyers who have an IQ below 100.
IQ isn't important to me, it's just reality. The difference between 100 IQ and 120 IQ (For instance) is palpable and you can't overcome that with hard work.
There is no universal ranking of doctors, you can't really claim "percentile of success" for doctors or lawyers, and it's weird you're trying to do so.
Why is it so important to you that you have to be "smart" to be a doctor/lawyer?
You said: "I think you'd be quite alarmed by the number of successful doctors and lawyers who don't meet the 100 IQ bar you're setting here".
The number of doctors and lawyers who do not meet that bar appears to be slim to none, so I'm not at all alarmed...
> There is no universal ranking of doctors, you can't really claim "percentile of success" for doctors or lawyers, and it's weird you're trying to do so
I'm not claiming percentiles of success, it's IQ percentiles across all doctors and lawyers.
Regardless of how you define success, a very small proportion of doctors and lawyers don't meet the 100 IQ bar. And if you define success as anything other than having the job, that proportion gets smaller.
There are way more than "slim to none" doctors/lawyers who are at or below 100 IQ.
Your citation is not accepted (it's from nearly 30 years ago, is a sample of men over 30 in Wisconsin, cites research from many years even older [50s and 60s], there's no accounting for correlation -- maybe doing harder work makes you better at taking IQ tests).
It's only doctors, who happened to be the folks who ran the study, that are substantially higher than every other group listed. I wonder why.
IQ is a predictor of success, but it is not an exclusive predictor. Unless you have a mental disability, you can be literally anything you want to be, and even if you have a mental disability, you can still be nearly anything you want to be.
Hard work is astronomically more important than IQ. The literal article you're commenting on is written by someone with one of the highest IQs in the world.
You're in disagreement with all these "high IQ" people you think are worthy of studying other humans, and given the option, I'm going to listen to them over you.
That’s absurd. Discoveries are rarely made by lone scientists, progress is made by tens or hundreds of people, each exploiting their comparable advantage, even if that is digging ditches.
Having high IQ is not knowing the shortcuts but being able to identify them.
Fact of the matter is that we make progress when collective effort is put onto something. Not everyone of us is a Terry Tao, or John von Neumann, but we can at least exploit our comparable advantage and help those better than us. Sucking your ego sucks but coming to terms with our inherent limits is freeing.
Knowing a preemptive shortcut is also "working hard".
1) Knowing when to apply previous experience is a skill that requires work and practice.
2) Someone else knowing a shortcut that I don't know means they worked hard when I was not observing them.
i doubt it. he was winning math competitions at a young age. I doubt he knew all the shortcuts in advance but just intuited them. He was probably smart enough to be given a hard problem and upon pondering for a minutes figure out the shortcut.
It really depends on what you define as natural abilities. The ability to work hard for 12 hours without break every day IMHO is as "natural" as having a good IQ.
> I've held for a long time that you must know the rules quite well before you're "allowed" to break them, and I think this reinforces my opinion on that.
I had an art teacher that pointed this out about Picasso. He got famous for his Cubist/Abstract work, but he was actually an excellent realist.
I saw this in university. You passed the physics exam by studying hard and practicing. People who put in the work got the results. There was no just getting it.
On a related note, this always trickles down to low level managers who then proceed to tell it to the floor workers.
Trying to motivate a cleaner, assembly operative, driver, cashier, warehouse operative, packer and other low level workers with it is like telling them to go fuck themselves.
It sounds like bullshit. It is bullshit. No one fucking loves these jobs. There's nothing to aspire to. Working hard means just killing yourself faster (but not fast enough).
I thought I was the only one that got offended by that kind of thing, it's ridiculous. How have these people convinced themselves that they're actually better.
To be honest, I don't see it as that different as a developer. None of my work makes the world a better place, and I work on products most people would see as essential and important. I want to be vague, but it's not like we make useless junk. The people pushing this garbage will be the ones seeing the benefits, I'll get a pat on the back if I'm lucking (and maybe like 1-3gs which will go right in my 401k)
Realistically, at mid-to-senior level, I've already seen all the significant changes to class that I will likely see. Hard work isn't even the main way to get ahead in the corporate world. Politics and social BS will have way more sway, and besides that, you just have to ensure that you don't have a reputation for incompetence (however exceptionalism is optional). Your mileage may vary, but in any case, hard work only gets you so far.
While I might be able to squeeze out an extra 10 or 20 grand here and there, salaries don't really go down, and it's not likely for that incremental improvement to have much of an effect. You know what will effect me though? Sacrificing the little personal time I do have.
It will only make me crazier and less healthy, by causing me to skip self-care and socialization. Something has to give, and I will not be seeing my friends, skip working out and cooking, or my house will be a disaster. I've done the math and 40 hours plus cooking/cleaning/exercise, basically yields 0 free hours, and whatever remains has to be use to relax or hang with friends.
It's just a bigger middle finger to the kind of low paying jobs you're talking about, because at least in engineering, you get a bigger payout for that sacrifice, and a chance of advancement. That's no small thing, and I'm not trying to say things are exactly the same, but it's not so different.
> Trying to motivate a cleaner, assembly operative, driver, cashier, warehouse operative, packer and other low level workers with it is like telling them to go fuck themselves.
This reads as true given how most jobs are currently organized/implemented. I don't think it has to be true though.
I used to work bagging groceries and pushing carts for a supermarket. I loved it. I worked quite hard and was recognized by customers for doing so. I personally enjoyed being able to help someone through great service.
Many of these jobs are naturally game-like (checkout the day before Thanksgiving = time trial). They are critical _essential_ positions.
These people probably don't love their jobs because they aren't treated as well as they should be. Realistically, bagging groceries is ~80-120% as hard as writing software (in terms of perceived effort); the software engineer shouldn't be making 5-20x more.
Making it clear that people are actually valued, by actually valuing them, makes a huge difference. Sadly, there are generations of MBAs who are allergic to the concept.
He is very specifically referring to putting in the work to achieve breakthroughs in graduate-level and higher mathematics here. No one in the that field is driving factory workers to actually produce the proof breakthroughs for them.
I used to work at a company where the janitor, by working hard, and being willing to step up to opportunities he was offered, became a shift supervisor. Not every company is like that, true, maybe almost none are, but it can happen. Reminds me of the concept "return on luck" to go along with "return on investment".
I can certainly understand how one can derive meaning from a trade or profession, but I would find it difficult to believe that anyone could really do that for menial jobs like a cashier or warehouse packer. These jobs are dead ends, they don't have a meaningful spectrum of quality and you're little more than a warm body.
A comedian (David Mitchell) once joked that he's proud of the UK's terrible service reputation. It doesn't seem honest or appropriate for service staff to be so happy and enthusiastic, why would they be? There's very little to be happy about.
> A comedian (David Mitchell) once joked that he's proud of the UK's terrible service reputation. It doesn't seem honest or appropriate for service staff to be so happy and enthusiastic, why would they be? There's very little to be happy about.
I remember watching this episode on TV but I haven't the faintest idea what the show was called... though it was incredibly funny
The only way to make those jobs manageable is to create some sense of meaning and mastery out of them. You're always striving to do a little bit better job. You remind yourself of the importance of what you're doing. If you have a good manager, they're trying to find ways to give you autonomy in what you're doing.
>"It is also important to direct your effort in a fruitful direction rather than a fruitless one"
This is actually the most critical sentence in the entire article.
I read an article somewhere, maybe 25 or 30 years ago, that was about this exact topic.
Some successful scientist, I don't even remember his name now, was asked about his success.
He said that others worked just as hard and diligently. But his skill was in selecting the projects that had a high degree of probability of success. He would watch others in his profession and see how they made horrible choices in the selection of their work. The unsuccessful people made a series of unwise choices. Tilting at windmills that had exceptionally poor chance of success, areas where there was no funding available or very difficult to get funding, and all sorts of other problems.
The same thing is true with everything. For example, lots of people start businesses that are shitty selection right off the bat - they have almost zero chance of success before they even begin. All teh perfect execution and hard work will be for naught. The founder has blinders on.
You always hear about the successes. People always say false things like, the idea is 1%, execution is 99% of it. Not true. It's more like, the idea is worth 99%, and the execution is the other 99% of success. Trust me, I've seen a LOT of great execution on shit ideas and the company goes down the drain. You just never hear of them. And by the way, this is in regards to ideas that are actually have a corporation started around them, as opposed to just aimlessly talking about ideas.
Anyways, take what you will from what I just wrote.
This holds up really well, in any STEM field, not just mathematics. Celebrate those dimples on the surface of human knowledge, if you can, in fact, even make them. Very few people can, and our future depends on them.
It's interesting to see what qualified as worthy of a blog post not so long ago.
It takes time and effort to do difficult tasks? You shouldn't overwork?
What new insights, let me blog about it :)
For those who don't know, the 8 hour work days and holidays were talked about by Adam Smith more than 200 years ago. The reason that system was put in place was because letting people work as much as they wanted led to over-exertion and injuries, lowering productivity.
That was for physical labor by the way. In another 200 years, I expect people to finally realize that thinking is harder than repetitive physical labor and one can't do more than a few hours of it, per day.
Until then we'll have 'burn out' blog posts and people reading and posting on HackerNews/reddit/twitter during work hours.
Worth highlighting, for those of you that are skipping through.