Comment Re:Software is neither "hard" or "easy" (Score 1) 409
But we *are* going to make that date.
You don't know that. There is no way of knowing that. Use it as a mantra at project meetings sure, but realistically there is no way of knowing for sure.
Admitting that one doesn't know about the future is pretty much all there is to it. If one can do it without loosing face, one might have enough experience to call himself a professional.
A team can succeed by creating an environment that is prepared for change, on every level not only system design. This change always happens and it is exactly what separates the wheat from the chaff. Change and how well you can survive it is what makes or breaks deadlines.
Having it "all figured out" is the claim of the rookie. Experienced programmers SAVE time by avoiding design that does not survive change, ie complexities. They know they will have to SPEND it later on redesign anyway. Rookies never save time for rewriting the whole thing. A rookie will never expect to since they already "got it all figured out".
You don't know that. There is no way of knowing that. Use it as a mantra at project meetings sure, but realistically there is no way of knowing for sure.
Admitting that one doesn't know about the future is pretty much all there is to it. If one can do it without loosing face, one might have enough experience to call himself a professional.
A team can succeed by creating an environment that is prepared for change, on every level not only system design. This change always happens and it is exactly what separates the wheat from the chaff. Change and how well you can survive it is what makes or breaks deadlines.
Having it "all figured out" is the claim of the rookie. Experienced programmers SAVE time by avoiding design that does not survive change, ie complexities. They know they will have to SPEND it later on redesign anyway. Rookies never save time for rewriting the whole thing. A rookie will never expect to since they already "got it all figured out".
