Many years ago, while having a casual dinner at a local restaurant alone, a stranger came up to the bar sat down and ordered his dinner as well.
He was reading the local newspaper and wanted to strike up a conversation.
He was a contractor from out-of-state doing a project for a friend who owned a summer home on the lake.
He was looking for information about local lumber yards, typical costs of materials, potential subcontractors, plumbing and electrical supply centers or local hardware stores.
Trying to help him with his questions, a suggestion was made to ask in the code enforcement office for a list of local contractors or to pick one of the many business cards on the wall out in the hall.
This was met with a quick response of, “This place has a code office… way up here in the middle of nowhere?”
He made it quite clear he had no intention of getting building permits or inspections for anything.
Not wanting to get permits, he was convinced he was saving his client money and time, and besides “up here” the local inspector was most likely an ignorant woodchuck whose only goal was to get some money for the town.
He continued by elaborating on how tough codes were in his town; and clearly up here in the mountains he could build anything better than anyone around here.
We continued our conversation about building houses in other areas, of which we both had a fair amount of experience.
Comparing building techniques, material costs, customer relations, and code enforcement officer experiences, he still had no clue who he was talking to.
Although currently being the code enforcement officer, it was also true about previously being a home builder and past president of the Central New York Home Builders Association.
We could share real stories about past projects, problems, challenges, codes in general.
We had some pretty common ground.
It was very clear he did not like codes of any kind, and he disliked code enforcement officers even more.
Myself, having been around the business of codes for a very long time—and involved with the regulatory process within the state that administers all the codes—and then being a builder for many years… Well, this tends to provide a unique ability to see both sides.
He only thought he was talking to another builder.
When New York State adopted the first mandated Uniform Fire Prevention and Building Code back in 1984, it was an attempt to raise the bar of professionalism within the code enforcement world.
Requiring minimum training, the passing of a state exam and requiring continued education every year were a few of the fundamental concepts needed to make code enforcement a more professional and effective tool to promote building and life safety.
In many ways it has worked well across the state.
However, there is no doubt that it is not consistent everywhere.
We talked about different code officers, how they interpret various sections of the code, how they interact with contractors and homeowners good or bad, public officials and other regulatory agencies.
We both agreed that code officers should work hands on, in the construction industry for some time to be on the receiving end of enforcement.
We also agreed how architects and engineers should do the same.
And how some designs are almost impossible to accomplish based on the plans provided.
This builder did have a fair amount of experience under his belt, but he also had an ax to grind regarding code officials… he had some pretty difficult encounters.
It was clear he had no intention of getting a permit, because there was no one around this area who knew how to do things as good as he could.
And why should he spend a few hundred bucks to let some uneducated pawn of the local town take his money?
The entire time was an education all by itself.
But, dinner was finished and I had no desire to hang around the bar, so it was time to leave. So I said good night.
He asked quickly, “What is your name?”
All that could be done was to introduce myself, hand him my business card and say, “Hope to see you tomorrow… have a good night.”