I my early 20s, after getting out of the service, I worked as an assistant manager at a fast-foot restaurant in the evenings while I did college during the day. It was a full load of credits, and the food place I was working was very busy too, so it made for a long, hard slog. One day I was talking to another of the assistant managers. I asked him about burn-out. Do you ever feel like you might be burning out? "Not m…
I'm still trying to figure out if the 'fast foot' restaurant was a mistake or a pun in relation to life being a marathon ;) That's an excellent point though, and if life is a marathon then being burnt out is probably best compared to having to sit out a part of the race because you can't run any more. I'm all for tackling all kinds of stuff, sometimes more than what you can naturally expect a person to do, as long as…
Hey I was up until 2am coding and got back up at 8. When I get the coding Pon Farr on my mornings get a little hazy :)
This actually relates to your article. For the last month or so, I have been trying "banker's hours" coding -- 9-5 and taking time for everything else. It was great.
But something funny happened: I stopped making progress. Sure, I would make a little bit at a time, but nothing like what I used to do.
I finally figured it out a couple of days ago. For some reason, unless my body and mind is convinced I am serious about driving through to solve a problem, I get very little traction. But if it's 11pm and I'm getting ready to go to bed but realize I can code it better and then go act on it, things work out. Unlike working for a BigCorp, working for yourself involves a gut check.
A lot of problems are like hills -- tough on the front side but easy on the back side. If you only go 1/4 way up the hill, you just slide back down overnight. But if you go balls-in and stay with it until you make it, suddenly it becomes easier.
Perhaps one must suffer for their art.
At least that's my experience, for what it's worth.