Jim Wilson writes: > From where I sit, I'd have to agree more with David. There should be no cruft > left in the code that gets committed. This doesn't mean individual developers > can't keep it around on there local drive, but once something is good enough > to commit it should contain working code and nothing else. Critical > information can always be kept in comments, but ifdef'ed or commented out code > is very distracting. For here on out I hereby give anyone permission to hack > out any dead, commented out, or useless code that I submit to the project. > You don't need to ask. :-)
That works fine as long as the other person doesn't misidentify undead, unuseless code as being dead and useless. Not asking first can lead to hard feelings, and there's been too much of that going on around here lately. Where we can find ways to be nicer to each other, that is good. :-) > On planning ahead: Back when I studied systems analysis 20 years ago, > planning ahead was everything. Hardware price/performance, OO design, and > networks have changed all that. These things are what make requirements so > unpredictable these days (and systems so flexible). How many distribution > software designs of the early nineties anticipated web based e-commerce? But > now as the business world becomes increasing internetworked, requirement > cycles measure in weeks and months, not years and decades. It is hard to > break old habits though. This can be viewed at different levels. No we can't predict the future, and yes we need to be nimble and flexible and quick to adjust to the world changing around us, but some planning, some vision, some anticipation of the future is necessary to be succesful. Anyone who writes successful code is doing this at some level even if they say they aren't. :-) Curt. -- Curtis Olson IVLab / HumanFIRST Program FlightGear Project Twin Cities [EMAIL PROTECTED] [EMAIL PROTECTED] Minnesota http://www.menet.umn.edu/~curt http://www.flightgear.org _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel
