Professional Visitors README: Difference between revisions

From Cibernética Americana
Jump to navigationJump to search
No edit summary
No edit summary
Line 23: Line 23:
  <blockquote>
  <blockquote>
  In me this principally applies to the disconnect between the speed of my cognitive flow and that of the individuals from the group this page addresses. This is seldom  a problem with co-workers, regardless of their abilities as I quickly adapt to these once in production mode.
  In me this principally applies to the disconnect between the speed of my cognitive flow and that of the individuals from the group this page addresses. This is seldom  a problem with co-workers, regardless of their abilities as I quickly adapt to these once in production mode.
It has until recently though been a constant problem prior to that as many classes of IT labor buyers are focused on an individual with 1-5 years experience and a type of worker profile that doesn't apply to me at all. Here are some links to content here which will explain this in more depth.  
It has until recently though been a constant problem prior to that with some classes of IT labor buyers (or their 3rd party proxies). Here are some links to content here which will explain this in more depth.  
<br>
<br>
<ul>
<ul>

Revision as of 05:33, 22 September 2007

The material for the general anonymous user in "My Web For Smarties" is of course appropriate also for current, former, or potential biz partners or co-workers but some things can be said here specific to these groups.

  • "Quick Dispatch To Buy My Services "
  • "Patience is not a Virtue"

    This meme can be considered to have started with the Author(s) of Perl who famously declared the 3 principle virtues of a programmer to be hubris, impatience, and sloth. The idea is that these obvious vices lead to behaviours which ironically work for better software production. For example, because she is lazy, the programmer will add valuable features that prevent her from having to do stuff. See also "Impedance Matching" below.

  • "Impartiality and Moral Hazard"

    Conditions of production prevalent at this time entail various conflicting stakeholders whose interests must be taken into account. We take the stance of an Impartial Observer relative to these interests and are at great pains to make sure this Impartiality is auditable by examination of the biz processes implemented here: all source code*sup1;, our development and social intent, and last but not least, our books.

  • "Impedance Matching"

    In me this principally applies to the disconnect between the speed of my cognitive flow and that of the individuals from the group this page addresses. This is seldom a problem with co-workers, regardless of their abilities as I quickly adapt to these once in production mode. It has until recently though been a constant problem prior to that with some classes of IT labor buyers (or their 3rd party proxies). Here are some links to content here which will explain this in more depth.

    I may not be the right choice for some buyers of IT labor. In particular those with little in depth experience of software development and who have both simplistic expectations of what can be done, a lack of patience/flexibility, and a desire to get something for nothing or as cheaply as possible, regardless of any sense of fairness, should pass on me as a resource.

    Pragmatically pricing and time management are the standard resolving mechanisms for these difficulties.


¹ Of our software only! Clients in general are not presumed to support open source development for thier projects.