58 members
58 members
87 members
182 members
169 members
Started this discussion. Last reply by Brian Arnold Jun 20, 2009.
Started this discussion. Last reply by Paul Shapiro Jul 5, 2009.
Started this discussion. Last reply by JOSEPH KOONCE Apr 26, 2009.
Added by Mike Walker
Posted on May 3, 2009 at 7:19pm — 16 Comments
Posted on February 11, 2009 at 6:56pm — 4 Comments
The login above DOES NOT provide access to Fire Engineering magazine archives. Please go here for our archives.
Our contributors' posts are not vetted by the Fire Engineering technical board, and reflect the views and opinions of the individual authors. Anyone is welcome to participate.
For vetted content, please go to www.fireengineering.com/issues.
We are excited to have you participate in our discussions and interactive forums. Before you begin posting, please take a moment to read our community policy page.
Be Alert for Spam
We actively monitor the community for spam, however some does slip through. Please use common sense and caution when clicking links. If you suspect you've been hit by spam, e-mail peter.prochilo@clarionevents.com.
Check out the most recent episode and schedule of UPCOMING PODCASTS
45 members
116 members
62 members
73 members
166 members
65 members
277 members
510 members
10 members
106 members
© 2024 Created by fireeng. Powered by
FE Home | Product Center | Training | Zones | Fire-EMS | Firefighting | Apparatus | Health/Safety | Leadership | Prevention | Rescue |
Comment Wall (32 comments)
You need to be a member of Fire Engineering Training Community to add comments!
Join Fire Engineering Training Community
I'll check it out often.
Stay Safe,
Dave
Go for it! I appreciate your efforts to pass on the info. Reading smoke should be as common as a motor vehicle size-up: Evalute traffic, number of cars involved, damage/stability, hazardous energy involvement, visible victim status, etc.
-Dave
What we've notice in many cases is that there are two things which can be great for progress but also great for "doing nothing", depending on the way you use it. These two things are the concept of "brother" and the documentation.
A brother is a man to who you can say "You're wrong" and who can say you the same. If you do "wrong", and you are not my "brother", I'll not tell you you're wrong, because it doesnt matter to me. When I tell my student that they must work a lot, because they are not "good", that's because I love them.
The bad use of "brother" is to say "you can't make criticism to a brother". because in that case, the brother can do bad things for years. And one day, you will be in front of his grave. The grave of a brother? No. Because when my brother do bad things, I'll tell him immediatly. I don't wait him to get an accident.
Documentation can also be used in a positive or negative way. You can use doc as a start point, to increase knowledge. This is a right way. But when the guys don't want things to change, they use the docs, to say "You can't do that, it's not in the doc!". This is the bad way.
Same tools. Two results. Not easy to use. :-)
Very best regards
Pierre-Louis
Thank you, you're the best...
Dave Mc.
We did have a fire the other day ( SFD )lots of smoke no vis fire. Heavy was first due and did a search ( took the can ). First due engine arrived a couple of min behind them. During their search they made the fire room and put out the contents fire with the can. Guys said it was starting to out of the room. This wouldn't have had happened a year ago. The guys had done some can fires and new what they could extinguish.
Had a rookie on the Engine ( first fire ) they met him at the door and burst his bubble.
View All Comments