Slashdot Mirror
Worst Working Conditions You Had To Write Code In?
sausaw writes "I recently had to write code in a hot dusty room for 20 days with temperatures near 107F (~41C); having nothing to sit on; a 64 Kbps inconsistent internet connection; warm water for drinking and a lot of distractions and interruptions. I am sure many people have been in similar situations and would like to know your experiences."
Those guffaws are annoying.
I once had an office mate that LOVED Kenny G. I think those were pretty horrific conditions...
I once had to write code on a palm pilot while I walked 15 miles uphill in the snow while naked with a pack of wolves and two grizzly bears stalking me.
You had water?!
That's your cue, geezers.
Fuck systemd. Fuck Redhat. Fuck Soylent, too. Wait, scratch the last one.
I'll go you one better - I once had to maintain Perl code.
No folly is more costly than the folly of intolerant idealism. - Winston Churchill
You had to move your hands in between revolutions and very quickly type. No time for comments and indentation and occasionally it would cut your hands off.
I still have nightmares of those endless tendrils of code wrapping around my ankles... it's too hard to talk about, man. Just too hard to talk about.
512 MB RAM, 20 GB disk, 200 GB transfer, five datacenters. $19.95/month.
At a client. Ok I was debugging something and to be fair they did warn me not to spend too much time there, but it took a while to set things up.
Nasy experience actually, I could feel my nerves being a bit frazzled even the next day.
echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
Working in industrial automation. Installing a machine, and tweaking the code. An un-airconditioned plating shop in Oklahoma, in August, in a heat wave. So 100F+, near 100% humidity. Sometimes hanging above a vat of nasty chemicals while debugging with an oscilloscope.
Fun times.
Best Slashdot Co
My last Employer actually expected me to write code in the morning! We are talking pre 10am here. I still have nightmares...
A learning experience is one of those things that say, 'You know that thing you just did? Don't do that.' - D. Adams
This identical question can be found here: http://stackoverflow.com/questions/741581/what-are-the-worst-working-conditions-you-have-written-code-in
A paralegal I worked with was sent to do a document review at a Client's industrial site. She was in a small, metal shack filled with boxes of old documents. While she was working away, half a dozen guys in full hazmat suits came in. They were as shocked to see her as she was to see them since the building was condemned and they were there to clean it out!
If brevity is the soul of wit, then how does one explain Twitter?
No matter the physical environment, nothing is an intense and scary as the pressure that mounts above you as you attempt to code on a customer's premises, on production code, trying to find a problem you didn't cause and barely understand, with no connectivity and no source control and no opportunity for QA.
-mkb
I write automation software for sewage treatment plants, and sewage pumping stations. I could describe incidents that rival goatse.cx of old.
Floaters any one?
Cheers
* Carthago Delenda Est *
I was having to write code to debug radar problems while on board one of NASAs P3 Orions (not technically The vomit comet but close enough)... in a thermal suit where the ambient temperature would go below zero at high altitudes then they would perform corkscrew dive maneuvers at some serious G-force to point the nadir looking antennas above the horizon back down to 300ft above the ocean where the temperature would spike over 100 degrees and the turbulence would throw you from the seat if not for the 6 point restraint. And the korean grad students were barfing their tuna fish sandwiches everywhere so the whole place smelled as can be expected. YOU KNOW NOTHING OF PAIN.
---------
No matter how thin you slice it, its still baloney.
I once had to write code sitting on a metal stool in an aluminum rolling plant in Muscle Shoals Alabama in the summer. The background noise level where I sat was well over 80db, and the noise peaked at something over 130db when the machine was in operation. My connection to the embedded device was a 9600 baud serial line, and the code/compile/test cycle took 30 minutes on a 25mhz AT&T server running SVr3. Every time the guys on the rolling line wanted a break, they kicked the server until it reset and they had 15 minutes to go smoke. This would of course happen in the middle of me editing code.
Aside from the 110 degree temp in the plant, 100% humidity, and horrific noise level, I had to wear a dust mask to try and filter out the particulate matter from the grinding work down the line. When I'd shower at night the drain would turn a matted grey color.
My only memories of Alabama are horrible. Other than the ribs, of course.
As many here can attest, it only takes one bad boss to make working your conditions analogous to hell on Earth. I would argue that in the worst cases, your setup would be welcomed on a daily basis if got away from their boss that is not worth the dirt they walk on.
Invexi - a Phoenix, AZ based web design and web development company.
I was on-site at a clients' place of business for a few months and I had to endure weekly prayer meetings. Not just the run-of-the-mill prayers, but the owner of the company would speak in tongues. I tried to skip them, but somebody would always come to retrieve me and I was told that they were mandatory.
If I wasn't a contractor, I would have sued their asses off for every nickel they're worth.
I once had to write code is a super-small stuffy room.
That's not so bad, but I had to share it with two people who smoked like chimney. I am serious, that was before all those non-smoking laws. The two smoked close to a pack a day per person. I probably "smoked" more with these two than ever before, or after... And I am a non-smoker!!
The stench was so bad that, when I arrived at the office, and I was usually the first person to come, I would open every single window in the office to make sure some of the cold tobacco odor would go out a little bit. And I did this religiously, no matter how cold or rainy it was outside, since the smell was so bad I was that close to puking every time I would go in that room.
To cut a long story short: I had -- in about six months time -- a bronchitis, followed by a sinusitis, followed by a bronchitis AND a sinusitis at the same time! Each time, my doctor would look at me, and practically plead with me to stop working in that place.
Thank goodness, that contract only lasted for about 12 months. Most horrible conditions I have ever worked in. My hatred of smokers started in that place.
The right to offend is far more important than the right not to be offended. (Rowan Atkinson)
During the SARS outbreak a few years back, I was employed as a programmer in a hospital where there was a quarantined SARS area. As a result, the entire building was on lockdown and you couldn't enter or exit without a medical overview (they take your temperature, ask you a bunch of questions) and being suited up in a face mask and rubber gloves that were not to be removed for any circumstances... Try coding for an 8 hour day in rubber gloves and a face mask!
While working for the USAF developing a PTT (Part Task Trainer) for the new "glass cockpit" on KC-135R Aerial Refueler, my coding partner and I worked at the largest non-commercial airport in the US. Our office was a 6x9 closet. We were located by the fuel station, so every afternoon when the news choppers and flight for life choppers would refuel, the ventilation system pumped AvGas directly into the "office". It would get so bad that we would have to stop working from 3-5. After attempting to work through it at first, we would get dizzy from the fumes.
I once had a job at a wireless ISP where I would regularly troubleshoot disfunctional rooftop routers located on an antenna mast. This sometimes left me balancing my laptop on top of a ladder in order to connect to the crashed device, which was particularly fun on high buildings during windy days. Every tried to troubleshoot and fix a kernel panic by tweaking kernel driver source code in a situation where you could fall to your death if you lost your balance? It would make an awesome geek extreme sport.
I recently had to write code in a hot dusty room for 20 days with temperatures near 107F (~41C); having nothing to sit on; a 64 Kbps inconsistent internet connection; warm water for drinking and a lot of distractions and interruptions.
We were evicted from our Hot Dusty Room! We had to go code in a lake!
I'm going to burn the building down....
I'm sorry but I have to call BS on this. My brother previously worked with the Pentagon and my other brother codes in the Army. I myself was with military intelligence (make the jokes while you can) and the civilians NEVER were in the line of fire. And they were the ones who code for the military. No one codes in the line of duty; you may have to edit a configuration, change the settings, setup a terminal, etc... but as any coder will tell you, that's NOT coding. Changing a config file is not coding. System administration is NOT coding.
Maintaining a deploy of an app built on an MVC framework with a replication database backend... now thats coding.
This is my sig. There are many like it but this one is mine.
I was coding in portable building, (looks like a shipping container), in high summer. No a/c, no breeze... I was working with two cute and VERY well-endowed female coworkers who decided to skip bras and wear the smallest cut-away T shirts possible. Oh, and thin summer mini-skirts.
They might just as well have been naked.
Now you try and debug a financial application written in uncommented RPG3 in that environment...
I was riding my Xooter around on the hardwood floors of our TriBeCa luxury office loft in my tailored suit, while on a conference call via the wireless headset. As I veered around the servers, Aeron chairs, and putting green, I stopped by the espresso bar in our giant kitchen only to realize there was no more organic fair-trade raw sugar! I xooted over to the PM & demanded an explanation. He gave me some lame excuse about there not being any at the store.. I told him if the situation wasn't rectified I was going to raise my consulting rate another $10! Needles to say, the next day we had the sugar, but I had to suffer such horrible indignity and it changed me forever.
Try sitting next to Sarah Palin.
Try sitting next to Cowboy Neal.
Customer site. There was already a contractual dispute. Entire company hated our guts (some because of the software, some because of the contract). Were perfectly happy letting us know how much they hated us.
Were in one room with company owner. Guy smoked cigars all day long. Had two PC's + keyboards + mice + documentation on a tiny six-sided table. Bad chairs.
Topping it all off, this was in an office with a view on my grandmothers house. She passed away while I was typing code in that damn office. Was taken to task by company owner for leaving work early that day. Asked for and received a transfer to another project after that.
Bloody lugzhury.
We had to write "dent-code" in braille using a white-hot knitting needle on sheets of wet tissue paper of while being submerged up to our tits in lava.
The worst punishment of all? The only thing we were allowed to drink was shitty American megabeer.
My Human Gets Me Blues.
The use Exchange on the battlefield? Suddenly, I feel a whole lot less safe.
Over 100 degrees in a bedroom owned by a slob of a teenager.
With a monochrome display that was prone to collapsing the image to a single dot in the center of the screen.
With a 25 line, 40 column text display that wrapped upside down over the last two lines.
With 64KB of total memory.
Less to actually work with.
In assembly.
Of course the disarray of the room was self-inflicted.
Not a coding job, but by far one of the worst I ever had.
In the mid 1980's, I worked in Reno as a houseman for a large hotel casino. Being a houseman was bad enough. Having to move furniture, sort the dirty linen, cleaning up rooms that the maids called "too dirty" for them to clean. But on one day, I was looking for a way to make some brownie points with my boss, when he asked for a volunteer to clean a room. I made the mistake of raising my hand.
Before I was sent to clean the room, I learned that the guest had blown his brains out with a small caliber gun. I was to clean the room and place any "biologic matter" in a special haz-mat bag they gave me.
I then was briefed by the detective on the case that the bullet had not yet been found. Part of my cleaning job was to "feel" each piece of brain matter as I bagged it up for them to look for the bullet. It was about two hours later, when I had finished cleaning the room that I learned from my boss that they had found the bullet. He didn't want to come up and tell I didn't have to keep looking for it, because the idea of seeing the mess make him feel sick.
I was so pissed that I tossed the bag-o-bits on his desk and told him to call the cops to ask for a pick-up.
Carpe Scrotum - The only way to deal with your competition.
I was once 'invited' to a Barbeque at my boss's house on a Friday evening. When all of the programmers had shown up, he had us check out his new computer setup. We entered this little room with about a half dozen PCs.
He then LOCKED US IN and told us we could leave when the programming project we had been working on was finished.
Yes. You read that correctly. He kidnapped about 8 people.
I had no family at the time so I thought it was all great fun. But some of the married people were less excited to be forced to work the weekend. The conditions weren't terrible, but no one likes to work anywhere there is no choice.
No surprise but the upshot: Many programmers quit, boss was fired, company soon folded.
I worked for a research facility out in the New Mexican desert for many years. It wasn't too bad until one of the teams farked everything up with a resonance cascade during one of their experiements. Damn alien sons of bitches... and then there were the marines... Horrors that you can't imagine.
I'll never go back. I've since landed a job with Aperture Labs working on a project called GLaDOS. Much better.
Dedicated Cthulhu Cultist since 4523 BC.
My worst environment was revising code on a UNIVAC 1230 in the late 1980s in a metal shack out in the middle of the Mojave Desert. The source code had been lost years earlier, so one had to patch object code using toggle switches to enter data one bit at a time.
But it make this more challenging the tape decks were ex-Navy warship units - armor-plated and weighing over a ton. Unlike on board the ship, the drives were not bolted down to a metal deck, but just sitting on a plywood floor. Each tape deck unit had three tape drives that slid out. The kicker - you had to remember never to pull out more than one drive at a time, and to lock each in place when it was closed. Otherwise the armor-plated deck would tip over and crush you to death.
Oh, and there were rattlesnakes outside. The deadliest species - Mojave Greens.
Starships were meant to fly, Hands up and touch the sky - Nicky Minaj
The building was the research wing of a nationally known foundation. I'm not going to name them because I actually like the organization and admire their work. HOWEVER.....
When they bought the ventilation system for the researcher's fume hoods it was spec'd stainless steel with a draining gradient to prevent pooling of condensation. What was actually built was a sort-of-level duct system made from the same galvanized steel components as the HVAC system.
To save money on duct hangers, they stacked the fume ducts with the HVAC ducts, HVAC on the bottom. The guy in the basement was researching plant DNA, and for complicated reasons he used to boil skunk cabbage in fuming nitric acid from time to time. When he did this in the summer, the airconditioning in the HVAC ducts cooled the whole duct stack and the mercaptan-laden acid condensed into puddles on the more-or-less level bottoms of the fume ducts. Eventually, near the end of one hot summer, the acid ate through both layers of steel and toxic fumes from dozens of research experiments in six stories of lab building were comingled with the building atmosphere. The HVAC system was on a duty cycle and the fume exhaust system was on constant fan, and things got real ugly real fast; people vomiting and being sent to the hospital, itchy, burning eyes, the whole nine yards.
To fix the problem, the entire building HVAC was ripped out, stem to stern, over the course of a month or so. This left me (on the fifth floor) with no AC for the central computing system (a DEC mini that blew quite a bit of heat). With no external wall (since the new library wing got built over it) I had to chop a hole with a hatchet into the wall leading into the main hallway and install a household window air conditioner in order to get the payroll and other critical jobs run. This put the hallway at 107 degrees Fahrenheit and humidity like the amazon rainforest, and the computer room in the high 80s to low 90s depending on how often people sneaked in to cool off. It also necessitated turning all the lights and conveniences off because the AC unit overloaded the available electrical circuits.
You'd think that was bad enough. But actually it was OK once we got used to it; I ran extension cords and 20mA loops out to the roof and set a couple VT100s up there so my cow-orkers and I could work on the roof in the (relatively) cool breeze in t-shirts. We had smokes and tall drinks with umbrellas in them, it was OK as long as it wasn't raining. It was worse by far for the scientists who had to continue working in stuffy, unventilated labs and offices (did I mention that nobody stopped working for any of this?).
But the months dragged on, and the HVAC reconstruction did as well. Other crises came and went and various stumbling blocks were overcome, but in the middle of a freezing Philadelphia winter we had no heat but that generated by our trusty DEC mini! Since the building circuits were (still) inadequate, electric heat was reserved for offices and labs without heat-generating computer systems. I personally cannot type with gloves on, I had to periodically escape to the heated wings or rub my stiff fingers over the PDP's exhaust fans so I could keep coding. This was while re-writing the database software for a 12-million-object live database... you could see your breath in the computer room.
Nearly a year passed before the last wall was sealed up and the HVAC/fume systems were pronounced sound. During the course of the demolition, several walls that I had drilled and sleeved for cables were taken down, and when they were mortared back up the mason for some reason carefully separated each wire bundle into separate ethernet and 20maLoop cables, laid one down every foot or so into the mortar bed, and laid block over them. When you entered the wiring closet, the wires were growing out of the wall like bright blue and grey grass, over about a ten-square-foot area. It was dumbfounding. I discovered this when communications starting failing everywhere... the li