5 ms·
o-f'r-cryinoutloud. I can't believe everyone's actually discussing this as though it were insightful. Look, you're sitting at home, you're a student, and you
by thaumaturgy 15y ago
o-f'r-cryinoutloud.
I can't believe everyone's actually discussing this as though it were insightful.
Look, you're sitting at home, you're a student, and you have, let's say, three things you can choose to do right now:
1. You can study for your class tomorrow, working towards a degree. Effort required: high. Reward: far future.
2. You can go out with friends. Effort required: medium to low. Reward: near future.
3. You can play a video game. Effort required: low. Reward: immediate.
So which one do you really want to do?
Before you answer that, let's add one more little piece to our hypothetical: let's imagine that you have all the time in the world. You're immortal. There is absolutely no rush to get your degree. Whether you do it this year or in thirty years will make absolutely no difference.
So which one do you do?
This is procrastination. I should know. I'm an expert procrastinator. There are about eleventy-seven things I should be doing right now -- and they are all things which require a lot of effort right now, and won't pay off today. What am I doing instead? I'm wasting time on HN: low effort, immediate reward. If I couldn't be on HN, I'd probably be in my garden. Again: low effort, quick reward.
This guy's a book author. He wants to sell more books. He probably wants to make a little extra money doing speaking engagements. So he has to set himself up as an expert, and to do that, he's put together this notion about "ancient brains" and evolutionary psychology (which is mostly bunkem) and the "wasting" of energy.
And it sounds sort of OK, except that it skirts around the basic notion that we're largely reward driven, and all of these distractions that we have today are really good at pushing our little reward button, and we'll keep triggering our reward button for as long as we can -- until we become that little mouse that starved itself to death pushing its feel-good button.
Short-circuiting this requires two forms of self discipline: one, you have to tear yourself away from pushing the reward button occasionally (and no amount of telling yourself why you're trying to get a degree will do that). You have to have enough self-awareness to realize that you've just blown your entire afternoon on a game or online and you have nothing to show for it, and maybe you should try to squeeze in some actual work before the day's over.
Two, you have to have the discipline to recognize the things that make you procrastinate, and engineer around them. For me, it's barriers. Once I get working on something, I'll plow through it like a bullet through jelly. But, if I'm not yet working on it, and there's the merest little speed-bump of a barrier to overcome before I can work on it ... then I don't want to start.
So, for that reason, I put a lot of extra effort into making it really convenient to get things done. I write scripts that do things for me with a single command. I keep things organized so that I don't have to find things (which is a barrier) before I can get started. I try to keep things simple.
But that's just me. Maybe it's different for you.
But I seriously doubt that the approach in this guy's article will actually help anybody.
- quizbiz 15y agoWould love to hear more about "I write scripts that do things for me with a single command."
- thaumaturgy 15y agoIt's nothing fancy. I'd be embarrassed to say much about them on HN.
- jackowayed 15y agoA simple example: if running your development server requires remembering several parameters for the command and possibly also requires starting up a database, that's annoying and may require you to look it up. Not a good starting-work experience It feels unnecessary, but have a script called run in the root of your project that does that startup stuff. Then you just run ./run and it's time to code. No friction
- pbhjpbhj 15y ago>"have a script called run in the root of your project" // Bleurgh. Why not give it some sort of descriptive title? "./run-startup-actions-initialise-database.sh" would only need an extra keypress to start with shell completion active.
- phlux 15y agoI agree, though also I have found my self making aliases for lots of things and using them for a year on a box - then moving to a new machine/new job and not recalling how to do any of the things manually. Years ago, when I was at Lockheed, we had to do a bunch of stuff in support of devs - and after having them "train" us on the ridiculous install of their product, we wrote scripts and aliases to get the job done - but then after some time were wholly dependent on the scripts and couldnt do it by hand any loner.
- pushingbits 15y ago(article seems to be down right now, so I have no idea what it's saying.) >>requires two forms of self discipline Anyway, I've tried the pure willpower self discipline approach for a long time with mixed results. Not like I never got anything done, but I wasn't as productive as I would've liked. And the thing is, I thought that willpower was the only thing that could possibly work. All those other things people did? Gimmicks. Trying to trick yourself into being productive? Guess they didn't have the... willpower. Well, that kind of attitude didn't improve things for me. Willpower is nice. Some willpower is needed. But there are ways to make whatever willpower you have go farther. For instance, one thing that made more of an improvement than all the "I'm going to be disciplined starting tomorrow!" mantras was just keeping a to do list with very tiny tasks. So instead of buying a programming book and then planning to read it all in a weekend by sheer willpower and then usually never starting or giving up after five chapters, I set up my to do list manager to show me "read one chapter" as a task every day. Now I'm working through 1-2 programming books a month in my spare time whereas that used to take me half a year before. (I realize that you weren't promoting pure-self-discipline-and-nothing else and the low barrier to entry thing you mentioned is in a similar vein... just thought I'd emphasize that discipline is the starting point, not the end all solution.)