<commit_before># Resume

Continually in progress. Unfortunately (or perhaps fortunately?) I have a job
I enjoy, and am not particularly inclined to write a resume. However, below are
some things that came to mind.

## Education
Entirely on the job. I got my first professional development job after
experiencing some disaster running my own personal fitness training business,
and I have been faking it ever since.

## Competencies
If you're curious about the level of knowledge I have, check out
[my notes](https://docs.littleman.co/). They're visible as they're nicer to read
that way, and since it's deployed by Travis CI onto Kubernetes, updating them
is effortless.

### Languages
I'm pretty sure I could hack around in another language reasonably quickly; it
might take me a couple of years to feel at home in it, though.

- 7/10 PHP
- 6/10 JavaScript
- 8/10 SCSS/CSS
- 5/10 Bash, Shell
- 1/10 Go (I'm ambitious here, but haven't found anything to use Go for)
- 6/10 English
- 3/10 German
- 1/10 Japanese

### Environments
- 6/10 Linux (Debian, Arch & Ubuntu. Also, there's just so much to Linux! I'll
  never know it all)
- 5/10 Windows (I don't use it at all anymore, save for playing games)
- 6/10 Kubernetes
- 7/10 Docker

### Tools
- 7/10 Intellij IDEs (PHPStorm)
- 7/10 Git

## Work Situation
I work at Fontis, a specialist Magento development company in Australia as a
general Magento developer. My entire professional life has centered around
Magento!

## Notable Work
It's hard to point to things and say "There's something I did", as almost all of
the work I do is collaborative, and to take credit would be to do a disservice
to the other members of the teams I work with.

However, I can say "Here are some of the projects I've been involved with, that
I'm particularly happy with"

### Port the MageAudit Magento analysis tool from Laravel 2 to Magento 1.x
Most of the analysis existed, however the initial design had some inefficient
designs, and the opportunity was taken to restructure the design to make
additional analysis far easier to implement in future.

### Implementation if automated lints as part of the normal code review process
While still in its trial period, and more generally a proof of concept the PHPCS
lint is now a standard automated machine code review that takes place prior to
human code review.

## References
I could probably ask some people if they're OK to tell you what they think of
me. I have never asked before!<commit_msg>Rewrite my resume<commit_after># Resume
Below is a short list of the more notable aspects of my career. If you're
curious what I can do, ask me to do it!

## Education
Self taught.

## Competencies
I keep [a lot of notes](https://docs.littleman.co/) which are a reasonable
indication of my compitancy and interest. Generated by Hugo, deployed via
Travis to a Kubernetes cluster.

### Languages
I'm pretty sure I could hack around in another language reasonably quickly; it
might take me a couple of years to feel at home in it, though.

- 7/10 PHP
- 7/10 JavaScript
- 7/10 SCSS/CSS
- 5/10 Bash, Shell
- 2/10 Go

- 6/10 English
- 3/10 German
- 1/10 Japanese

### Environments
- Docker
- Kubernetes
- Linux (Debian, Ubuntu, Arch, Minimal RHEL)
- Windows 10

### Tools
- Atom
- Boilr
- Git
- Intellij IDE (PHPStorm, IDEA)
- Modd
- Lets Encrypt

## Current Employment
Full time developer at Fontis, PTY LTD.

## Employment History
### 3/10/14 - Present; Fontis, PTY LTD
Developer, specialising in the LEMP stack.

### 1/3/14 - 1/10/14 - Shop At, PTY LTD
Developer, developing a custom Magento based platform for multiple buyers and
sellers to showcase their wares. The company was a start up, and ran out of
funding.

## Notable Work
Just about all work has been collaborative, and I will take any full credit for
anything I've been involved with. However, some of the more notable projects
I have been involved with are:

### Port the MageAudit Magento analysis tool from Laravel 2 to Magento 1.x
Most of the analysis existed, however the initial design had some inefficient
designs, and the opportunity was taken to restructure the design to make
additional analysis far easier to implement in future.

### Implementation if automated lints as part of the normal code review process
While still in its trial period, and more generally a proof of concept the PHPCS
lint is now a standard automated machine code review that takes place prior to
human code review.

### Redesign of the GAZ MAN website
The design for the desktop site was kept as similar as possible to the current
design, but the design was ported to bootstrap 3.x and made responsive.

### Provisioning of a Kubernetes cluster on CoreOS
Still ongoing, but the goal is to have a Kubernetes stack that can be run on
anything from bare metal to a cloud provider.

## References
If you'd like to talk to some people about the quality of my work, let me know
(or just ask them. Large samples of my work are public)
{'fraction_non_alphanumeric': 0.056577086280056574, 'fraction_numerical': 0.017579308951303295, 'mean_word_length': 3.9798792756539236, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 2, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3063068', 'n_tokens_mistral': 1455, 'n_tokens_neox': 1319, 'n_words': 795}