I will be out of the office today helping to facilitate a roundtable code update on the 2015 IBC, followed by a session of Code Jeopardy hosted by Jeff Batick of Allegion, so this post will be a quick one. Before I get to today’s topic, I just want to say THANK YOU for helping iDigHardware break some new records! In the month-long period ending yesterday, there were 25,696 visits to the site by more than 16,000 users, and y’all read more than 50,000 pages on the site in that period! There were 1,357 visits to the site on Monday – the highest 1-day total ever, and 416 copies of the new code reference guide have already been downloaded! iDigHardware was 6 years old in February (where’s the cake?? 🙂 ), and I’m so grateful for your participation. Otherwise, I’d just be talking to myself (the same way I feel when I’m telling the kids to do their chores).
Last week I posted a couple of videos explaining some basic code requirements and terminology for panic hardware. The next videos in the series address a topic that I KNOW many architects and others struggle with (because I’ve personally explained it at least a thousand times and this article has been very popular) – lock functions. Leave a comment if there are other topics you’d like to see covered in this type of video. There’s one on the list that I’m SO EXCITED about…flush bolts and coordinators. What other hardware mysteries should we tackle?