I'm Ryan Waggoner. I build things. I blog about how to work harder and smarter to build the life you want. You should subscribe.

How I Work



What I Do

Warning: nerd-speak coming up. Skip to the next paragraph if you hate acronyms.
I started programming when I was a kid, pecking out BASIC programs on a TRS-80 hooked up to my TV. I eventually graduated to C and C++ before discovering web development about eight years ago. For the last six years, I’ve been doing PHP/MySQL web development. I spent a year working in product management at CNET, which was an incredibly valuable experience.

Today, I help companies leverage a number of open-source platforms and technologies to accomplish their business goals, make their customers happy, and build strong brands. Some of the technologies and platforms I’m proficient in include:

  • LAMP: Linux, Apache, MySQL, PHP
  • Content management systems: WordPress, Drupal, Joomla
  • MVC frameworks: CakePHP, CodeIgniter, Zend, Symfony
  • Social networking apps: BuddyPress, Facebook Apps, Twitter Apps
  • JavaScript: jQuery, Prototype, Scriptaculous

I’ve done a variety of other types of projects as well, so if you need something that isn’t on this list, contact me.

Why I’m Different

Unlike many developers, I have a background in business and product management, so I excel at balancing technical requirements, business goals, and the customer experience. While I love technology and building things, I am a tireless advocate for the user, and my goal is to build things that customers can’t help but fall in love with. Ultimately, decisions about an application or project are up to the client, but I work hard to ensure that my clients understand all the pros and cons, so they can make the most informed decision.

My Working Process

This is the general process I follow for new projects. Existing applications or websites will have different requirements.

1. Discovery – We start by getting to know each other, the parameters of the project, and determining what technology or platform is the best fit for you. It’s important to balance short-term needs with long-term objectives, and selecting the wrong technology upfront can end up costing you tens or hundreds of thousands of dollars down the road.

2. Prototyping – Once we’ve selected the technologies to be used in the application or website, we flesh out the basics of the presentation layer. It’s not important that we get this perfect, but having static or functional mockups can help identify problems or issues with the application logic, user experience flow, and development prioritization.

3. Development – After we’re satisfied that we’re on the right track, we do the work of building out the actual core logic of the application. The majority of the work usually takes place in this step.

4. QA and Testing – A step often skipped by less experienced developers, QA and testing ensures that we minimize bugs and unforeseen problems in the delivered product. I run through a variety of user testing scenarios, do basic security checks, test for speed and performance, and check the site in all major browsers. More advanced testing and QA can be arranged if necessary.

5. Delivery and Deployment – Now that the application is finished, we have to put it out there for the world to see. This often involves integrating with other existing applications, configuring hosting, and writing documentation. The end result is a solid application with clean code and written documentation for future developers to reference.

What Now?

If the above sounds like it might be a good fit for your project, or if you have some questions or concerns that I didn’t address, you should request a quote. It’s completely confidential, only takes a few minutes, and it’s the first step to getting to know each other. Click here to tell me more about your project.

Subscribe by email:
Connect With Me