Live data from Hacker News

I Knew a Programmer Who Went Completely Insane

startingdotneprogramming.blogspot.com

91–100 of 336 posts

Re: I Knew a Programmer Who Went Completely Insane

#91
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…

constant work-prevention structure imposed by people who have never accomplished anything

I think this comment distills the essence of the problem the which gives people so much trouble. If your perspective is that of a maker/hacker then good work (which should be rewarded) is to make great things, things please people and improve their lives, and perhaps profit the company. If your goal is maximising profit for the company, sometimes good ideas will need to be canned or replaced by bad ones the customer wants, sometimes work will need to be stopped after much effort was put in, sometimes politics will override technical considerations. If your goal is maximising profit for the individual at minimal cost, you want others to do the work while you get the rewards, and neither the business nor other workers, nor their pet projects, are your concern - more fool them if they take the company propaganda as truth, believe they are living in a meritocracy, and don't realise the realities of workplace politics. From the perpective of a manager who has climbed the greasy pole to luxury while workers suffer horrible working conditions, who is the idiot?

I would argue that classifying people as idiots is not useful and obscures the real differences in outlook which produce this sort of friction. There are many other perspectives to work (not tied to specific roles like manager or programmer I hasten to add), and holding them does not make people idiots, in fact many others might view someone slaving away for a company in the misapprehension that they are improving the world as an idiot; both would be wrong. The best way to deal with this IMHO is to recognise that workplaces have a culture, which contains and controls many different aspirations, and if you find this culture toxic, you should change job if at all possible - it is very hard to change a company culture or the perspectives of other workers on their work. Also, work should not be your only passion if you want to remain sane.

Re: I Knew a Programmer Who Went Completely Insane

#92

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.

I think that it is. I've worked for a number of companies in north america but in the US people are basically expected to work long. If your co workers are working overtime to get more done then you should work overtime to get more done.

The latest company I was employed at there had me working ridiculous hours but this is completely anecdotal, I'm glad I have my life back.

Re: I Knew a Programmer Who Went Completely Insane

#93
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…

There're lots of people who feel like you do.

Re: I Knew a Programmer Who Went Completely Insane

#94
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."

True. 35% may be a bit low, however, but I agree with everything else. On my first job, I didn't follow these guidelines. That's a mistake I won't commit again.

I'd add:

Fourth - say no to overtime, even if it's paid. Unless you're really in desperate need for money, think for a copule of minutes and you'll realize that your time (which you can use to do a ton of interesting things, and in fact is ultimately the matter life is made of) is usually more valuable than your money.

Re: I Knew a Programmer Who Went Completely Insane

#95
post #14

Earlier quoted context omitted.

I don't think that works because if management is incompetent enough to neglect problems they are creating, do you think they are competent enough to realize they are causing them?

Sure there are many shades of gray. But, for example, if you keep telling your management (as in writing e-mails with CC to higher management or have it written in the meeting minutes) that we need more file servers because we might run out of space and they ignore it, then when it happens and you're not around to fix this next time they may think twice before ignoring your advice. On the other hand if you resolve th…

Very true. My client was always talking about how much better development could move forward if we worked with a bigger agency, so I stopped stalling it and let him spend a bit of his money to learn firsthand how much "better" everything gets. Afterwards I fixed everything they broke (paid by the hour of course) and haven't heard complaints since.

Re: I Knew a Programmer Who Went Completely Insane

#96

There are at least 3 posts from hellbanned users there, defending sanity of that programmer. Stigmatisation at work. :-(

I especially like lucian303's one, which I'll reproduce for those who don't have the appropriate setting:

> The 8 hour workday was fought for and won for a reason. To expect more, an employer would be unprofessional. To accept more, except when compensated or in extreme circumstances, makes the engineer unprofessional. One comes to soon realize this. (See The Clean Coder: A Code of Conduct for Professional Programmers (Robert C. Martin.)) Most companies, especially startups, don't. It's sad to think that the culture values high stress, long work hours with the inevitable diminishing return, and literally anything, no matter how unhealthy, to get workers to be slaves. At the same time, a lot of these companies have mediocre health and dental benefits with high cost to the employee.

> Yeah, companies don't give a shit about you. And why should they? Corporations exist to make money. That's all. Your health, while in the long-term helps this goal, in the short-term it doesn't. The shorter the lifespan of the company, the less they care. This is easily observed.

> The question is, why do you give a shit about your company?

Re: I Knew a Programmer Who Went Completely Insane

#97
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."

> First - don't care at all about your job.

Maybe it is counter intuitive but I think healthy dose of this keeps me more productive and more focused on the job. While at work I always try to keep somewhere in the back of my mind Bertrand Russell's quote: "One of the symptoms of an approaching nervous breakdown is the belief that one's work is terribly important". It helps.

Re: I Knew a Programmer Who Went Completely Insane

#98
post #53

Employers, even the good ones, will put as much work on your plate as you can handle and then keep going. Systematically a workplace just isn't set up to help an employee handle stress, or even pay attention to an employee's stress level. They'll ask you to work overtime even if it is obviously killing you because that's just how the typical work environment is structured. Even moving higher up in the food chain, to…

No they won't. Plenty of good employers understand work life balance, they understand that output doesn't linearly increase with time, especially in development. Good employers push their employees in terms of not letting them coast, giving them meaningful work and challenging them to be their best. That is not the same as piling on work and ignoring stress levels. There is an optimum amount of stress at which humans…

Do you even have any anecdotes to support this? I have literally never encountered an example of an employer proactively managing an employee's stress level. To suggest that an employer can somehow put employees at 'an optimum amount of stress' suggests a lot more understanding of employees than I think is possible in most scenarios.

I mean, yeah, we can spout platitudes all we want here. I agree that if you aspire to be a good employer, you should treat your employees well. But that's not the problem here: The example employee in the OP was a top performer who helped solve tough problems, and nobody seemed to suspect that anything was wrong until he snapped.

The problem is that workplaces are not designed to be able to identify an employee having problems with stress, let alone to actively manage it. I have never encountered a workplace that can do so effectively - some employers are better than others about things like work/life balance, etc. But the level of stress in your life is variable, and the level of stress being generated by your work is variable, even in the best of circumstances. It is difficult, if not impossible, for an employer to even understand how much stress you might be under outside of work.

For example, a lead artist at a previous employer got let go for getting into too many arguments at work. It was only at that point that we learned that he was having a really tough time because he was a single parent and his son was suffering from a severe, life-threatening condition. It's nice to think that if his supervisors had known they could have done something about it - maybe they would have - but from the outside it merely made him look like a bad employee. Maybe he wanted to keep his personal life private, maybe he thought he had it under control, or maybe they decided they had to set an example regardless of his reasons - but the point stands: Ultimately, it is up to you, not your employer, to manage your stress.

Re: I Knew a Programmer Who Went Completely Insane

#99

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 could be a cultural thing. In Spain and Ireland (where I've work), if there is some extra time involved, it's not compensated, unless it is very serious and requested from management (working weekends, etc) My impression is that some people just get a higher workload and work overtime "to catch up" without telling anyone. Of course that's a bad idea, as your manager won't probably notice that you are working overt…

I'm in Spain, and this is very much the case. Overtime is basically expected, in many places there's a real culture of not leaving before the boss.

Re: I Knew a Programmer Who Went Completely Insane

#100
Troll banned, right? Or "hell-banned" is it?

Either way. You're completely missing the point. First off "insane" is a completely non-precise term, and I strongly believe a clarification of psychological framework be made before the discussion actually begins. Let's stop wasting time on this. Let's stop throwing around "type" systems in CS but not in Psych, which are both supposed to be sciences.

I sent this to some developer (acting as a recruiter) for a prominent SF company during a bar run (he was looking for front-end devs not with 10+ startups under their belt but with someone they're looking to mold):

The Web is a hypermedia application. So we're building pretty much http://schema.org/ vocabularies implemented over models (Django, Rails, etc.) with hypermedia specs (front-end begging for more data in more stupid ways than anyone cares to document).

Look. You want kids who'll acclimate better than the Chinese or Russians to text editors like LightTable and who enjoy the pleasures of vim-seek.

And you want an actual Web, or at least people who have dreams which logically entail that such a thing is possible (dreams of mundane facts).

So what am I getting at? What are you dreams restricted by? Is it this or that job? What are you building? What am I building? And what why does it seem that we should be building these things, by our evolution? Demanding high-pay? Insane? What are you talking about? "High-pay"? "Insane"?

What does any of this have to do with the Internet Declaration of Independence? Why are you inheriting this psychological framework? Why haven't you consumed post-structuralism? Why is your Internet "American"?

Again: "Insane"?

That's in your headline. In your headline. Headline. That's significant weight.

Post reply on HN