On 3 May 2010 20:56, Uri Guttman <u...@stemsystems.com> wrote: >>>>>> "HP" == Harry Putnam <rea...@newsguy.com> writes: > HP> "Uri Guttman" <u...@stemsystems.com> writes: > >> this is what has been bothering me here. you haven't yet spit out a > >> proper problem specification. as i kept saying comparing dir trees is > >> tricky and you kept showing incomplete examples which now all seem to be > >> wrong as you just made a major change in the 'spec'. now duplicate > >> filenames could actually be different files vs just copies in different > >> places. this is a whole other mess of fish. > > HP> None of what I've shown contradicts the full program... quit karping > HP> about it. Sloppy... yes, I have been. I wonder if that might be > HP> because I don't really have a good idea of what I'm doing or how to do > HP> it. What a surprise... that's why its called perl.beginners.
[snip] > you could easily have written up a short goal document. > > i have some directory trees which may have duplicate filenames and those > files could be the same or actual different files. i want to scan the > two trees, compare them and locate common filenames in both. then i want > users to be able to choose from menu what to do with the files when dups > are found. > > that is close to what you are doing. was that too hard to write? > > you are really closing your eyes here and just driving around. sure you > have learned some coding skills but you aren't seeing the bigger > picture. this will keep biting you until you discover it yourself with > more experience. that deep experience is what i am offering here and you > are refusing it. note that others aren't refuting what i am saying, they > all work with goal documents at some time or other. I have to support what Uri says here. You shouldn't start writing *any* code at all until you know what you want it to do. If you don't know what you want to do, you're groping in the dark. If you ask for help, people can't give you the help you need because they don't know what you want to do either. Every software engineering method incorporates this principle, usually as a step called "requirements analysis". It's a fancy way of saying "what do I want to do?" Phil -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
