Live data from Hacker News

I Knew a Programmer Who Went Completely Insane

startingdotneprogramming.blogspot.com

131–140 of 336 posts

Re: I Knew a Programmer Who Went Completely Insane

#131
post #39

The trick to avoiding complete burnout is easy. First - don't care at all about your job. Remember that all corporations are by definition psychopaths and they will treat you accordingly. Second - never do more then 35% of the work you are capable of doing in a day. Third - if you find yourself getting stressed out tell yourself repeatedly "It's only a stupid job. There is no point in stressing about it."

Second - never do more then 35% of the work you are capable of doing in a day.

I'm a big fan of three-hour-per-day planning. "Metered work" (what your boss expects of you) should be limited to a 3-hour block, preferably a contiguous one. After that, find a way to sneak time into things that build your career. Don't mix the two. (You'll either cut the self-directed stuff and burn out, or give your job responsibilities the shaft and at zero, you might actually get fired.) When you need to spike, turn that 3-hour dedication to 4 or 5 or 6 for a little while. The nice thing about the 3-hour plan is that it accounts for slack, because things always take longer than they should.

It takes your boss 15 minutes per week (on average) to tell you what to do. If you do 15 hours of metered work, you're giving him 60:1 leverage. That's enough not to get you fired.

The trick to becoming awesome, I think, is to take that 25 hours of "working time" per week that most people spend on Reddit or Farmville or non-work IMing and turn it into Coursera or open source time (don't ever use it to write code you'll need for a side project; legal issues make it not worth it). It's not easy, though, because it's much harder to hide it when you're studying machine learning at 2:30 in the afternoon.

Re: I Knew a Programmer Who Went Completely Insane

#132
post #122

Earlier quoted context omitted.

I don't like labeling this type of situation mental illness. That suggests that it's only the individual who is ill. It seems to me that situations like this result from a sick system as much or more than from individual sickness.

Are you saying that the system is broken because some jobs ask you to be a hard worker? The article indicated nothing specific that the company had done wrong. It even admitted that the guy was "well treated and well paid" for his hard work - he just didn't like how he was "respected". It's astonishing me that getting paid and treated well to work hard triggers a comment that the "system is sick".

It's a matter of human beings being treated like cogs in a machine (which is in fact what they are in today's world). The potential of highly intelligent people is wasted by those who are better at extracting value than creating it. This leads to ever growing frustration which eventually explodes leading to the destruction of peoples lives.

These are seen as individual problems but if these trends continue I believe they will lead to the failure of human civilization and possibly of the human species itself.

hard worker - exactly the type of concept that the machine uses to exploit the naive.

Re: I Knew a Programmer Who Went Completely Insane

#133
post #109

Is it an american thing that workers do free overtime? I live in Sweden and I know NO ONE that stays late without being compensated either with money or shorter days later in the month.

It depends on the type of work you're doing. Most jobs in the US fall under the 'Fair Labor Standards Act' and are classified as 'exempt' or 'non-exempt'. 'Exempt' jobs do not require payment for overtime work. The classification of a job as exempt or non-exempt is not arbitrary but I don't know all the rules governing that. I would wager that the majority of people reading this page who live and work in the US would…

All "Computer Professionals" are exempt, so that would cover many of the people on this site. The other exemptions are rather broad and would probably cover most of the rest.

Re: I Knew a Programmer Who Went Completely Insane

#135

It's not only programmers. Its managers as well. Its anyone who subsumes their job to be their identity! At my old company (big corporation) management shuffles happen every 9 months to a year. One manager went from having 45 people working under him to 0. The guy had a nervous breakdown as well. I heard he swam in one of our large number of fish tanks. That could be a bad rumor though. Anyway he was admitted and all…

Easier said, then done.

Re: I Knew a Programmer Who Went Completely Insane

#136
post #84

Although this is an extreme example, I sympathize and often have feelings like this. But it's not about the amount of work; it's about the constant internal struggle. Let me explain. I have never had a problem about the volume or difficulty of work in any job I've ever had. In fact, some of my favorite memories of work have been sprints to finish something, whether in software, retail/distribution, or food service. I…

I have only 1.5 years of work experience as software engineer. Maybe I am wrong, but aren't most of these quirks just a part of working with others? Regardless you are working for yourself, a company or organization, you have to deal with people. And people can be unethical, apathetic, incompetent, rigid, inexperienced, inappropriate. And when your company become large, it will have processes to limit your reign of p…

You learn well, grasshopper.

Indeed, whatever your occupation you will balance imperfect choices of what you will do, who you will work with, and the outcome of your efforts. Humility and acceptance of your limits go far in preserving sanity, whether you lead a multibillion dollar corporation, write software with a team, or sweep the floors alone after hours. You don't have total control, but that doesn't mean you don't have some control; do what you can (sometimes that means doing your job well, and sometimes that means leaving your job for another).

Re: I Knew a Programmer Who Went Completely Insane

#137
post #84

Although this is an extreme example, I sympathize and often have feelings like this. But it's not about the amount of work; it's about the constant internal struggle. Let me explain. I have never had a problem about the volume or difficulty of work in any job I've ever had. In fact, some of my favorite memories of work have been sprints to finish something, whether in software, retail/distribution, or food service. I…

Unfortunately, after seeing Ed's previous breakdown on Hacker News (https://news.ycombinator.com/item?id=5361056), I have to see comments like this in a new light.

Re: I Knew a Programmer Who Went Completely Insane

#138
post #84

Although this is an extreme example, I sympathize and often have feelings like this. But it's not about the amount of work; it's about the constant internal struggle. Let me explain. I have never had a problem about the volume or difficulty of work in any job I've ever had. In fact, some of my favorite memories of work have been sprints to finish something, whether in software, retail/distribution, or food service. I…

Wow... This situation must be more common than I thought. I've had a few jobs in my lifetime that left me with the feelings you posted here... The beatings will continue until morale improves. These points: - working for unethical people - busting my ass while others sit and watch - watching horrible decisions made by those for their own benefit were ultimately the biggest reasons I've left jobs. In one place I worke…

Yes. The feeling is so common, it even has a name:

http://en.wikipedia.org/wiki/Self-serving_bias

Re: I Knew a Programmer Who Went Completely Insane

#139
It's the worst week in 11.5 years to joke about what a part of me wishes he had done, for the good of society, so I won't.

Seriously, though, we need to fucking take this industry back. (I am so fucking serious about this issue that I am willing to fucking split infinitives with "fucking".) These executive assholes are destroying trillions in value ( http://michaelochurch.wordpress.com/2012/11/25/programmer-au... ) and we have no fucking need for them. Do we need people who understand business, economics, relationships, and sales? Absolutely. And more than anything, we need genuine teachers to step up and provide leadership. What we don't need are the short-sighted extortionist fuckheads who pass for management in most companies.

Re: I Knew a Programmer Who Went Completely Insane

#140
post #34

>the extra effort and hours that you put into your job as a software developer does not usually amount to someone higher up thinking you should run the company. It has been my experience that good producers are more likely to be asked to continue to produce. In principle this is not even a bad thing. A great software engineer might not be that great as a manager or CEO. It would be better to have a technical career t…

It's also not necessary to move someone to management to give them more authority. Most software engineers don't want to deal with hiring/firing people or any of the other stuff that comes with being a manager, but they would be interested in having more say in technical decisions.
Post reply on HN