Trading desk, as a research quant. The office was open-plan, there were constantly people passing behind me, and expletive-laden interruptions related to market conditions were frequent. For the first 6 months, it was very exciting, but eventually the sensory overload and taxing environment got to me, and I started having health problems. In retrospect, I think the open-plan office was much more of a contributor than…
Ask HN: Worst working conditions you have written code in?
31–40 of 75 posts
Re: Ask HN: Worst working conditions you have written code in?
#32Back in 2000 I was working at a startup in Washington, D.C. and we had been working 80-100 weeks for nearly 1.5 months before management finally brought in some contractors as reinforcement. All of the developers were in a 20x20 or so room working at folding tables. One of the contractors that they brought in had a form of Tourette's that caused him to make this noise that I can only describe as a loud squawk at rand…
Re: Ask HN: Worst working conditions you have written code in?
#33Hard to get work done with that right point firing and visible from the window.
Re: Ask HN: Worst working conditions you have written code in?
#34The worst time is at school, when my friends (tech-savvy people) ask me for questions in a very noisy way that I loose concentration. So I agree with most of you about concentration, we can class it then
Concentration
Computer bugs and speed
Screen (if u sit for long hours)
Mouse and Keyboard (especially for those cheap laser mouses!!!)
Computer noise (if it's an old dirty one)
your girl friend (if u got one!!!)
Those are all factors that can affect your programming or whatever you are doing if it's mind related, like Math or Physic calculations
Also I posted it in SOF, no the question was not closed
Re: Ask HN: Worst working conditions you have written code in?
#35Earlier quoted context omitted.
I was a grad student who worked in a fab. I found that after a couple of years wearing that bunny suit, mask, and rubber gloves for 6-8 hours per day (or, more likely, per night) I was completely used to it. I used to catch myself surfing the web in the clean room after hours. "Wait!" I would say to myself, "I could be doing this outside the clean room, where I could take off this silly suit!" But they are stressful…
yeah, no tunes, and i just couldn't get used to the sweaty hands from the gloves. i forgot about the mask. those dark red lines in your face, i much prefer my aeron chair and office now :)
Re: Ask HN: Worst working conditions you have written code in?
#36Wrote custom test-set software in a clean-room. Bunny suit, mask and rubber gloves for 8 hours a day. It was a windows box connected to a x-ray diffraction machine so I had to be in the room.
Finally, a keyboard that is free of bits of dirt. :)
There was a day when I was sitting there in an academic fab, in my bunny suit, and a fly flew by. At first I didn't notice. Then I did a hilarious double-take.
I believe the airlock design has been improved since then.
Re: Ask HN: Worst working conditions you have written code in?
#37Re: Ask HN: Worst working conditions you have written code in?
#38Re: Ask HN: Worst working conditions you have written code in?
#39Here's what the simulators look like: http://blafsen.net/photos/simulator.jpg
I changed the code, and brought the simulator up on motion to test it... and the machine started bucking like a horse and tossing me around the cabin. I had the instructor console right in front of me, and for a while it was physically impossible to hit the freeze button - I was being tossed around too badly.
That day I learned a lesson about testing: first check it with motion OFF.
Re: Ask HN: Worst working conditions you have written code in?
#40When I started programming I used to work taking care of paralysed people. This was a night job, and you had to stay awake for the entire night and listen in case any noise came from the bedroom, in which case I had to go check to see that the person had not moved to a position that could be dangerous for him. Since there was nothing else to do apart from listen, I wrote code the entire night. The problem was that wr…
You could have bought one of those noise-amplifying toys, stuck its microphone inside the bedroom, attached headphones to it and turned the volume up.