in reply to Project Structure Revisited

This node falls below the community's minimum standard of quality and will not be displayed.

Replies are listed 'Best First'.
Re^2: Project Structure Revisited
by BrowserUk (Patriarch) on Aug 16, 2010 at 21:26 UTC
    This is an engineering problem.

    True. And if you are any kind of engineer, you'll understand why engineers have multiple of these, rather than one of these.

      Understood. Could you point the way to the Snap-On catalog?

      We don't need the conch anymore. We know who ought to say things.... It's time some people knew they've got to keep quiet and leave deciding things to the rest of us.
Re^2: Project Structure Revisited
by rowdog (Curate) on Aug 16, 2010 at 22:27 UTC

    I wish that you would please

    Listen to me.

    So I can tell you that

    The barbecue sauce is esoteric and mystical

    Which is why you have to

    Muddle through your own way.

    but you can learn from us through the use of the ancient art of

    Monkey see, monkey do.

    I really don't mean to be facetious but there's a reason our answers are all the same: if this could be elegantly solved by engineering, it would already have been done. If you disagree, well, good luck and please share the holy grail when you find it.

    A reply falls below the community's threshold of quality. You may see it by logging in.
Re^2: Project Structure Revisited
by oko1 (Deacon) on Aug 17, 2010 at 01:22 UTC
    I'm not looking to become a project management expert but I'd like to learn enough to keep from screwing myself every time I touch a file.

    An apropos quote:

    Don't blame me for the fact that competent programming, as I view it as an intellectual possibility, will be too difficult for 'the average programmer'. You must not fall into the trap of rejecting a surgical technique because it is beyond the capabilities of the barber in his shop around the corner. -- Edsger Dijkstra

    Project management - scalable project management - is like that. Whether you like it or not, that's the scope of it. You can't take an arbitrary piece of it that's "just enough not to screw up"; the field is complex enough that experienced people still screw it up on occasion. They just do it a lot less often.

    It seems to me that, given this complex problem - one that requires a complex solution - your answer is "well, I don't like it being complex - somebody make it simple for me!" At this point, you've been told by a number of people, in a forum of what you yourself recognize to be experts, that it is complex and not reducible to the level of simplicity that you want - but you continue to behave as though argument will somehow force the solution that you want to come into being. I did mention "hire an expert, and then listen to them", right?

    I'm poor folks.

    Ah. In other words, you want (to steal a bit from BrowserUk) a stylish 18-wheel, 7-seat, drop-head, hybrid, supercar. With F1 performance, Prius economy, Peterbilt carrying capacity, Porsche cache and Spyder exclusivity. For nothing, or at least very cheaply.

    Well, frustration is supposed to be good for the metabolism, and can occasionally stimulate lateral thinking. Please let us all know if you come up with something new and interesting.

    But as you say, the cybersphere is full of starving experts. Maybe I should offer one a hundred bucks to put together a reading list. The question then is, "Who can I trust for good advice?"

    Ah. In other words, I/we have just converted your (essentially impossible) technical problem into a (relatively easily solvable) people management problem. You're welcome.

    (Hint: recognizing competence is a lower-order problem than being competent. Thus, HR and management.)


    --
    "Language shapes the way we think, and determines what we can think about."
    -- B. L. Whorf
    A reply falls below the community's threshold of quality. You may see it by logging in.
Re^2: Project Structure Revisited
by locked_user sundialsvc4 (Abbot) on Aug 16, 2010 at 22:06 UTC

    Your arrogance is breathtaking.

    Tell ya what, know-it-all:   why don't you “go find the book,” or better yet, just save Amazon the trouble?

    Any of us could, if any of us were so inclined, “fight fire with fire,” but why bother?   “Troll baiting,” while a mildly interesting exercise that occupies way too much bandwidth at some forums, does not work here.   You are addressing the world-wide community of Perl developers, and I am quite sure that you will find a different attitude to be much more fruitful.

    A reply falls below the community's threshold of quality. You may see it by logging in.