The Lounge is rated PG. If you're about to post something you wouldn't want your
kid sister to read then don't post it. No flame wars, no abusive conduct, no programming
questions and please don't post ads.
I agree with you, but lately it seems there are developers around who don't. When I was a teenager I got a 9:00 to 9:30 job 6 days a week. Got pretty good at eating lunch in 5 minutes, napping 20, and not having to be nudged awake. That was around 4AM. Documentation? I'll be happy to do it.
In my case we started with no documentation at all only few bad written specifications. Then we wrote some of the code(around 80 %) and start changing things because the specification writers didn't think of everything carefully enough.
After we "finished" my boss told me to make documentation on how things work o.O with no requirements, no examples it was said: Make documentation with graphics.
The task was for me alone and instead of only doing documentation i also did code review and found few bugs, guess who gonna fix them.
Microsoft ... the only place where VARIANT_TRUE != true
Some 15 years ago I went with my boss to sell our new (then first time Windows based) version of our application. The problem was that we had no such application, so I spend two week with Photoshop to create some nice images to sell...
I'm not questioning your powers of observation; I'm merely remarking upon the paradox of asking a masked man who he is. (V)
To me, documentation can be boring and so can test plans, but a lot has to do with what you're documenting. If it's a sick mess of spaghetti, yeah, it's going to be a pain to document, but good code/architecture can be documented fairly painlessly although it's always tedious.
On the other hand, I have come into a company, been asked to fix a bug or add a feature, been told that there is no documentation and no one knows exactly where the source code is, and had to figure out which of the installations of this code on the various servers is actually the one that is being used and not just left behind on a deprecated server or a previous version of the code, then get those assemblies and decompile it (thank you .NET), set up a source control server because they aren't using source control, put the code in source control, then figure out what the code is doing, come up with a regression testing plan, come up with a test plan document template because they don't have one, write up that test plan, ask managers to approve it (approve what? a test plan?), test it on my own machine because they don't have a dedicated test server for that production server and then explain to the web admin how to set up a asmx service on "his" server.
So, sometimes it's nice to come into a place and find a little documentation as well as all of those other non-coding necessities.
I'm just old enough that I'm on the tail end of the generation where you went to work, worked for a company for 30ish years, took a pension, and retired. Thus, it didn't occur to me that even though the job was making me miserable, it was ok to go somewhere else. I stayed at least 2 or 3 years too long.
Of course, like any situation, there's good and bad. I have some friends from there I still keep in touch with almost 20 years after I left; so, not all the people were bad.
Another thing to keep in mind is that if a place is bad for you, that doesn't necessarily make it a bad place to work. Some of the people I worked with back there are still there. Even though it became a horrible place for me to work, it's apparently working out for them.
If your co-workers/bosses/whatever tried to get you to stay, extra money/vacation/perks they offer still might not be worth it for you specifically. If you're miserable and hate to get out of bed each morning, it's just not worth the hassle. When you recognize that, time to move on.
I think it would be better to ask if people had never worked in a place that they hated.
I've had some miserable jobs, you know when it gets serious because the end of the weekend becomes deeply depressing. I just walk at that point.
I work on a freelance basis so I think I suffer less from the fear of losing a job, it's naturally not going to be there for that much longer anyway. Some people hate their jobs but fear moving somewhere else, which I guess is natural, but very often can keep them trapped in a miserable situation.