I've been writing front-end JS since 2007, doing everything from a standalone Tetris clone in vanilla JS to complex AngularJS components for single-page apps.

I've also done some work with NodeJS, mostly command-line tooling.

I've been using bash and the panoply of standard Unix tools (ssh, cron, grep, sed, awk, find, xargs, etc...) to automate server maintenance, analyze log files, streamline my local development experience, and generally problem-solve since college.

Terraform, k8s, Ansible, and friends are all great, but at the end of the day just about any server you run will have bash - it really pays off to know it, because in a clutch it'll always be there for you.

I've used git in many ways, including:

* skunkworks projects with a Git box under my desk and code review in patch files 
* Gerrit's formal, idiosyncratic rebase-oriented super-rigorous code review workflow 
* as a Subversion client via git-svn
* GitHub's pull request model
* GitLab/Stash's merge request model

I use the CLI and Magit (an Emacs extension) for working with Git, and recommend learning the git CLI, but I can help you sort out the myriad confusions of learning Git whatever interface you prefer.

I've written everything from cross-platform desktop GUI software to complex webapps using Python 2, using procedural, object-oriented, and functional paradigms.

I've been using Emacs since a college professor recommended his C++ class use it for working on our Sun cluster.

It's my daily driver programming environment, and I have a heavily-customized configuration. I've written a few Emacs Lisp packages, too (though I'm not a Lisp expert).

I love it for its longevity, extensibility, flexibility, self-documentation, and openness.

I don't recommend it blindly - editors are personal, and Emacs is not the One True Way.

If you're curious, though, I can give you a glimpse of why you might want to use it.

I've been maintaining a side project with a friend using Python 3 since 2017.

I don't have extensive experience with it, but that has taught me some of the differences from Python 2.

I've done everything from advanced database design for complex data collections to writing complex queries for reporting. I normalize my tables until performance demands denormalization, I use foreign keys, I add indexes where they're needed, and I appreciate the subtle nuances of data structuring that distinguish an okay schema from a great one.

I've been using PHP to write website and API backends since 2012. I've used a variety of frameworks as well as vanilla PHP, and while the purist in me prefers Python and Javascript, the pragmatist recognizes why so many people wind up using PHP.

I've used Ansible to automate creating local VMS, test, and production servers. 

I've used Vagrant with various other tools to automate creating development environments, and it's my preferred tool for the job (paired with whatever provisioning system meets the production needs best).

I've been using and administering Linux boxes since college, and have done systems administration work throughout my career. I've dealt with the common problems of running a Linux webserver many times and can probably figure yours out.

I've always had an interest in exactly where and how the code I write gets run, and have cared about reproducible dev server setups since 2007. I don't know all the latest and greatest tools, but I do know how to make reliable, reproducible setups that work for both developers and operations people on local desktops and out in the wild.

Nginx has been my preferred webserver for years. It's incredibly fast, has a light footprint, makes HTTP load balancing easy, and is surprisingly flexible for being so minimalist.

Personal details

Nate E.

Summary

Technical skills