In January, suppression expert Bob Upson presented a webinar on frequently asked questions concerning standpipe systems out of NFPA 14 with NFSA's online teaching platform. If you work with standpipe systems regularly, I'd highly recommend it. 

One of the topics he discussed was a brief history of how both the International Building Code (IBC) and NFPA 14 (Standard for the Installation of Standpipe and Hose Systems) have changed over time between requiring standpipe hose connections on intermediate floor-level landings to floor-level landings.

By floor-level landings, typically you would have a hose connection 3-5 feet above the floor level immediately at the landing upon entering an exit stair.

To get to a hose connection on an intermediate-level landing, you would enter the stair and walk down a single flight of stairs to get to the next landing (typically opposite of the main floor level landing).

I was interested in exploring this code history in a little more detail - so below is a compilation of the last 20 years of the IBC and NFPA 14 and where standpipe hose connections have been required by each code edition within exit stairs.

Hope your week in fire protection is going well.

Standpipes within stairs can be an important item to coordinate with the project architect, as the fix for the lack of coordination can be extremely difficult to accomplish in the field. This week I'm breaking down an enlarged floor plan detail for a standpipe hose connection within a stairwell.

Avoiding the Egress Path
The image above shows the clear span that's required to maintain clearance. How do you know the radius of this line? Just take the width of the stair, set the center of your arc to the edge of the stair, and draw your arc from one end of the stair to the other. This is an extension of the required egress of the stair to turn on the landing and move the other direction.

Is it possible and allowed to locate small parts of the hose connection within this clear span? There could be a basis for it. 

In design I try to avoid any controversy by locating both the standpipe and those valve entirely outside of this egress path. Doing so may require a little extra space on the landing, but it is far better than finding out after the stair is constructed that you're short on space.

Structural Conflicts
A traditional new-construction stair will likely have support for the stairwell landing incorporated into the stair enclosure, or contain a beam across the landing where the landing meets the beginning of the stairs if it's a concrete stair. These new builds don't present too much of a challenge to coordinate with structure.

However, for retrofits or stairs that do not simply jog back and forth, beware of beams that could run where you'd like to locate the standpipe connections. Core drilling a 4-inch to 10-inch hole through a concrete beam will not make you good friends with the structural engineer.

Handle Clearance
The hose connection is required to have 3-inches of clearance on all sides of the handle. (NFPA 14 2013-19 4.7.5)

​It's not enough to just stick your hand and start turning the valve, we have to remember that it's the firefighter's thermally insulated and rigid gloves that must turn the hose valve while the building is literally on fire. Giving 3-inches of clearance just feels like a minimally-nice gesture to thank your local first responder.

Drain Riser
Lastly, don't forget about the drain riser.

If the standpipe includes pressure-reducing valves, these valves require testing and it's required to have a way to connect directly to an oversized drain riser that can handle the testing. This can be done with capped outlets on the drain riser that can accept a hose connection for testing.

NFPA 14 provides guidance on sizing the drain riser in this scenario: 3-inch drain riser for 2-1/2-inch pressure reducing devices, a 2-inch riser for 1-1/2-inch pressure reducing devices, or sized large enough to handle the full flow from the largest pressure reducing device. (NFPA 14 20037.12, 2007-19 7.11.1)

Know someone who might be interested in content like this? Please forward them a link.

Want to get weekly articles like this yourself? Subscribe here.

Hope your week is going very well.

This week I'd like to open a short series on standpipes. Today's article is a basic overview of some basic requirements associated with standpipes used for fire suppression.

Purpose
Standpipes are used to support manual firefighting efforts by delivering water to hard-to-reach areas of a building. The intent of a standpipe system is to avoid having to distribute and connect hundreds of feet of hose for a single interior attack by firefighters.

Hard-to-reach areas of a building aren't confined to one direction. Buildings which are very tall (highrises) or are deep underground, or are very wide by nature could all have portions of the building which would be difficult to reach.

Applicable Codes & Standards
In the US, the International Building Code (IBC) and International Fire Code (IFC) are often the first stop for standpipe requirements. While the two codes mirror each other, the International Building Code requires standpipes based on:

• height (a story located more than 30 feet above the lowest level of fire department access, or 30 feet below the highest level of fire department access) (see IBC Section 905.3.1)
• unsprinklered assembly occupancies (see IBC Section 905.3.2)
• covered and open mall buildings (see IBC Section 905.3.3)
• stages (see IBC Section 905.3.4)
• underground buildings (see IBC Section 905.3.5)
• helistops and heliports (see IBC Section 905.3.6)
• marinas and boatyards (see IBC Section 905.3.7)
• rooftop gardens and landscaped roofs (see IBC Section 905.3.8)

Once it has been determined whether a standpipe system is required or not, the IBC and IFC defer to NFPA 14 to prescribe how the system is to be installed.

Class of Standpipes
Standpipes can be classified in several areas. The first is the class of standpipe, which relates directly to the hose connection type and the intended user. Based on 1-1/2 inch hose failures and the associated testing that goes along with them, 1-1/2 inch hose stations are much less common today.

I've found many situations with sprinklered buildings where hose stations have been removed as they are no longer required and are a burden for testing and maintenance. Here are the standpipe classifications, with Class I being by far the most common in the US today:

• Class I: provides 2-1/2 inch (64 mm) hose connections for fire department and trained use.
• Class II: provides 1-1/2 inch (38 mm) hose stations to supply for building occupants or initial fire department response
• Class III: provides 1-1/2 inch (38 mm) hose stations for building occupants and 2-1/2 inch (64 mm) hose connections for fire department and trained use

Types of Standpipe
The other defining description for standpipe is when water is delivered, and at what relative pressure. Types of standpipes include:

• Automatic dry: normally filled with pressurized air where water is delivered automatically when a standpipe hose cap is removed. The water, when delivered, is capable of supplying the system demand.
• Automatic wet: normally filled with water capable of supplying the system demand automatically.
• Manual dry: normally filled with air and without a permanent water supply. Water is required from a pumper truck in order to meet system demand.
• Manual wet: normally filled with water that is not at a pressure capable of supplying the system demand. Manual wet systems require  water to be pressurized by a fire department pump in order to meet system demand.

Components of a Vertical Standpipe
Standpipes are not always vertical standpipes, but for multi-story buildings they are the most prevalent and are the topic of discussion this week.

Flexible Coupling

• Purpose: Flexible couplings are included near floor levels to prevent catastrophic damage to the suppression system from the building structure while the building structure is moving in an earthquake. Flexible couplings allow the vertical pipe within a standpipe (or sprinkler system) to tolerate the horizontal building movement and still stay connected.
• Where Required: Within 12 inches above and 24 inches below floor level in multi-story buildings. [NFPA 13 2002-16 9.3.2.3(2), 2019 18.2.3]
• When Required: When the building requires seismic protection (seismic design category C, D, E, or F). Couplings are also provided at each floor level (often just above the floor level) to aid in installation.

Isolation Valve

• Purpose: Standpipe isolation valves allow shutdown of a single standpipe without interrupting the water supply to other vertical standpipes. This can play an important role with maintenance, repair, modification, or during active firefighting scenarios.
• Where Required: Isolation valves are required on all standpipes (including dry standpipes). [NFPA 14 2003 6.2.2, 2007-19 6.3.2]

Penetration Clearance

• Purpose: Clearance around floor penetrations are important for seismic bracing, again to prevent damage to the system from the building structure during an earthquake.
• Size: The diameter of the hole or sleeve must be 2-inches larger for pipes 1 to 3-inches in diameter, or 4-inches larger than the pipe for pipe 4-inches or larger in diameter. [NFPA 13 2002-16 9.3.4.2 and 9.3.4.3, 2019 18.4.2 and 18.4.3]
• Where Required: Where pipe passes through platforms, foundations, walls or floors, except where flexible couplings are located within 1-foot of each side of the penetration. [NFPA 13 2002-16 9.3.4.5, 2019 18.4.5]

Pressure Gauge

• Size: Not smaller than ¼-inch (6 mm). [NFPA 14 2003 5.6.1, 2007-19 5.5.1]
• Where Required: For standpipes, a pressure gauge is required at the top of each standpipe. [NFPA 14 2003 5.6.1, 2007-19 5.5.1]

Riser Clamp

• Purpose: Riser clamps are used to provide support to vertical pipe.
• Where Required: Within 24-inches (610 mm) of the centerline of the riser, to support the riser horizontally. In multi-story buildings, riser supports are required at the lowest level, at each alternate level, above and below offsets, and at the top of the riser. [NFPA 13 2002 9.2.5.3.1, 2007-16 9.2.5.4.1, 2019 17.4.5.4.1] Support above the lowest level to prevent movement upward when flexible fittings are used. [NFPA 13 2002 9.2.5.3.2, 2007-16 9.2.5.4.2, 2019 17.4.5.4.2]

Standpipe Hose Connections

• Purpose: To provide a point of connection for firefighters to connect hoses and get water to manually fight the fire.
• Where Located: At 3-feet (0.9 m) to 5-feet (1.5 m) above floor level. [NFPA 14 2003 7.3.1, 2007-19 7.3.1.1]
• Where Required: We’ll explore this in greater detail in the articles to come. There's volumes of information about these requirements, but for reference be sure to check NFPA 14 2003-19 7.3.2-7.3.4 and IFC 905.4-905.6.

Want to follow the rest of this series, or know someone who might be interested? Subscribe here.

I'm excited to announce a new addition to the Toolkit that has been in development for a long time - the NFPA 13 Edition Translator.

2019 Changes

With the major restructuring changes in the 2019 Edition of NFPA 13 - it has been difficult for me to flip straight to the content I'm used to doing. From the feedback I've heard I'm not alone on that learning curve.

As a result, a couple weeks ago I released the first version of the translator, which takes any numerical section from the 2016 or 2019 edition, and returns the matching section from the opposite edition.

Full Tool Now Available

This full version is quite the powerhouse. With over 130 hours of research included, it can now take any numerical section from any edition of NFPA 13 from 1999 through the 2019 edition, and returns the matching section throughout it's history.

Why?

Why could this be helpful? If you work across multiple jurisdictions or your local jurisdiction just updated to a new edition of NFPA 13, the shift in organization can be frustrating. 

If you use the free versions of NFPA 13 that are supported by NFPA, then this tool could help you quickly navigate equivalent sections.

Probably the most common use I have is finding the back-history of where a section first appeared and where to look for it in past editions. This comes up occasionally for projects when there's disagreement about a particular section of code and searching for the back-history and any clarifications in future editions is very helpful.

Available Now

If you're a Toolkit subscriber, you can download the latest version of the Toolkit, including this edition translator, here. 

I've made it easier to download updates for Toolkit users. You can access the latest version and quickly download it at www.meyerfire.com/download. No sign in required.

​Find this interesting? Consider sending to a friend or colleague who might find it helpful.

Following the interest and popularity of the ceiling-mounted obstructions tool, I've been working on some new tools that cover other obstruction situations which we often encounter. This week's post is a quick demo of the progress for one of these obstruction situations, which is the soffit against a wall condition.

One way NFPA 13 addresses soffits is by shifting a sprinkler away from the wall, which allows water from the sprinkler to throw below the soffit. With only two input values this tool will quickly determine the horizontal distance a sprinkler needs to be located away from a soffit in order to meet NFPA 13 Figure 8.6.5.1.2(b) (2016 Edition).

Give this demo tool a quick try and comment below with any concepts you'd like to see added to this tool or the site. Thanks in advance!
​

When I was six years old, I came home from school unexpectedly excited one day.

I ran up our driveway, pushed wide the door and yelled to my mom.

“You won’t believe it! There’s this place at school where you can go through shelves and shelves of books and pick out anyone you want – 
and it’s free! They call it a library.”

It wasn’t one of my mom’s proudest parenting moments, but in our house, we never pretended to be great readers… or apparently even pretended to introduce kids to a library.

I guess I’ll just come out and say it… Both of my parents are accountants.

Now, I know what you’re thinking, and yes, the accountants are where my well-rounded sense of humor comes from.

But there’s another big benefit to having parents as accountants – 
and it’s having a love for spreadsheets.

I’m not sure if little excel formulas naturally run through my veins or whether it was every family calendar my parents ever created, but one way or another I thoroughly appreciate the power a spreadsheet has.

Even if your parents are not both CPAs, there’s a place for Microsoft Excel in your engineering life.

For one, Microsoft Excel is not called
the “Swiss Army Knife of Software” for naught. Excel is a blank canvas for any calculation you need to make. You can quickly create and repeat repetitive calculations to speed up and organize your workflow. You can complete reports, forms, create charts, tables, organize content, or use any of a myriad of highly powerful tools.

Here are a few of my most often used formulas:
​

• =concatenate(cell,”psi")      Will combine strings from any combination of cells or text, in this case cell A1 and psi
• =lookup(cell,range)             Will lookup a value in a cell against a table. Great for quick reference calculators.
• =vlookup(cell,range,column number,match)    Will lookup a value in a table and return adjacent results
• =if(test,value if true,value if false)     Determines a logical test and returns different values on the outcome.
• =countif(range,value)          Will count specific items in a list if they match criteria.

That’s pretty much all of my secret sauce. About 95% of the tools created combine those formulas alongside mathematical operators (like max(), min(), sin(), sqrt(), etc.).
​
One of the best parts about using Excel is that you may already have access to it. If your company has a Microsoft Office suite (or what’s now their subscription model with Office 365), you already have access to these tools.

Creating helpful resources is what we’re all about, and Excel is the epitome of giving you, the rockstar designer or engineer, the ability to create and flourish with the tools you need. 

You didn’t get into the industry to do poor, sloppy work. You came here to help save lives. We shouldn’t have to wait for programmers to create the daily tools we need to do great work. Excel is one way you can organize and validate the great work you do.

There came a point near the end of my undergraduate work and at the beginning of graduate school where I realized I needed to create a clean, organized method to show details within calculations. The method I slowly developed needed a single logic path, had to be easy to follow, would thoroughly explain the process, and had to allow the easy repetition of the work.

What’s resulted is the standard format that’s used in the PE Prep Guide and on many of the tools you’ll see around this site. Concepts are researched, painstakingly created, tested, refined, tested, refined, beta tested, and refined more.
​

If you’ve followed the blog for a while, you already know the blog, daily forum, and even the PE prep materials are all created to help foster discussion that leads to shared expertise and knowledge.

Outside of a few major players and organizations, the fire protection industry is comprised of thousands of thousands of small outfits that welcome this shared expertise. Our industry thrives on the contributions from a wide spread of individual parties.

​Don’t let me or anyone else douse your enthusiasm to create resources that improve your ability to impact the industry. 

Keep on keepin’ on. 

​Oh and remember to take your kids to the library. 

Looking for an opportunity to turn a basic concept into a controversial one on a project? Great! This week I'm exploring the quick-response remote area reduction that's provided in NFPA 13.

Suppress Early, Suppress Less
The concept behind reducing the calculated hydraulically remote area in a fire sprinkler system is entirely based on fighting a smaller fire earlier in the development of the fire.

There's a handful of factors that contribute to the timing of sprinkler response (a good future discussion), which include the thermal sensitivity, sprinkler temperature rating, distance of sprinklers relative to the ceiling, sprinkler spacing, ceiling height, and dynamics of the fire itself.

The reduction in the hydraulically remote area is based upon comparative tests of quick-response against standard-response spray sprinklers. According to the NFPA 13 handbook, the tests demonstrated that the earlier the water is applied to the fire, the smaller the fire and ultimately the less number of sprinklers needed to activate.

Not Universally Accepted
While the remote area reduction has been included in NFPA 13 for years, it's not universally accepted. Many engineer specifications don't allow the reduction, and design standards for major organizations such as the Department of Defense (UFC 3-600-01) don't permit it either.

Why not accept the remote area reduction, if NFPA 13 includes it? Like other elements in hydraulic design for fire sprinkler systems, not using the remote area reduction provides an additional safety factor to the system.

Additionally, since the quantity of sprinklers relates to the quantity of water flowing in the system, main sizes are directly impacted by using or not using the quick response area reduction. Building owners may opt to not want to reduce the remote area to preserve reasonable (larger) main sizes and give themselves flexibility on building modifications and sprinkler system changes in the future.

Quick-Response Area Reduction Calculator
This quick calculator is in part a checklist of prerequisites to reduce the remote area on a fire sprinkler system, in part a method of showing your work, and in part a quick calculator on determining your final remote area size. Don't see it below? Give it a try here.
​

This site is all about helping you shine in fire protection. Want these weekly tools & articles? Subscribe here, for free.

A little earlier than this time last year I wrote an article covering how NFPA 13 addresses sprinkler protection underneath canopies, overhangs, and exterior projections on buildings. It ended up as one of my favorites and I've had good feedback on it as well.

With the big changes in re-organization to the 2019 Edition of NFPA 13, it is only appropriate to make a few updates to the flowchart and get it in your hands so you can do what you do best.
​

Here's a link to the original article in full. If you haven't read it, it might be worth a few minutes here:
​

If you know someone who might find this useful, please send this to them and let them know they can subscribe to these free weekly tools & resources here.

Unless you're tuned in as an AHJ yourself, you've likely made a few "code calls" to a code authority and asked a litany of questions to make sure your project's design meets the local requirements.

I'm not even sure if the term "code call" is a common term, but I've heard it enough that I suspect you already know what I'm talking about regardless of where you call home.

I enjoy this process now, but I didn't always. Fresh out of school I'm pretty sure I was visibly shaking the time I first made a code call. I was sure that within seconds my cover would be blown and it would be all too obvious that I had no idea what I was talking about. Despite my awkwardness (I make a good engineer, right??) nothing went sour and since then I've slowly learned and repeated many many times.

There was even one of my favorite code calls that I made about an elementary school to coordinate local fire alarm requirements. It was only right after the call late on a Friday afternoon that I found out that the fire marshal I just spoke with was hired onto our team and was starting the following Monday. They say fire protection is a small world, right? He turned out to be one of the most knowledgeable people I know and one of my favorite people to work alongside. 

The Joys & Pains of Code Calls

Code calls also come in many different flavors.

Sometimes I'm just shocked by how friendly and helpful code authorities are. I once made a call at 15 minutes till 5pm on a Friday to a small town in Arkansas, thinking I would just leave a voicemail. After my questions, I asked if the department conducted flow tests, and while he said they did, he apologized that because of a prior commitment he couldn't do it then but would be happy to do it first thing Monday morning. I almost fell out of my chair. Very helpful and caring people in this field.

On the contrary, sometimes the hardest part about a code call is just finding the right person to speak with who is actually responsible for plan review of fire protection systems and getting a few minutes of their time. Not to pick on New York City because I love the people there and speak with a handful of you regularly, but if you're trying to get a hold of someone to verify or coordinate a few particulars of your system... well... good luck! Maybe it's because they knew I can't stand the Yankees.

I also sometimes get AHJs who simply say all they do is 'per code' and they aren't interested in talking specifics. The whole point of the call is filling in the gaps where a code or standard does not direct but rather defers decisions to the AHJ.

Want a siamese fire department connection with national thread, or a Storz-type? Either way is code compliant. As an engineer I can make either way work.

Is a wall-mounted FDC permissible, or does it need to be freestanding? Either location is compliant, but NFPA 13 says the location needs to be coordinated with the AHJ. 

The Cheatsheet

What I've gathered and refined over hundreds of code calls is my cheatsheet I currently use today. Just like the design cheatsheet, if you're using the Toolkit you can quickly highlight categories for your record keeping.

What's even better about this tool, though, is that you can quickly fill in the content (while on the call) and then right after save as a PDF and email to the AHJ themselves. Want them to have a record of the call and a quick way to verify your notes? Great! You now have a logged code call and the AHJ has an opportunity to review your notes.

The process of calling, taking notes, and composing the email used to take close to an hour total. This tool alone brings that total time to about 15-20 minutes. That's three-quarters of an hour you could save on every job you make the call! 

A Radical Big-Picture Concept

One of my longer big-picture ideas to help the industry is to beta test and, if successful, open up a larger code-call database. I envision this as a database that brings designers and code authorities together to make local requirements clear and help jurisdictions get installations that reflect their preferences and mandates.

Want to know what hydraulic safety factor is required for sprinkler systems in Springfield, Illinois? Great - a quick query in the database reveals that and a clean list of other local requirements. 

Want to know what type and location for FDC's that Tucson, Arizona requires? Great, we'd have that too.

This would clearly have a huge value for designers and engineers - but what I'm really curious about is how to incentivize code authorities to take the survey or help us populate the database. If you're an AHJ, email me (jdmeyer@meyerfire.com) or comment below about whether you'd be open to the idea of making your local requirements public in a database. 

I would have to think that AHJ input would only help local authorities get installations that match their needs - but I also know that getting action out of anyone is only possible with mutual benefit and sometimes incentives.

Just like the Design Cheatsheet posted a couple weeks ago, this form is integrated into the updated version of the MeyerFire Toolkit ready for download today. Below is a blank and filled-in template.

​If you're already a Toolkit user, you can download the code call cheatsheet today by logging in here. If you're not using the Toolkit, you might consider joining in on what's quickly becoming what some consider the best tool for fire sprinkler design under $200. See more about it here.

The Questions on My List

The current code call checklist I use today has had items added and scratched over years of finding out what's important and what questions always get the same answers. 

​That being said, there's no real one defined list that matches everyone's preferences. What questions do you ask that you feel are important to the design that's not explicit in code? Comment below.

Join the Cause

​Our line of work in helping save lives and property is extremely important, but you already know that. This site is built to help you excel in fire protection. If you're not already subscribed to these free weekly resources & articles, you can do so here for free.

I had several long standing global concerns when I was in grade school. 

It wasn't general anxiety or depression-related, but I certainly felt as though the weight of worldwide issues hung squarely on my small shoulders.

At the time in school there was a major focus on the environment (I would imagine there likely still is now). It wasn't just a hard-sell on earth day, it was the disappearance of rain forests, erosion due to overbuilding, overpopulation, oil spills, our reluctance to recycle, and the overzealous use of oil that would undoubtedly cause our planet irrevocable damage. It was our generation's tasks to make right what generations before had begun.

The gravity of the concern didn't feel just environmental either. 

New media opened the front door to war, disease, and a myriad of reasons to be pessimistic about the future and the world our kids will someday inherit. 

Now years later, as a father, I've heard similar sentiments prevail; "how could someone bring a child into the world today?" "I can't imagine how to parent with all the (fill in the blank) going on today." "Will there even be X around when our kids are old?" 

I'm not going to pretend that everything is sunshine and roses for everyone. There are major geopolitical issues and wars and famine and poverty and disease. A great day for me could also be the worst day for someone else.

What I am hear to say is that when you adjust your focus from the immediate present and look out a just little more distant - there is so much promise in the world. And by so much promise I mean that the planet is getting healthier, cleaner, and the quality of human life is improving in ways that we've never seen before in human history.

There has actually never been a better time to bring a child into the world.

In Peter Diamandis and Steven Kotler's 2012 bestseller "Abundance: The Future is Better Than You Think", an author and engineer review historical data and trends that show how technology is achieving exponential improvements in computing, energy, and medicine.

​These independent technology-based innovations have and will continue to drive major improvements to clean water access, food, energy, health care, education, and other facets of a first world standard of living for the planet's future nine billion people.

Not only does mainstream media not cover the positive trends in the world today, but the future of our planet is looking more urbanized, education, cleaner, and healthier.

Speaking of population, the United Nations recently released a DESA report projecting nearly 10 billion people in 2050 and over 11.2 billion people in 2100. Since this latest update there's been fairly widespread disagreement about these figures, with many researchers speaking out out about the projections that hinge on one major flaw: population growth rates are declining. Some countries have already peaked in population and are now in decline without immigration. Many expect that we, as a planet, will never reach more than 10 billion people.

This isn't news to you if you live in Europe or Japan, of course, but in the U.S. many of us seem unaware of this major global trend. Research shows that with urbanization and better education, couples have less children. This speaks to major positive impacts in using less resources and shaping a cleaner planet in the future.

Trends in Fire Protection
​
That's great Joe, but what does this have to do with fire protection?

First, as is my underlying theme in the whole website - engineering is going to save the world. I'm sure my wife would also suggest that scientists deserve some credit too, but this isn't her blog.

Second, don't be discouraged if you feel that the quality of our line of work is in freefall, that no one is entering the industry, or that we've lost all sense of pride in what we do. Big-picture trends in fire protection are very positive, with death rates due to fire steadily decreasing per capita over the last century. The unrelenting overall trend is that we are doing something right as fewer people per capita are dying now from building fires.

​Fire fatalities have been and continue to decrease with advancements in code adherence, our knowledge of fire protection, and shared education of the subject. Just the last 30 years across Europe and the US there's been major improvements in fire safety:
​

Third, if you've ever felt similarly barraged by the negativity in the media or fears that we're only one step away from global catastrophe, I would wholeheartedly encourage you to read or listen to the book Abundance: The Future is Better Than You Think.

There's no summary that I could put together that I feel would do the book justice.

Of the fifty-plus books I read last year this was without-a-doubt the most impactful. [On a side note, if you're wondering how I average 50 books a year - I cheat and listen on audible.com. You can actually get the book Abundance and another book, for free, with a free trial here]

If you've read Abundance, comment below on your impression. If not, I'd highly encourage you to read it and let me know what you think (shoot me an email at jdmeyer@meyerfire.com). I promise the read will be worth your time.

Similar Articles

If you've enjoyed this article, consider subscribing to these free weekly posts here.

Here's a few other book reviews:
Chicago Death Trap: The Iroquois Theatre Fire of 1903
Fahrenheit 451 & The Thirst For Knowledge
Triangle: The FIre That Changed America

References

Diamandis, Peter H. Abundance: the Future Is Better than You Think. Simon & Schuster, 2015.
​
Fire Death Rate Trends: An International Perspective. FEMA, July 2011, www.usfa.fema.gov/downloads/pdf/statistics/v12i8.pdf.

United Nations Population Division | Department of Economic and Social Affairs. United Nations, www.un.org/en/development/desa/population/publications/trends/population-prospects.asp.