Metric discussion

There are intuition based competences and fact based competences. More age and therefore more contact will improve intuition based studies, as long as the environment doesn't change (or experience is incorrect). For fact based studies, I disagree with this principal. I state the structure like this, as one can't intuit the correct way to write an OBJECT tag in HTML, one looks it up.

For sales roles, there is little useful training that I have seen. For engineering, there are alot of low value courses that train you in what order to hit buttons in your IDE. There are also some high value courses which get you to defend a preposition, and allow open access to a large library. The former are expensive, the latter are long.

If one was looking at a new data storage system (e.g. MySQL going to MongoDB), the architecture changes are larger and so a longer period is necessary. One may study the API, and be able to use Mongo as though it was MySQL rapidly. One can start using a new system for a new project very quickly. To build document based systems, rather than a normalised RDBMS is a larger scope. Mostly the existing process would need to be massively revised.

My history (factual competences)

This lists commercial experience only, as commonly requested. I don't think that much of this list is headline material, but if you want an experienced developers, I list my history here. The figures are set with bounds, please see above text for why.

  • HTML (prefer HTML5), 5+ years
  • ms-word HTML for HTML email, I use a service that builds them.
  • ask for examples of specific HTML5 items
  • JS for forms (prefer libraries, but can build them), 5+ years
  • jQuery for forms, 5+ years
  • JS for complex applications, 4+ years, I need more study here, as it changes frequently.
  • OO JS, for large scale work, 5+ years
  • CSS, 5+ years
  • new CSS (i.e. MSIE10+), 5+ years
  • using CSS frameworks, 3+ years
  • mobile/tablet focussed, 3+ years
  • AJAX concept/SPA, 5+ years
  • AJAX libraries, 5+ years
  • AJAX via jQuery 5+ years
  • writing jQuery 4+ years
  • writing jQuery plugins 5+ year
  • using JSON, 5+ years
  • testing frontend, via behat/mink, behat/goutte or selenuim, 4+ year
  • testing frontend, via a browser catalogue (I use a 3rd party service), 5+ years
  • XML processing, 5+ years, mostly older stuff
  • XML tools (xmlspy etc), 5+ years
  • XML without tools, 2+ years
  • XML validation 5+ years
  • ask for specific XML frameworks, I have done alot of B2B?
  • (my XML systems generally have a regression suite, unlike the webpages)
  • API integration, 5+ years
  • API creation, 5+ years
  • REST creation, 5+ years
  • source control concept, 5+ years
  • GIT, 5+ years
  • SVN, 5+ years
  • PHP language, 5+ years
  • Perl language, 3+ years
  • Python language, several months
  • C language (Unix), 1+ years
  • PHP5, 5+ years
  • OOP/ OOA/ OOD, 5+ years
  • Zend2, ~2 years
  • Symfony2, 2+ year
  • Node, 1+ year
  • Express, 1+ year
  • Mongoose, 1+ year
  • REST architecture, 5+ year
  • SQL language, 5+ years
  • MySQL (variety of versions), 5+ years
  • Oracle, nearly 2+ years
  • Postgres, 2+ year
  • FMP, 1+ year
  • Mongo, 1+ year
  • use of transactions, 5+ years
  • use of temporary tables to make reports faster, 3+ years
  • managed data import, 5+ years
  • use of storproc, 1+ year
  • use of Catalyst, a few months
  • use of CPAN, 2+ years
  • use of Perl OO, 2+ years
  • complex tree structures in Perl, 2+ year
  • use of DBI, 3+ months
  • use of DBIx Class, 6months
  • use of XML processing in Perl, 1+ year
  • use of Perl templating, 1+ year
  • use of Unix make (for C), 1+ month
  • use of ant style build systems, 6+ months
  • use of jenkins, 6+ months
  • use of my own custom compile/ build RPM/ deploy, 4+ years
  • use of autoconf / configure, 2+ years
  • use of pear, 1+ years
  • use of composer, 3+ years
  • IP based networking, 5+ years
  • sockets, event IO, 5+ years
  • configuring IP based networks, 4+ years (at an ISP, I wrote software to do this)
  • Managing SMTP software (but not the service itself), 3+ years
  • Managing routing software (but not the service itself), 3+ years
  • linux/ unix, 5+ years
  • bash, 5+ years
  • redhat or centos admin, 5+ years
  • ubuntu admin, 4+ years, but is my primary OS on my personal machine
  • have used Amazon ec2
  • manage mac osx 3+ year
  • managing PHP, so the right modules are available, 5+ years
  • deployment via RPM (making the RPM myself), 5+ years
  • deployment via GIT, as source, 5+ years
  • deployment via composer, 2+ years
  • installation via npm, 1+ year
  • managing/creating triggers in SVN or GIT, 3+ years
  • custom build platforms, 5+ years
  • managing auto-config (deploying different configs for each target), 3+ years
  • apache, 5+ years
  • NginX?, 1+ years
  • managing logging, 5+ years
  • creating man-pages, 5+ years
  • created invoicing systems, 5+ years
  • with multi-teir billing, 5+ years
  • reconciliation, 2+ years

My history (intuition competences)

  • unit testing (mostly use phpunit, qunit, test::more, junit), 5+ years
  • test automation (i.e. regression suites, test creators, CI), 4+ years
  • AJAX testing (distributed, multi-thread/process), 5+ years
  • architecture, 5+ years
  • multi-thread/ multi-process applications, 5+ years
  • templating (mostly HTML), 5+ years
  • Adapting services to meeting custom business requirements, 5+ years
  • Analysis of repetitive work/ automation/ kaizen, 5+ years
  • managing branding (on CSS, images etc), 5+ years
  • UX, revised sites to be simple and easy from a users perspective, 5+ years
  • business work flow (reducing time to solution by automation), 5+ years

Experience template

RSS. Share: Share this resource on your twitter account. Share this resource on your linked-in account. G+

Experience template

RSS. Share: Share this resource on your linked-in account. Share this resource on your twitter account. G+ ­ Follow