There is this whole Computer Sciences way of doing that, O-notation etc... but it is largely theoretical and concernes with algorithms, not tasks.

What do you mean by "estimate complexity"? It's one thing to look at complexity in the abstract sense (e.g. it takes N^2 operations on N items).

Task like 'create user' is numerically trivial, but may be extremely time consuming when you're talking to Active Directory.

It sounds like you're asking about how to analyze how much time a task takes (or many tasks take).

"Tasks" are not trivial. Tasks such as creating a user make use of algorithms (such as searching or sorting), so the traditional analysis applies. If anything, they are more complex, because you'll have to consider CPU and memory load, on the machines running the task, as well as network usage. Factor in the time of day. Even the degree of disk usage and fragmentation may affect how well a certain task runs.

How can I estimate if I'm at all able to accomplish something like 'Create Interface Module For Loudmouth Library'?

that would require using Inline::C or h2xs, following on that question, how do they compare in terms of required knowledge and free time?

I'm not sure what you mean by this. You want to create a module that does what?

In reply to Re: Estimating Task Complexity VS Loudmouth by rrwo
in thread Estimating Task Complexity VS Loudmouth by Eyck

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.