Live data from Hacker News

Ask HN: Worst working conditions you have written code in?

news.ycombinator.com

11–20 of 75 posts

Re: Ask HN: Worst working conditions you have written code in?

#11
When 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 writing code can get very mentally taxing after a few hours in the night, and combined with the thought that spacing out can result in a persons death, it was a very demanding task, particularly in the period from 4am to 6am.

Re: Ask HN: Worst working conditions you have written code in?

#12
post #3

Not working conditions per se, but debugging a legacy bioinformatics program written in perl. Comments were in french which I do not understand. It took three days to run and exited with: "Error - good luck finding the bug".

Ooh, and it insulted you ! And in French, too (I presume). Total burn.

Re: Ask HN: Worst working conditions you have written code in?

#15
post #7

Wrote 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.

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 places to work. The noise is quite troublesome and the ergonomics are generally awful.

Re: Ask HN: Worst working conditions you have written code in?

#17
post #10

A hot, noisy hotel room, dial-up internet, 4:00am writing in _VB6_ to connect to some weird COM+ service that used VB calling conventions, then a C++ COM wrapper for that, then a C wrapper to connect to a Java JNI service. At 8:00pm I didn't know VB, either. And it had to work by 9:00am when some system it interfaced to started up. Oh - and I couldn't actually test it against anything but stubs.

How did that turn out? What was your margin of safety? I hope they appreciated the heroic effort you put forth.

I haven't done anything that crazy but have debugged (and fixed) a few memorable, painful, stressful software (usually system integration) problems on frantic conference calls mere hours before the paid-for-and-scheduled on-site training on the software commenced.

Re: Ask HN: Worst working conditions you have written code in?

#18
This is not my story of course but the story that immediately popped in my memory when I read the title.

Steve Wozniak's story about rewriting floppy drive low-level software the morning of a big demo:

>I got it to where it was writing data on a track, reading the data on a track. Then I got it to where it was reading the data in the right byte positions. Then I got it to work with shifting tracks, and we wanted a simple program where we would say "run checkbook" or "run color math" and it would run the programs that were stored on the floppy disk. So we went off to Las Vegas, and Randy and I worked all night and we got it done to where it was working. At the very end, it was 6:00 a.m. and I said, 'We have to back up this floppy disk." We had one good disk that we prepared with the data hand-massaged to get it just right. So I stuck it in the floppy and wrote a little program, and I typed in some data and I said "read track 0," stuck in the other floppy and said "write track 0, read track 1, write track 1." There were 36 tracks—I had to switch floppies back and forth.

When I got done, I'm looking at these 2 floppies that look just the same. And I decided that I might have written onto the good one from the bad, and I did. So I had lost it all. I went back to my hotel room. I slept for a while. I got up about 10:00 a.m. or so. I sat down and, out of my head and my listings, recreated everything, got it working again, and we showed it at the show. It was a huge hit. Everybody was saying, "Oh my God, Apple has a floppy!" It just looked beautiful, plugged into a slot on our computer. We were able to say "run color math," and it just runs instantly. It was a change in time.

But the real eureka moment for me was the very first time I ever read data back. I wrote it on the floppy, which was easy, but read it back, got it right. I just died.

I think that Steve's entire interview is probably one of the most inspiring in Founders at Work:

http://www.foundersatwork.com/steve-wozniak.html

Re: Ask HN: Worst working conditions you have written code in?

#19
While I was in the Navy, I coded in my 2'x 6.5' rack on my ship while deployed and while the AC in my berthing was broken. It was 105 degrees inside my berthing (that I shared with 25 other guys) and the AC motor had caught fire so we were out of luck in terms of that comfort. I don't recommend doing this, it wasn't exactly a good idea to be coding in such heat and misery.
Post reply on HN