Hacker News new | ask | show | jobs
by bitwize 5128 days ago
Step 1:

Realize that if you don't work, you'll fucking starve.

Step 2:

Close HN.

Step 3:

Work like fucking crazy, to put as much distance between yourself and starvation as you possibly can.

3 comments

Step 1 is not really true for a large number of middle-class Westerners, though, and even less true for middle-class Westerners with tech skills. There are a lot of unpleasant things that would happen if I stopped making money tomorrow, but it would be a long time, if ever, before I starved. Between savings/friends/parents/foodstamps/etc., I would have to seriously run through about 20 fallback plans before literally not having food.

And in particular, it doesn't solve the independent-motivation problem. There are a lot of people who can work a regular job who have trouble, at least initially, getting into a productive self-directed work mode. If someone is trying to figure out how to transition from regular employment to self-directed productivity, telling them that their motivator should be money-making to eat misses the point, because they could do that via the "failure" option of just giving up and going back to a 9-5, too.

If I stopped working tomorrow, it would be months before anyone even noticed. Probably much longer before they got around to stopping my pay. This doesn't help with motivation at all.

This doesn't help with motivation. You folks who are living on the edge of starvation have it easy!

"You folks who are living on the edge of starvation have it easy!" Where did you assume that from?
I think it's a joke.
i think this concerns working on stuff beyond satisfying basic needs

that project you wish you'd get done in your spare time

Step 4:

Burnout, depression, homelessness

The above is the advice of an amateur who hasn't actually had to tackle work in a self-motivated manner whether the OP fits that mold or not.

Moderation and focusing on what is actionable is how you keep rolling.

This is spot on. After four years as an independent, burnout is a huge issue. I'm 1/3 as productive as when I started down this path.
I have had unproductive patches too as an independent. right now I am going through a reasonably productive time. There are times when the inspiration just kind of flows, and even hard problems end up being easy when confronted. There are other times when simple problems end up hard. There is some natural oscillation between the two. I have started to learn to take advantage of the pattern. Take down time when I need it (that's a hard thing to do as an independent) and work hard a lot of the rest of the time, even if it's only 6 hrs a day of hard programming (and probably 4 hours a day of other crap, and another 2 hours a day of still other stuff).
Do something else, and exercise. Both help incredibly with burnout.
I hit burnout and was less productive for a long time.

It's taken about five years, but I'm almost back to full productivity. I'm basically back to normal, or better, in my day-to-day work, but I still have almost nothing in the way of progress on side projects compared to before.

Advice:

1. Pace yourself, get some work done, then go make coffee/food, or in my case, go for a motorcycle ride/work out at the gym.

2. Exercise. Hard. No walking on the treadmill shit. Start strength training and do sprints for conditioning/cardio. Our bodies weren't meant to languish in front of a computer and tend to throw a snit-fit if you don't satisfy them.

3. Have a hobby/hobbies that don't involve a computer. As stated before, for me these are strength training and the motorcycle.

4. Read a lot.

5. Focus on actionable, bite-sized amounts of work. Don't think about macro, long-term, or broad scope stuff. You'll just get overwhelmed. Let the dopamine hits come rapid-fire as you check things off in quick-succession throughout the day.

With that, I'm off to ride in the mountains.

Good luck.

100% agreed with all of the above, except I would add one caveat to #5....

I think one does need to focus on macro, long-term, and broad scoped stuff a bit. This doesn't mean keeping it as a goal (which I think is your point) but it does mean setting aside time to plan, think about the long-term, re-evaluate where you are from time to time, etc. At the same time these plans should be shelved once complete and only reviewed periodically. The point of such planning is to think about the long-term not map out how you are going to get there. As Eisenhower said, "Plans are nothing. Planning is everything."