I remember discussing with a friend of mine who, at the time, was a recent hiree to Boeing. After a few months(!) of introduction and systems learning, he was tasked with writing a small portion of code. I don't remember the specifics, but it was a very specific task (e.g., "write code to display the fuel level in liters.)
After a day or so, he turned in his code (something like 30 lines) and was chastised for having done too much. "What are you trying to kill people?!?"
Turns out the regular output of their developers was something like 5-10 lines of code per day, and only certain days of the week. Finished products were peer reviewed before being QAd.
At the time, I was just learning early Ruby, and getting used to the concepts of rapid development, and it seemed so strange. Of course, if my webapp breaks, there aren't any lives on the line.
Comments
I remember discussing with a friend of mine who, at the time, was a recent hiree to Boeing. After a few months(!) of introduction and systems learning, he was tasked with writing a small portion of code. I don't remember the specifics, but it was a very specific task (e.g., "write code to display the fuel level in liters.)
After a day or so, he turned in his code (something like 30 lines) and was chastised for having done too much. "What are you trying to kill people?!?"
Turns out the regular output of their developers was something like 5-10 lines of code per day, and only certain days of the week. Finished products were peer reviewed before being QAd.
At the time, I was just learning early Ruby, and getting used to the concepts of rapid development, and it seemed so strange. Of course, if my webapp breaks, there aren't any lives on the line.