We just concluded the initial presentation of the Discussion Board project, and my was I shocked -- First, the project wasn't finished and nowhere near the proposed functional requirements, and Second, there were only a grand total of 2 questions asked by the instructor. It's a software engineering class which doesn't regard the Open Source development model, and still requires the documentation (ala Cathedral style) of weekly progress, and even documents for "end users" or "clients".
I personally despise the need to write progress reports in human terms -- mainly I want to show that progress is being made in terms of code and functionality. I don't want to put down into writing things that I feel about my groupmates, but rather I would like to commend them just for their accomplishments. I've just submitted one progress report, and I never really liked it. My grade may be in jeopardy because of that, but anyway that's how I personally feel.
This is one reason why I would think twice in working for a software development company which requires the employees to time in, and time out, and have some semblance of a productive working environment -- where you're forced to sit there and code for the time that you're there. Sure, there would be meetings, and discussions among members of the group, but deadlines don't appeal to me that much -- pressure only breeds complacency and a high risk of failure. I'd rather do my progress report in terms of patches, and patch sets. That way, there'd be ample proof that I had been working.
But then the world doesn't work that way -- but who likes the world as it is? I will never know...
Chill.
I personally despise the need to write progress reports in human terms -- mainly I want to show that progress is being made in terms of code and functionality. I don't want to put down into writing things that I feel about my groupmates, but rather I would like to commend them just for their accomplishments. I've just submitted one progress report, and I never really liked it. My grade may be in jeopardy because of that, but anyway that's how I personally feel.
This is one reason why I would think twice in working for a software development company which requires the employees to time in, and time out, and have some semblance of a productive working environment -- where you're forced to sit there and code for the time that you're there. Sure, there would be meetings, and discussions among members of the group, but deadlines don't appeal to me that much -- pressure only breeds complacency and a high risk of failure. I'd rather do my progress report in terms of patches, and patch sets. That way, there'd be ample proof that I had been working.
But then the world doesn't work that way -- but who likes the world as it is? I will never know...
Chill.
Comments
Post a Comment