Deeply caring about the quality of things we release. A system should be useful, be dependable, do the correct thing when given good input, expect non-sunny-day conditions and not do the wrong thing when they happen, communicate clearly with users and other systems, and have a reasonable cost for what it accomplishes - both up front and over time measured in time/money/hardware.A generalist who goes deep into subjects, reading the code as well as documentation to understand what is a system does and how.Experienced around development of server applications, internet service provider infrastructure, and projects doing integration and orchestration.
Listed skills include Apache, Linux, Postgresql, Php, and 29 others.