TPMCafe
« What's New... | Home | WE WIN!- White House Reinstates Davis-Bacon »

My Kingdom for a Conjunction

user-pic

I'll eagerly await Mickey Kaus's take on George W. Bush's betrayal of neoliberalism as he backs down on the Davis-Bacon issue. Until then, let's talk semantics:

The administration contended the move would reduce rebuilding costs and help open opportunities to minority-owned companies, but unions and other critics said it would result in lower pay for workers.

But of course insofar as suspending Davis-Bacon would, in fact, reduce building costs it would do so by offering workers lower pay. That's the whole idea. "The administration contended the move would reduce building costs . . . , and unions and other critics said it would result in lower pays for workers." On the other hand, as they taught me in QR-22, "and" and "but" are logically equivalent. For all x and all y, "x and y" is true if and only if "x but y" is true. In the real world, however, "and" and "but" are often regarded as something akin to opposites, which became the source of vicious controversy during the editing of "The Incompetence Dodge".


12 Comments

| Leave a comment

I won't answer for Kaus of course, but I think his first response would be that lower wages for workers were not the only or even the primary means of reducing building costs.  Rather, as several Kausfiles correspondents noted, the administrative burden of complying with Davis Bacon -- the forms, certifications, etc. -- are apprently the real driver of increased costs.  I seem to recall some claims that wages were most often not different in private vs. D-B jobs.  Of course, there is some logic to this since, as I understand D-B, it requires payment of the "prevailing wage."  Since the market theoretically determines the prevailing wage, it is the certification process that would be the real cost to a contractor.  That said, clearly the government has historically approved prevailing wages that were on the optimistic side (from the employees' perspective) in many cases, so I don't doubt that there will be some jobs affected by this decision.

When facts are used in "and" or "but" contexts like these, wouldn't the different meanings of the conjunctions be more relevant to the implied statement?
That is, (x and y) might equal (x but y), but [(x; x implies a) and (y; y implies not a)] is a fallacy, and not equivalent to [(x; x implies a) but (y; y implies not a)], which is valid.  So in this case the implied a would be "this makes things better for everybody" and not a would be "but it makes things worse for a large number of people", so the first case cannot be true.  Since it's basically a conversational (rhetorical?) exchange, the fact that the negation refers to the results of the non-contradictory events, rather than the events themselves, is implicit.

Yes, 'and' and 'but' are logically equivalent.  The difference between 'A and B' and 'A but B' is that 'but' suggests that A and B don't exactly reinforce each other in making whatever point is being made.

For instance, "Brad Basher hit 43 home runs in 2005, but he had only 72 RBI."  My fictitious slugger hit 43 dingers AND batted in 72 runs, but it's the BUT that points out that he should have had a lot more ribbies with those 43 homers. 

Or, "Brad was a good thing for his team...OK, maybe not so good."

Same with the Davis-Bacon sentence: "Suspending Davis-Bacon would be good...OK, maybe not so good." 

The problem here is that, in both of the above examples, there's no implication that A and B are related, whether or not they're working at cross purposes.  But in the Davis-Bacon example, their connection is the real point:the unions are saying B=>A.  That's what's missing from the sentence; screw the ands and buts.

How the sentence really should have been structured: "The administration contended the move would reduce rebuilding costs and help open opportunities to minority-owned companies, but unions and other critics said it would do so by lowering pay for workers."

The Labor Lawyer's remarks are spot on. Matt is out of his depth here.

Matthew also ignores that the following sentence is just plain wrong:

But of course insofar as suspending Davis-Bacon would, in fact, reduce building costs it would do so by offering workers lower pay.

Kaus presented evidence that workers' pay in the Gulf Coast is actually higher now than it was prior to the storm and higher than the Davis-Bacon "prevailing wage".

So, while the left thinks that the Davis-Bacon suspension was a "gulf Coast Wage Cut", in actuality, there was a "Gulf Coast Wage Rise."

Moreover, since wages were already above the D-B prevailing levels, D-B itself had nothing to do with increasing wages, and thus every dime spent on compliance with D-B is a waste.

However, I would be interested in the great "but" controvery Matthew hints at in the final sentence.  Looking over the linked article, I can't figure out the contrversial "but", although I do note that far too many sentences begin with the word "But".  I was taught that you shouldn't begin a sentence with a conjunction, but apparently Matthew and his co-author never learned that lesson.

That lesson is stupid, just like the "no split infinitives" lesson and the "no ending sentences with prepositions" lesson. For those who value arbitrary rules over quality of expression.

In the next installment of this gripping narrative, when asked if he would like vanilla or chocolate ice cream, our hero replies, "Yes!"

I vaguely remember from a long-ago course that touched on computational linguistics that these kinds of issues can be thought of in terms of pragmatics rather than semantics, but my memory might be completely off.

In any case, people often find formal logical difficult; after all, the predicate calculus (logic with quantification) wasn't even developed until the late 1800s.

I'm sorry Matt, I have to ask---did you watch Schoolhouse Rock as a kid? I'm guessing you were too young, but perhaps NYC public TV had resources mine did not. Did anyone else have Conjunction Junction turned on in their head when reading this blog?

Labor Lawyer,
I wanted to clear up some misconceptions surrounding the "certified payroll" requirement. The D-B payroll standards require that 1) record of work hours be kept 2)employees be paid weekly 3)ees be classified (trade designated) and paid at that rate.

There are several software programs designed specifically for these types of payroll, but it can easily be done with a standard payroll format.

 All businesses (with minimal exceptions) in the United States are required to keep record of employee pay and hours. This applies almost uniformally to the construction industry, regardless of private or public works.

With the exception of classification breakdowns, all information required in a certified payroll is standard for any business in the U.S. that does business legally.  "Certified" refers to the sworn statement by the company head or payment officer that ees have actually been paid as listed in the payroll.  I would hope this promise of truthfulness wouldn't be an excessive burden.

The extra time taken to designate a classification is also minimal if doing business legitimately; Electricians are electricians, Sheet metal workers, are sheet metal, etc. It's very rare that legit businesses have no clue what there workers do all day.

My experience in labor law enforcement, (which includes D-B), tells me than when contactors complain about the "excessive paperwork", it usually flags a situation where their labor payment system is not at all  professional, regular nor dependable, hence the extra work in (illegally) fabricating reports for government oversight.

Reputable and professional contractors are already keeping the records that are required under Davis-Bacon, and very minimal additional administrative work (ie. photo copying, mailing to contracting agency) is required.
SEC62:

I appreciate that your enforcement experience tells you these administrative issues should be minor for most construction companies.  On the other hand, my experience representing employers tells me that what may be "very minimal" in the eyes of someone in the enforcement business may be quite different to the actual employer.

First, yes all non-exempt (under FLSA) employees must be paid properly and have their hours recorded, regardless of D-B -- that's not the issue.  Nor is signing the certification.  In my view, the question is:  Is determining who qualifies for which official government job classification as easy as you say it is. 

You write that "Electricians are electricians, Sheet metal workers, are sheet metal, etc. It's very rare that legit businesses have no clue what there workers do all day."  That is simply a red herring.  You may know exactly what your employee does but either (a) not be able to fit him/her into the official job clasification; or (b) be forced to "upgrade" him/her to prevent the risk of a finding that you violated the rules.  For example, on a non-D-B job you may hire a laborer who moves beams, hauls concrete -- whatever -- most of the day but when the electrician needs him, he assists with the wiring.  Where should he go?  And if you say "electrician" remember that may mean he loses his job because we can't afford to pay laborers electrician rates.  Frankly, the permutations are endless -- it's just not true that everyone fits neatly into some government approved box. 

So, as I understand it, there really is a considerable administrative cost burden to taking on a D-B job.  This results in yet another advantage to the Haliburton types (i.e, the big guys who can absorb this stuff and/or those who do D-B jobs all the time).  My point is that D-B does not appear increase the wages of workers (other than in a few cases where the worker is probably being overpaid) and, back to the original post, I think it's certainly not logically required that workers wages go up in order for D-B to result in increased construction costs.

Labor lawyer:

Touche in identifying the classification process as the (perceived) administrative roadblock for small and inexperienced government contractors that can increase their costs. 

Off course I will allow that it is not a neat little box for all workers, but please don't tell me that a typical sub's scope of work for his people is so confused that he's not sure whether it's an electrician or a plumber who should be running conduit.
 
You and I both know that the bulk of misclassification issues than can get to a dispute revolve around employers wanting to use a lower wage "laborer" classification when another pay class (which, Oops! - happens to pay more) is more appropriate.

Yes, Yes, it can be intimidating and on rare occasion,
I have seen honest subcontractors be absolutely clueless about the resources that were available to them through the prime, agency contracting officer, and local Wage Hour office regarding how to make those determinations and keep the records.  In 99% of the cases, there are answers and information available to the subs that will cut that time and perceived administrative burden.

Clearly, how the process works and getting info promptly is to everyone's advantage, and will relieve the administrative burden.  The bureaucracy HAS to improve in this area. If only because the perception of administrative burden has lessened the quantity of bids on any given project.

But, I stand by my original assertion that many legit prime and subcontractors can and do get D-B compliance accomplished with minimal extra work. 

We see the real "red herring"s when a contractor's refusal to make payrolls, (ie. ees work weeks and weeks for free) or payment of piecerates to crews (ie. I'll give $500 for the roof) is blamed on the "confusion" over classifying ees work.

P.S. You know that the answer to the laborer who does wiring is to break down the time right? - ie. 2 hrs wiring (electrician), 6 hrs labor.

Leave a comment

Advertisement
Please disable your adblocker!
Ads are how we pay the bills!

Subscribe

The Coffee House
TPMCafe's regulars

House Brew
From Your Cafe Editor

Special Guests
Big names and big brains

Special Features
Pressing topics and trends

Table for One
An expert's week-long talk.

All Reader Posts
TPM readers discuss.

Recent Reader Posts

All Reader Posts »



Book Club Calendar


Coming Soon



Nov. 30-Dec. 4



January 12-16



« Book Club ArchiveFull calendar »

Book Club Archive



Masthead

Editor-in-Chief
Josh Marshall

Site Editor
Lila Shapiro

Intern
Kyle Krahel-Frolander



Subscribe to TPMCafe's feed.
Subscribe to TPMCafe's reader blog feed.

Advertise Liberally
Share
Close Social Web Email

"To" Email Address

Your Name

Your Email Address