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!
I read a lot, and my colleagues are nice enough to impart knowledge upon me where they have it.
A (non-exhaustive) list of the books I've read):
Predominantly, I have quite a bit of experience with Magento, and am passionate about performance, user interface and, to a lesser extent, security.
I keep a lot of notes which are a reasonable indication of my competency and interest. Generated by Hugo, deployed via Travis to a Kubernetes cluster.
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.
Full time developer at Sitewards GmbH
Developer, specializing in the development, deployment and ongoing management of Magento 2.
Developer, specializing in the LEMP stack.
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.
Just about all work has been collaborative, and I cannot take all credit for anything I've been involved with. However, some of the more notable projects I'm happiest with are:
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.
Now part of the standard workflow, lints are run as part of code review, and issues highlighted (and generally solved) before a human reviewer inspects the work. This reduces the nitpicking associated with code review, and provides some clear standards for code style to follow.
Implemented lints are:
In order to keep my own code as clean as possible, all the repos I work with run the lints over all files that have changed. If the lints are violated the violations are displayed in the terminal, and the commit cancelled.
The lints can be skipped by ensuring the environment variable "SKIP_LINTS" exists. However, to ensure I don't become lazy, a large warning notice is shown, and the commit is paused for 5 seconds.
You can see this git hook on GitHub
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.
A complete reimplementation of a one step checkout, requiring as little information from the user as is required by the other information specified during the checkout.
Still ongoing, but the goal is to have a Kubernetes stack that can be run on anything from bare metal to a cloud provider.
Highlights of this were:
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)
© Andrew Howden, 2017
Curious about how this site works? See the article