I thought your name was familiar. Hello! One caution/suggestion about your idea: a piece of code could be left unchanged because it is unused or poorly maintained. There are parts of the network, streams, file system, etc. that *should* have changed long ago. Core concept or complacency? But even calling attention to what does and does not change without knowing why could have some value. Note the reference to similar work in this thread.
Bill ________________________________________ From: [email protected] [[email protected]] On Behalf Of HwaJong Oh [[email protected]] Sent: Saturday, October 09, 2010 8:38 AM To: [email protected] Subject: Re: [Pharo-project] Learning by download all the mcz files from a repository Your name is very familar. Are you Bill Schwab from Dolphin community? If true, hi! I just want to be productive by learning packages effectively by researching better way of doing it. This idea is just one of them. The point of the idea is, sometimes knowing history can explain better than just knowing present. Quantum theory is very hard to understand, but its history tells us why the equations has to change. Some unexplainable facts enters and new theory can expain the past facts and new facts together. I think it is very similar in software. It has to change for a reason which was not the case in the past. Besides I can find some classes which do not change in the timeline. They can be considered as core concept of the package. Best regards HwaJong Oh -- View this message in context: http://forum.world.st/Learning-by-download-all-the-mcz-files-from-a-repository-tp2966289p2969523.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
