Well, congratulations. You made it. I knew that you could do it; I believed in you the whole time. You see here? Here's a guy who's calm under pressure, enjoys taking a big-picture view of things, and gets really excited when he hears a good idea. He's just itching to try it out. The problem is that
Well, congratulations. You made it. I knew that you could do it; I believed in you the whole time. You see here? Here's a guy who's calm under pressure, enjoys taking a big-picture view of things, and gets really excited when he hears a good idea. He's just itching to try it out. The problem is that there are so many really cool things going on right now.
Our friend Danger here really enjoys wielding machines--that's his phrase for using machines (generally computers) to accomplish vastly more than could be accomplished without them. He's excited about writing programs that write more programs, code that generates more code, in building (generally large) things that allow people to build very small things that then do the task of very large things. Remember, writing actual code is usually the easy part. The hard part is understanding what you want. And if you want a lot, then you'll need a lot of code, and then things become time-consuming.
He also generally dislikes frustratingly inefficient things. This includes, but is not limited to, "old" or "standard" software that just doesn't do the job. He's not afraid to dig into an open-source project and submit patches to get things fixed up. But he's also not afraid to build a better version on his own. Some open-source projects end up becoming so big that they become useless to everyone. For example, a "standard" suite of tools and libraries that have requirements to be run on tiny little embedded systems but also enterprise servers, and also being backward compatible with the version from 10 years ago. That's frustrating, and it actually just ends up being difficult to use on all systems. If we don't care about embedded systems, for example, then let's build a version that works for our needs perfectly.
Senior DevOps Developer @ This was an exciting opportunity; SevOne previously had no formal DevOps organization, and I got to join this all-new team composed of people from various positions throughout the company.
* Scrum master for DevOps team
* Automated appliance-build process and VMware OVA creation
* Created JSON REST services
* Created Polymer Web UIs
* Created Ansible playbooks for various new services From August 2015 to Present (5 months) Director, Quality Control @ * Determine weak points in software development and release workflow and address them.
* Develop tools and process to aid both the QA team and QA effort.
* Jump-start new projects, get the frameworks and processes in place, and then hand off to QA team. From August 2014 to August 2015 (1 year 1 month) Director, Architecture @ * New framework and automation development.
* Responsible for code and design standards.
* Responsible for various training and education topics (for example, SNMP, ZeroMQ, etc.).
* Escalation point for Support and Development. From March 2013 to August 2014 (1 year 6 months) Software Architect @ * Requirements gathering from customers.
* Full design specifications for new projects.
* Performed integration work with partner companies.
* Escalation point for Support and Development. From 2010 to February 2013 (3 years) Software Engineer @ * General product development involving the entire software lifecycle.
* Primary focus on daemons and other background aspects of the system.
* Meeting with customers to better understand their requirements and needs.
* Product support (answering phone calls, meeting with customers). From 2006 to 2010 (4 years) Intern @ Start up time! In addition to all of the fun and crazy stuff that went on by virtue of having only three people in a garage, these were some of the more visible things that I did.
* Updated and simplified original graphing engine.
* Decoupled data processing from data visualization.
* Created a new user-access system.
* Improved HA solution.
* Reduced language count by converting magical Perl scripts to PHP. From June 2005 to 2006 (1 year)
Bachelor of Science (B.S.), Computer Science @ University of Delaware From 2003 to 2006 Massachusetts Institute of Technology From 2012 to 2012 Fire Service @ Delaware State Fire School From 2013 to 2014 Delaware Technical and Community College-Stanton-Wilmington From 2008 to 2014 Cecil College From 2008 to 2008 Charter School of Wilmington From 1999 to 2003 Douglas Manley is skilled in: Linux, PHP, Distributed Systems, MySQL, SNMP, C++, System Architecture, Git, Bash, Enterprise Software, Java, Database Design, Subversion, Software Development, Apache
Looking for a different
Get an email address for anyone on LinkedIn with the ContactOut Chrome extension