'Shall' means do it. 'Should' means do it unless you can explain why in writing.
Codes and Standards Jokes
Clauses, editions, addenda and “it depends.” 67 jokes.
Mandatory appendix: the only appendix you can't have removed.
Code book humor is like a mandatory appendix: dry, well referenced, and nobody asked for it.
An addendum is the standard politely saying it learned something.
The vessel passed the hydrotest. The paperwork is still under pressure.
A cross-reference is the code's version of 'see me after class.'
Acceptance criteria: because 'looks good to me' doesn't have a table number.
An 'informative' appendix is the code's way of handing you a flashlight, not an order.
When two clauses disagree, the inspector doesn't flip a coin.
Show the Punchline
She writes a letter.
When two codes disagree about one weld, the only thing both will accept is a longer conversation.
Why did the inspector put the code book on the scale?
Show the Punchline
Somebody said the new edition carried more weight.
What do you get when you cross a code book with a set of sticky tabs?
Show the Punchline
An inspector who always lands on the right page.
Why did the Level III refuse to sign the weld as acceptable?
Show the Punchline
The procedure said 'as required.' She wanted to know by whom.
How do you know a clause has been interpreted correctly?
Show the Punchline
The committee wrote back.
Why did the specification and the code go to couples counseling?
Show the Punchline
They kept requiring different things of the same weld.
What does an inspector say when the spec contradicts the code?
Show the Punchline
'Please send that in writing, signed, and preferably before the shutdown.'
Why does the acceptance table have a footnote on every row?
Show the Punchline
It's the only way a code can say 'yes, but' in a grid.
Why did the addendum cross the road?
Show the Punchline
To amend the other side.
Why did the pipeline inspector keep her code book in a sealed bag?
Show the Punchline
It's the only thing in the truck that has to stay dry.
What's an engineer's favorite part of the code?
Show the Punchline
The part that says 'unless otherwise specified.'
The code says 'workmanlike appearance.' Nobody has defined it, but everybody has seen the opposite.
'As agreed between the parties' is the most reread sentence in any code book.
The engineer's spec adds requirements, the code adds exceptions, and the inspector adds sticky notes.
Code questions go to the Level III. Snack questions go to the new tech. Both know exactly where to look.
A thicker code book doesn't mean more problems. It means more tabs.
There are two kinds of inspectors: those who know their code book and those who know where it's kept.
The latest edition fixes everything the old edition got wrong. Unfortunately, the contract still cites the old one.
You might be a code nerd if you've ever said 'it depends on the edition' at a dinner party.
You might be a Level III if you've ever cited a clause in an argument with your spouse.
You might be an inspector if your code book has more tabs than pages.
You might be a welding inspector if you've ever flipped to the acceptance table before saying hello.
The inspector found a discontinuity and checked the code. Table 6.1: acceptable. The client, thrilled, asked, 'So it passes?' 'It's a discontinuity, not a defect.' 'But it's a flaw?' 'Everything is a flaw,' said the inspector. 'This one just fits in the table.'
The engineer phoned to say his spec was stricter than the code. 'Then I'll inspect to the spec,' said the inspector. 'But the spec only has half the acceptance criteria.' 'Then I'll use the code for the other half.' 'You can't mix them.' 'Then which one do you want?' There was a long silence, followed by a revised spec.
A new inspector asked which code applies. 'Whatever the contract cites,' said the mentor, 'down to the edition.' The new inspector wrote the edition on her clipboard, in her notebook and on a sticky note inside the code book. 'Good,' said the mentor. 'Now you're ready.'
Three inspectors argued over one clause for an hour. They finally agreed. Then the Level III arrived, read it, and said, 'Oh, that was superseded last year.' They've been quiet ever since.
Addendum (n.): The code's way of saying 'We improved it. Please check the effective date.'
Code Case (n.): An exception wearing a code number.
Scope (n.): The first paragraph of a standard, and the one that tells you whether the other four hundred pages apply.
Informative (adj.): Describes any code material nobody is required to follow and everybody is expected to know.
Knock knock.
Who's there?
Clause.
Clause who?
Show the Punchline
Clause the book gently. That's the current edition.
Knock knock.
Who's there?
Table.
Table who?
Show the Punchline
Table-ing this discussion until the next edition comes out.
Knock knock.
Who's there?
Shall.
Shall who?
Show the Punchline
Shall I come in, or should I? The code is unclear.
The clause said, 'For details, see B.'
B said, 'Table four will tell thee.'
Table four, with a grin,
Said, 'The answer's within,'
And that's how it ended for me.
Table six point one
says the weld is acceptable.
Then I read the notes.
Roses are red,
Violets are blue,
The code says one thing
And the contract says two.
A code book is the only book where the year on the cover matters more than the title.
An acceptance criteria table has no favorites: every indication gets the same row, the same column, and the same answer.
Ever notice the clause you need is never in the section you'd expect? It's always in the one nobody tabbed.
Nobody warns you that 'shall,' 'should' and 'may' will become the three most important words in your career.
Ever notice that the footnote under the acceptance table is the one line that always matters?
What do a code book and a level have in common?
Show the Punchline
Both keep the project straight.
I once received a one-line scope of work: 'Inspect the bridge.' It was the longest document I've ever read.
Scope of Work (n.): A short document that answers every question except the one you have on site.
Every refinery has a corrosion circuit map, and every inspector owns a favorite highlighter.
The Navy inspector reviewed the weld map with the shipyard supervisor. 'All of these are required?' asked the supervisor. 'Every one,' she said. 'Even this one in the forward void?' 'Especially that one.' The supervisor sighed, picked up a flashlight, and handed her the other one.
Somewhere under every old bridge is a 1960s weld that would like a word with the current code book.
The county engineer asked how the bridge inspection was going. The inspector arrived with a snooper truck, two flaggers, a lift operator and a six-page traffic plan. 'That's a lot of equipment,' said the engineer. 'Ma'am,' said the inspector, 'on a bridge, this is the light version.'
Ever notice the load rating is the one number everyone remembers, and the inspection behind it is the one thing nobody mentions?
Ever notice that the inspector who checks the revision letter before starting always seems to finish on the first try?
Rail inspectors have a standard answer for everything.
Show the Punchline
Four feet, eight and a half inches.
I read the new edition of the code book cover to cover. It's a real page turner, and I did turn every page.
What's the first thing a Level III checks in the new edition?
Show the Punchline
The revision summary, then the paragraph numbers, then the revision summary again.
The new edition is the old edition with one paragraph changed, and the Level III found it first.
New edition day:
sticky notes all find new homes.
Highlighter, ready.
Nobody warns you that the best part of a new edition is the revision summary on page one.
Knock knock.
Who's there?
Edition.
Edition who?
Show the Punchline
Edition to the old code book, you need the new one. Check your shelf.
The code book is the one document every inspector reads and marks up with sticky notes.
Also Touching on Codes and Standards
'It looks fine' is a wonderful opening line, and it has never once appeared in an acceptance table.
The light meter read half the level the procedure required. The inspector asked for a second lamp. It arrived by morning with an extension cord, a work order and a supervisor who had never seen a weld so well lit.
What's the difference between a discontinuity and a defect?
Show the Punchline
One acceptance criterion and a very awkward meeting.
Why did the crack file a complaint?
Show the Punchline
It felt it was being unfairly rejected.
A perfect weld is a myth. A weld with only acceptable discontinuities is a Tuesday.
Discontinuities are innocent until proven rejectable.
A crack is the discontinuity that never needs the acceptance table to be rejected.
You might be an inspector if you describe a messy room as "lots of relevant indications, no acceptance criteria."
The welder asked the inspector if the porosity was acceptable. "It's a discontinuity," said the inspector. "So it's fine?" "It's a discontinuity." "Is it a defect?" "Let me check the table." He checked. "It's a defect." "You said it was just a discontinuity." "It was," said the inspector, "before I read the table."
Defect (n.): A discontinuity that lost the argument with the acceptance criteria.
Said a discontinuity, with a sigh,
"I'm no defect, so please pass me by."
But the table said, "No,
You are too long, you know."
Now it's rejected. Goodbye.
Nobody warns you that half of inspection is drawing a map so someone else can find what you found.
I treat my renewal date like a discontinuity. I find it, document it and never let it become a defect.
There once was a Level III sage
Who had memorized every page.
When you asked her to rule,
She would say, calm and cool,
'It depends on the edition's age.'
Holiday lights are inspected more thoroughly than most welds. Someone holds every bulb up to the light, and nobody has an acceptance criterion.
The first-article part finally met the drawing.
Show the Punchline
They were within tolerance of each other.
First-Article Inspection (n.): The one part that gets looked at more closely than every part that follows combined.