Have you ever been reading through the code and come to a section that you just can’t understand? One of those code sections that you read, read it again, think about it, then re-read it. Only to still not understand what it is saying? I’ve been in this spot more than once. So, how do you get past it? What are some steps to understanding what you are reading?
Here are the four steps to understanding hard code sections:
- Annex information. Is there an asterisk by the code section (for NFPA codes and standards)? If so, refer to the annex for this code reference or section. Additionally, reading the code section before and after the problem section can help by providing context. If these sections have annex information, then review that, as well.?
- Other editions. Refer to past editions and future editions of the same code section or language. Sometimes the same concept is stated or explained another way in other editions. Other editions may make the concept to be more clearly understood.
- Handbooks. Many codes have handbooks that are published by the code organization, or even outside publishers. Refer to the code section in the related handbook for potential commentary, explanation, or illustration, for clarity.
- Google search. Finally, do a Google search of key phrases from the code section, the code reference, or copy and paste the entire code section into the search bar. This may produce other resources such as articles, blog posts, social media comments, and other items that may provide clarity and direction for understanding.
How do you comprehend hard code sections??
Contact me at, www.aaronj.org.
![Hard Code Sections [how to understand them]](https://media.licdn.com/dms/image/v2/C4D12AQFVnfmLGq54eg/article-cover_image-shrink_720_1280/article-cover_image-shrink_720_1280/0/1638792129709?e=2147483647&v=beta&t=4lnpyXBtmmumL8YI8P4Oyrk6d4zAITeSjymy3XY3VQs)
Fire Protection Manager
3 年Excellent tips. Annexes, corresponding handbooks and published public input have always been my go to.
Senior Code Specialist at The FPI Consortium
3 年Assuming the code section is a newer one, I find the public comment reports extremely useful. They give you the reasoning that the proponent had for why the change was needed, and the reasoning for why the committee accepted it. But I will admit, the handbooks are my best friend!
President, Westhill Group, Inc.
3 年I want that logo.
COO at MountainLogic
3 年-Be able to restate the scope of section in your own words; -Flow chart the section; -Put pencil to paper and sketch out model implications on buildings or uses section applies to; -Then state how this section is intended to provide some improvement. Add notes to self about in what situations you might think it too restrictive or that it provides too little mitigation for situation or process section is designed for. Write, sketch, or flowchart an alternative that you find better. Of course better has quite a few directions of its own. Best.
Chief Fire Officer-QatarEnergy
3 年Good advice Aaron, I always try and think what the intent of the section is as well, what was the author intending when writing that section??