HTML, CSS, jQuery, Photoshop
I believe that a website's usability is paramount to all else. A design must be intuitive to navigate and has to push the eye to the most important information; yet avoid being intrusive.
A responsive site is a requirement, in today's mobile dominated world; therefore all websites must be viewable on any screen, device, and platform. Using CSS3 it is now more efficient than ever. This involves tuning all the graphics to be as fast as possible and scale well.
Make it light and fresh; it should be as quick as possible, both in load time, and in the number of clicks to get from landing page to desired content. Using applications like Google analytics reveals necessary trends, and allows web designers to craft their experience to its optimum potential.
Clean and recognizable, using an icon instead of a word can put more information into an area, without sacrificing design. However, a design cannot impact the speed of the site, otherwise a user will most likely click off. This is where Font Awesome comes in, it is fast and light, and adds a whole list of icons to the table. This not only reduces page load, but also increases intuitiveness.
PHP, MySQL, Apache, BASH
The background processes are what turn a website into a usable tool. They enable the site to have a purpose; static sites can still be a draw, but without a back-end, users can't interact.
Websites must be flexible and have a purpose. Using a back-end allows the site to have a certain beauty to the code, it never updates, so it can be efficient as possible. And optimizations appear on all pages; instantly
The best back-end is one that is never seen, that is why using apache rewrite rules is important, it allows URLs to be pretty and intuitive, while in reality it is much more complex. In fact this is the designers credo, deign should be invisible, like the design of everyday things, it has to work without thought.
Ubuntu, Networking, BASH, Amazon CLI, GIT
I have ran a mini-datacenter in my garage for many years now, and the experience taught me a lot about what lack of information does. Command line has a sharp learning curve, not because it is difficult, but because there is no feedback. This reinforced my designs, and shaped my programs. A program command line or not needs to inform the user what and how an action is performed. My little data center also taught me about network layers, clustering, and distributed storage.
Command line manpages reinforced my love of good documentation. Manpages tend to be long, confusing, and miss the point. Good documentation answers the question asked first, and explains second.
Amazon cloud hosting has taught me that the best way to launch services is with the Phoenix approach. If a server or service is having an issue, replace it. It is good for fast iterations and bug fixes, because all servers are designed to fail, and be replaced; a bug is not a problem (once a fix is found). Simply replace the servers by terminating them and replace it, via a script or other automated method.
As an administrator i was also working on other projects, we needed a git server, so i decided to make one. We still use my server to this day as our primary git server. Git is one of those programs that once you find out about it, you don't stop using it. As a developer i learned git, as an admin i embraced it. We now use a few tools to augment this process; Jira, Stash, and Bamboo.