About the Author

Zach Gardner

I am a HTML5/JavaScript Consultant for Keyhole Software in Kansas City. I help large enterprises with Single-Page Application architecture as well as consulting on full stack development. In my spare time, I read anything I can get my hands on when I'm not playing Dad to a 1-year-old girl, or playing husband to my wife.

Lessons From Facebook: React/Flux

Zach Gardner JavaScript, Opinion, Technology Snapshot 5 Comments

Note This blog post will cover Facebook’s React JavaScript library and Flux application architecture paradigm. It is a summary of the presentation I presented at DevCon 5 on 7/22/2015 in NYC. Introduction All the buzz on Hacker News these first few months of 2015 has been centered around Facebook’s React library and Flux paradigm. I got the itch to try them out on …

Docker: VMs, Code Migration, and SOA Solved

Zach Gardner DevOps, Docker, Technology Snapshot 1 Comment

It’s rare that a piece of software as new as Docker is readily adopted by startups along with huge, well established companies. dotCloud, the company that created and maintains Docker, recently nabbed $40 million in funding. Microsoft also announced on 11/18 a Docker CLI for Windows. Docker will also play a central role in Azure as well as the next …

Famo.us Guitar Tuner

Zach Gardner HTML5, JavaScript, Keyhole Creations 2 Comments

The Famo.us JavaScript library was released on 4/10/2014. The idea behind it is simple yet powerful: make HTML5/JavaScript/CSS web pages perform and feel like native mobile apps. There have been many companies that tried and failed to use HTML5 to build apps. Facebook famously decided to ditch HTML5 for its apps in favor of true native code to drastically improve user experience. Famo.us was born …

Advanced Debugging Techniques in JavaScript – Part 3

Zach Gardner HTML5, JavaScript, Tutorial 3 Comments

Overview This is the third part in my series on Advanced Debugging Techniques in JavaScript. Part 1 introduced Validate Your Assumptions, Binary Search, and the debugger statement. Part 2 covered Bottom-Up debugging, Top-Down debugging, and Break on DOM changes. This blog goes into more of the Chrome-specific debugging techniques that I use on a regular basis. The last part of …