Software developer at a big library, cyclist, photographer, hiker, reader. Email: chris@improbable.org
24173 stories
·
216 followers

Why I'm Resigning From The Intercept - Ken Klippenstein

1 Share

I resigned from The Intercept today in order to pursue a new kind of journalism here on Substack, one more hard-hitting than what’s possible in the corporate world. The Intercept has been taken over by suits who have abandoned its founding mission of fearless and adversarial journalism, and I can’t continue in an environment where fear of funders is more important than journalism itself. On a brighter note, though, I’m leaving DC to move back to Wisconsin, excited to embrace independence both in my journalism and from the Washington bubble.

The reason so much of the news media sucks is they aren’t writing for you. They’re writing for their sources in Washington, for the industries they cover, for rich people, and for fancy awards committees. Just take a look at the ads they run: for investment banks, defense contractors, oil companies. Unless you’re in the market for any of these products, they aren’t writing for you.

I want to write for you. 

I want to be an unabashed partisan for the vast majority of Americans who despise the people who run the country, putting my finger in the eye of the elites frog marching us through their managed decline of the American standard of living. 

The most effective way I can do this is through journalism that arms you with a better understanding of subjects elites don’t like the rabble meddling with, chief among them the national security state. But I also want to be able to write without fear of billionaires, wealth or Wall Street. And when I say journalism, I’m not talking about “democracy dying in darkness” or “holding power to account” or any of that sanctimonious bullshit. I’m talking about being a thorn in the side of our self-appointed betters. 

At its most basic level, I want to help you understand what’s actually going on in the world. But not how the mainstream media does it, with their sanctioned leakers and their endless handjobs of retired generals and the other celebrity architects of our decline. Whenever something important happens, take for example Iran’s drone and missile attack on Israel, you can find dozens of articles on it, but they’re all variations on the same story the White House disseminates. I’m not interested in Washington’s spin or the view from someone’s desk. (Who do you think is more familiar with the conditions of Amazon warehouses: Jeff Bezos or a rank-and-file employee?)

My best stories will be your story: how they want your acquiescence for the war party, how they want your money to pay for their follies, how they want to limit the information you receive, how they want to bee up your ass controlling every aspect of your life. 

I want to take it to the billionaires, expose the fraud and avarice of the national security state and the corporation, and explore a concept I have of a Journalism 2.0. I am not going to bother clearing my reporting with so-called “experts” at think tanks bankrolled by head-chopper authoritarian regimes like Saudi Arabia, by military contractors, or by billionaires. And I’m certainly not going to hide behind weasel words like experts say, journalism’s device for pretending like they’re being objective. No weird, disembodied voice of God narrating everything in the omniscient third person, either. For the first time in my career, I’ll be free to report without the straitjacket that is the dated norms of journalism 1.0. And I’ll be accurate, but I’m not going to pretend to be fair. If you want balance — the charade where journalism pretends to be interested in Both Sides and delivers the reasonable — turn on NPR. 

Here’s why you should read me here: I’m going after the rich, who hide their insatiable greed behind well-publicized, tax-deductible philanthropy. I’m going after the bureaucrats, who blather about public service and sacred oaths and then run for the corporate revolving door to cash in while manipulating the federal agencies they once ran. I’m going after the retired generals on TV and on the lecture circuit holding forth on every war despite their failure to ever win one. I’m going after anyone described as a “luminary,” the squeaky clean, feel-good types who spout platitudes while harboring deep, dark secrets. I’m going after the journalistic priesthood, like Judith Miller’s editor for her bogus Iraq WMD stories, whose punishment was being made editor-in-chief of ProPublica (salary: $480,000) and chair of the Pulitzer Prize Board. And any public figure confused about what young people are so mad about or how people could be dissatisfied with an economy where most Americans can’t afford to own a home.

My decision to go independent was a long time coming, but the final, precipitating event was the corporatization of The Intercept over the past few months.

In my time at The Intercept, I’ve watched the newsroom increasingly become dominated by management and bureaucrats whose numbers continue to swell as the number of people who actually produce news dwindles. While the Intercept now has one poor copy editor for the entire website, it employs two staff attorneys, as well as a legal fellow, a chief strategy officer, a chief digital officer, a business coordinator, a senior director of development and an associate director of development, a product manager, a senior director of operations, a chief of staff, and a chief operating officer. And for the first time in The Intercept’s history, as of Monday, the new editor-in-chief now answers to the CEO.

The company’s org chart, pictured below, provides a sense of how top-heavy it has become with business hires (basically the entire left half).

This orgy of management largesse has coincided with layoffs of the editor-in-chief, managing editor, national security editor, copy editor, photo editor, multiple senior editors, social media editor, as well as writers and reporters. There are passionate editors and writers left who still want to do news, like Ryan Grim and Ali Gharib, but they are toiling under the impossible odds of the new management regime.

After the initial layoffs in February realizing there wasn’t the bandwidth or the internal advocacy to get my stories through, I threatened to leave for somewhere interested in doing journalism. They hired an interim editor Bill Arkin, one I insisted on. Bill is a legendary national security analyst and reporter with a career going back to the Cold War, a splinter in the eye of every administration since Reagan. Not one for self-promotion, many don’t realize how many major news stories he’s been behind: first to report on the Bush administration’s top secret plan to invade Iraq, first person to reveal where all the nuclear weapons were, first to write about the above-top secret continuity of government system, first to report on the ground about civilian casualties and cluster bombs, first to reveal countless other secret programs and instances of government spying. Bill has worked at NBC News, The New York Times, The Washington Post, the LA Times, but as his frequent job moves attest, he’s not a corporate guy.

Bill laid out his philosophy: stop paying attention to the meltdown of The Intercept and report on American-centric national security topics. Help your readers understand a hidden world. Focus on the mal-practitioners, he insisted. And take no prisoners. 

We hit the ground running. My stories under Bill were a wild success for The Intercept, with one of the first — about the FBI’s attempts to root out so-called “extremist” gamers online — quickly becoming the site’s second most viewed article this year. 

But then we did a story on the billionaire founder of Amazon, Jeff Bezos.

It was a straightforward article detailing Bezos’s $50 million charity grant to the retired Admiral William McRaven (whose wife sits on the board of a charity linked to Bezos), calling the contribution a “racket.” The story seemed like vintage Intercept fare. One of our founders, Jeremy Scahill, made an excellent Academy Award nominated documentary about McRaven. My story was essentially a factual overview of McRaven’s own considerable wealth, and it noted the irony that the $100 million grant Bezos gave to McRaven and celebrity Eva Longoria was the exact same amount of money that the Bezos-owned Washington Post lost this past year. The story practically wrote itself.

Enter the Intercept’s general counsel David Bralow, who said he had problems with the article. He didn’t have legal concerns. Bralow instead thought it inopportune, saying that attacking Bezos might not sit well with the Intercept’s own billionaire donor, Pierre Omidyar, especially at a time when he was keeping the organization afloat.

“I confess on a first read that it gives me pause, particularly because the article waits until the back half to say that McRaven actually donated this money to other charities,” Bralow emailed Bill. “And how is that a racket?”

Bralow called the story “naive,” questioning our questioning of Bezos’ commitment to journalism. “A business, just like ours, has the obligation to remain sustainable,” he continued. “That it [the Washington Post] has net operating loss and its owner wants to make charitable contributions seems very different. Even more to the point, that Bezos does not want to subsidize the media anymore seems like we are ignoring our own story.” 

Email sent from The Intercept's General Counsel, David Bralow, to my editor
Download

Bill updated the draft — which already said in the subheadline that it was a charity grant — to further stress that Bezos’ $100 million gift was for charity. Bill then sent it back to Bralow.

What happened next, Bralow did not commit to writing, instead calling Bill. 

During the call, Bill told me immediately after, Bralow said that Annie Chabel, the CEO, had concerns about how the story might come off to the Intercept’s donors. Bill said that that might be unfortunate but wouldn’t influence his decision to publish, and that if Bralow had any legal concerns — as opposed to editorial — he would be happy to address them.

After a heated back and forth, Bralow declared: “I’m killing the story.”

Bill replied that he would resign, prompting Bralow to back off (I had said I would leave if Bill didn’t edit me, the reason Bralow retreated.)

“I don’t see the point of the story,” Bralow then complained before Bill told him to fuck off (literally, lol). We published. 

The Washington Post journalists who privately thanked us for doing the story seemed to understand the point just fine — as did the people who read it, making it one of the top performing articles that month.

Subsequent stories that Bill edited were repeatedly held up. Chabel and Bralow also saw to it that Bill was not provided access to the company Slack or invited to staff meetings or even be publicly acknowledged, siloing him off. Bill toiled on, editing me and my colleague Dan Boguslaw. Under his tutelage, we went on to produce most of the top performing stories on the site.

Bralow, who resembles a Catholic priest caricatured in one of Martin Luther’s tracts, living well off the generosity of his modest parishioners, is the personification of what The Intercept has become. With his bloated salary (over $300,000, per the most recent nonprofit filing), bureaucrats like him who prevent journalism is what your money is paying for if you contribute to The Intercept these days.

It wasn’t just my stories getting held up. Dan obtained a leaked copy of the membership list for the secretive Bohemian Grove, a private gentlemen’s club that counts business tycoons and former top officials like the late Henry Kissinger among its members. Bill worked with Dan to recreate the membership list as a new document to obscure the source, but the Intercept would have none of it.

Enter Nikita Mazurov, the company’s PhD in “Cultural Studies” who for some reason serves as the manager of digital security. Though Dan had obtained the document over a year ago from a source who was confident it was safe to use, Mazurov acted as if it was the CIA’s family jewels, going on and on about how the protection of the source demanded more work before we could publish.

In a subsequent call that included Bralow, Mazurov peppered Dan and Bill with bizarre questions, like: ‘What if there exists another list, compiled the day before, and then another, compiled the day after, and those list are each different, and the Bohemian Grove went through all three lists to pinpoint the exact date of your list and then went through a list of all people who had access?’ And ‘what if there was CCTV footage in the office where the list was stored, footage that would reveal the person who accessed it and leaked it?’

“This isn’t the CIA!” Bill yelled, calling Mazurov a fucking idiot. 

“That’s an HR violation!” Mazurov shrieked.

With Dan’s agreement, Bill abandoned the story. (Dan said he was so happy to see an editor stand up to the officious bureaucrats that the pleasure was greater than the story’s publication ever would have been.) 

Such an incident happened once again when a source provided me with diplomatic cables revealing the Biden administration’s private attempts to pressure other countries to vote against a Palestinian statehood resolution at the UN. Having received the documents just days before the UN vote, I urgently needed to get the story out in time for it to inform public debate. But again, The Intercept had “legal concerns.” I pushed back, stressing the story’s time sensitive nature, that the documents were unclassified and the source confident they were safe to publish. 

But Mazurov didn’t see it that way. He emailed Bill a list of over 20 separate “source protection concerns” he believed needed to be answered before publication. This kind of security theater had emerged in the wake of the criminal prosecution of two Intercept sources; but they had leaked classified information, and this was unclassified. With the UN vote drawing near, it seemed to me that The Intercept’s solution to its past source protection fiascos was not to publish journalism.

Email from Nikita Mazurov
Download
Email from The Intercept's digital security manager, Nikita Mazurov, to my editor.
Download

Bill wrote to Bralow that Mazurov’s list was surely some kind of “joke,” and he forced publication the day before the vote. 

Predictably, the story touched off a firestorm of outrage over the Biden administration’s public support for a two-state solution while secretly backchanneling to kill it.

There were other examples, and I got a window into how the corporation — now in the guise of a billionaire anchored non-profit — tended to itself and its own survival, rather than to journalism. 

On Friday, Bill was informed that he was being let go.

I decided there and then that I had to leave. At a time when Israel’s war in Gaza had spread to the rest of the region, drawing in the Iranian superpower, my sources in the U.S. government were leaking more than ever to alert the public to looming catastrophe. I could not in good conscience remain at an outlet that can’t publish these disclosures, nor continue to live off of donor money that is not going toward its stated purpose, journalism, let alone “fearless” journalism that the Intercept was founded around.

The extent of the dysfunction at The Intercept is not publicly known in part because, for all management’s problems, they are very good at one thing: structuring hush money payments. Multiple outgoing Intercept staffers have been offered severance packages in exchange for signing non-disclosure agreements. Following Bill’s firing, I was also offered a “retention” agreement. I did not dignify the offer with a response. I don’t begrudge my colleagues taking the money — people need to pay rent — but I can no longer stay.

My decision to resign from The Intercept is something of a leap of faith. Unlike many reporters I’ve run into, I don’t get financial help from mommy and daddy, so my runway is limited. But what I do have is an abiding faith in the generosity of ordinary people.

If you’ve received this letter as an email from me today, that means you’ve already subscribed to — and are currently on — my email list. My goal is to make everything I write available to all subscribers without a paywall. But I can only do that if I build a list of some 5,000 paid subscribers (At the time of this writing, I’m at 450, so we’re almost 10% of the way there.) That will generate enough income to pay me; to pay Bill, who will be the site’s editor; to hire my attorney and friend Beth Bourdon to help with FOIA requests; and to find administrative and research assistants, as well as some young journalists and freelancers to work alongside. If you want to support me and my work, please upgrade to a paid subscription or make a donation.

I’ve also created a GoFundMe account if you prefer to contribute there.

Join the fight and let’s take on the national security state and the monied elite. 

— Edited by William M. Arkin

Share

© Klip News, LLC

Read the whole story
Share this story
Delete

How I search in 2024

1 Share
We are now in a very weird liminal space in information retrieval for consumers, particularly those attuned to trends in search and working on the bleeding edge of LLMs. On the one hand, we have the fall of old companies. Broadcast-based centralized social media, which steadily served as a newsfeed and realtime search for a small, vocal minority, is basically dead, or on its last legs. Search, namely Google, is basically a useless pile of ads and SEO gamification at this point and a stopping point for Reddit results.
Read the whole story
Share this story
Delete

Apple poaches AI experts from Google, creates secretive European AI lab | Ars Technica

1 Share

Complete digital access to quality FT journalism with expert analysis from industry leaders. Pay a year upfront and save 20%.

  • Everything in Standard Digital
  • Global news & analysis
  • Expert opinion
  • Special features
  • FirstFT newsletter
  • Videos & Podcasts
  • FT App on Android & iOS
  • FT Edit app
  • 10 gift articles per month
  • Exclusive FT analysis
  • Premium newsletters
  • FT Digital Edition
  • 10 additional gift articles per month
  • Weekday Print Edition
  • FT Weekend
  • FT Digital Edition
  • Global news & analysis
  • Expert opinion
  • Special features
  • Exclusive FT analysis
  • FT Digital Edition
  • Global news & analysis
  • Expert opinion
  • Special features
  • Exclusive FT analysis
  • Global news & analysis
  • Expert opinion
  • Special features
  • FirstFT newsletter
  • Videos & Podcasts
  • FT App on Android & iOS
  • FT Edit app
  • 10 gift articles per month
  • Everything in Standard Digital
  • Exclusive FT analysis
  • Premium newsletters
  • FT Digital Edition
  • 10 additional gift articles per month
  • Everything in Print
  • Weekday Print Edition
  • FT Weekend
  • FT Digital Edition
  • Global news & analysis
  • Expert opinion
  • Special features
  • Exclusive FT analysis
  • Plus
  • Everything in Premium Digital
  • Everything in Standard Digital
  • Global news & analysis
  • Expert opinion
  • Special features
  • FirstFT newsletter
  • Videos & Podcasts
  • FT App on Android & iOS
  • FT Edit app
  • 10 gift articles per month
  • Exclusive FT analysis
  • Premium newsletters
  • FT Digital Edition
  • 10 additional gift articles per month
  • FT Weekend Print delivery
  • Plus
  • Everything in Standard Digital
  • FT Weekend Print delivery
  • Plus
  • Everything in Premium Digital
Read the whole story
Share this story
Delete

Tesla to lay off everyone working on Superchargers, new vehicles | Ars Technica

1 Comment

There's more chaos at Tesla this week. The Information reports that last night, the company's erratic CEO Elon Musk emailed workers with the news that he has dismissed a key pair of executives—one responsible for the Supercharger network, and the other head of new vehicle development.

The electric car maker posted its quarterly results last week and they paint a poor picture, with shrinking sales and plummeting profit margins. While Tesla once had a strong first-mover advantage and benefited from Musk's marketing savvy, the company has frequently ignored the many hard-learned lessons of the auto industry.

Customers not turned off by Musk's antics instead are losing interest with a product line up of two EVs that are ancient in car years (the Models S and X) and two EVs that are merely old (the Models 3 and Y). The Models 3 and Y are also the only two vehicles that Tesla sells in volume. Any other automaker would have a second-generation Model 3 ready to go either this year or next, but at Tesla the product pipeline is empty.

And yet, Tesla is not just laying off Daniel Ho, director of vehicle programs and new product introduction, but also his entire team.

"Hard-core about headcount"

Even Tesla's harshest critics must concede that the company's Supercharger network is its star asset. Tesla has more fast chargers in operation than anyone else, and this year has opened them up to other automakers, which are adopting the J3400 plug standard.

All of which makes the decision to get rid of senior director of EV charging Rebecca Tinucci—along with her entire team—a bit of a head-scratcher. If I were the driver of a non-Tesla EV expecting to get access to Superchargers this year, I'd probably expect this to result in some friction. Musk told workers that Tesla "will continue to build out some new Supercharger locations, where critical, and finish those currently under construction."

Many Tesla fans had been holding out hope that Musk would debut a cheap Model 2 EV in recent weeks. Instead, the tycoon promised that robotaxis would save the business, even as both of its partially automated driver assistance systems face recalls and investigations here in the US and in China.

Delivering on that goal is more than just a technical challenge, and will require the co-operation and approval of state and federal authorities. But Musk is also dissolving the company's public policy team in this latest cull.

"Hopefully these actions are making it clear that we need to be absolutely hard-core about headcount and cost reduction. While some on exec staff are taking this seriously, most are not yet doing so," Musk wrote to employees. Musk also told staff that he would ask for the resignation of any executive "who retains more than three people who don't obviously pass the excellent, necessary and trustworthy test."

Earlier this month Tesla engaged in another round of layoffs that decimated the company and also parted ways with longtime executive Drew Baglino, who was responsible for Tesla's battery development.

Read the whole story
Share this story
Delete
1 public comment
acdha
3 hours ago
reply
The brainworms are amazing!
Washington, DC
fxer
1 minute ago
Huffing his own covfefe

My approach to HTML web components

1 Share

I’ve been deep-diving into HTML web components over the past few weeks. I decided to refactor the JavaScript on The Session to use custom elements wherever it made sense.

I really enjoyed doing this, even though the end result for users is exactly the same as before. This was one of those refactors that was for me, and also for future me. The front-end codebase looks a lot more understandable and therefore maintainable.

Most of the JavaScript on The Session is good ol’ DOM scripting. Listen for events; when an event happens, make some update to some element. It’s the kind of stuff we might have used jQuery for in the past.

Chris invoked Betteridge’s law of headlines recently by asking Will Web Components replace React and Vue? I agree with his assessment. The reactivity you get with full-on frameworks isn’t something that web components offer. But I do think web components can replace jQuery and other approaches to scripting the DOM.

I’ve written about my preferred way to do DOM scripting: element.target.closest. One of the advantages to that approach is that even if the DOM gets updated—perhaps via Ajax—the event listening will still work.

Well, this is exactly the kind of thing that custom elements take care of for you. The connectedCallback method gets fired whenever an instance of the custom element is added to the document, regardless of whether that’s in the initial page load or later in an Ajax update.

So my client-side scripting style has updated over time:

  1. Adding event handlers directly to elements.
  2. Adding event handlers to the document and using event.target.closest.
  3. Wrapping elements in a web component that handles the event listening.

None of these progressions were particularly ground-breaking or allowed me to do anything I couldn’t do previously. But each progression improved the resilience and maintainability of my code.

Like Chris, I’m using web components to progressively enhance what’s already in the markup. In fact, looking at the code that Chris is sharing, I think we may be writing some very similar web components!

A few patterns have emerged for me…

Naming custom elements

Naming things is famously hard. Every time you make a new custom element you have to give it a name that includes a hyphen. I settled on the convention of using the first part of the name to echo the element being enhanced.

If I’m adding an enhancement to a button element, I’ll wrap it in a custom element that starts with button-. I’ve now got custom elements like button-geolocate, button-confirm, button-clipboard and so on.

Likewise if the custom element is enhancing a link, it will begin with a-. If it’s enhancing a form, it will begin with form-.

The name of the custom element tells me how it’s expected to be used. If I find myself wrapping a div with button-geolocate I shouldn’t be surprised when it doesn’t work.

Naming attributes

You can use any attributes you want on a web component. You made up the name of the custom element and you can make up the names of the attributes too.

I’m a little nervous about this. What if HTML ends up with a new global attribute in the future that clashes with something I’ve invented? It’s unlikely but it still makes me wary.

So I use data- attributes. I’ve already got a hyphen in the name of my custom element, so it makes sense to have hyphens in my attributes too. And by using data- attributes, the browser gives me automatic reflection of the value in the dataset property.

Instead of getting a value with this.getAttribute('maximum') I get to use this.dataset.maximum. Nice and neat.

The single responsibility principle

My favourite web components aren’t all-singing, all-dancing powerhouses. Rather they do one thing, often a very simple thing.

Here are some examples:

  • Jason’s aria-collapsable for toggling the display of one element when you click on another.
  • David’s play-button for adding a play button to an audio or video element.
  • Chris’s ajax-form for sending a form via Ajax instead of a full page refresh.
  • Jim’s user-avatar for adding a tooltip to an image.
  • Zach’s table-saw for making tables responsive.

All of those are HTML web components in that they extend your existing markup rather than JavaScript web components that are used to replace HTML. All of those are also unambitious by design. They each do one thing and one thing only.

But what if my web component needs to do two things?

I make two web components.

The beauty of custom elements is that they can be used just like regular HTML elements. And the beauty of HTML is that it’s composable.

What if you’ve got some text that you want to be a level-three heading and also a link? You don’t bemoan the lack of an element that does both things. You wrap an a element in an h3 element.

The same goes for custom elements. If I find myself adding multiple behaviours to a single custom element, I stop and ask myself if this should be multiple custom elements instead.

Take some of those button- elements I mentioned earlier. One of them copies text to the clipboard, button-clipboard. Another throws up a confirmation dialog to complete an action, button-confirm. Suppose I want users to confirm when they’re copying something to their clipboard (not a realistic example, I admit). I don’t have to create a new hybrid web component. Instead I wrap the button in the two existing custom elements.

Rather than having a few powerful web components, I like having lots of simple web components. The power comes with how they’re combined. Like Unix pipes. And it has the added benefit of stopping my code getting too complex and hard to understand.

Communicating across components

Okay, so I’ve broken all of my behavioural enhancements down into single-responsibility web components. But what if one web component needs to have awareness of something that happens in another web component?

Here’s an example from The Session: the results page when you search for sessions in London.

There’s a map. That’s one web component. There’s a list of locations. That’s another web component. There are links for traversing backwards and forwards through the locations via Ajax. Those links are in web components too.

I want the map to update when the list of locations changes. Where should that logic live? How do I get the list of locations to communicate with the map?

Events!

When a list of locations is added to the document, it emits a custom event that bubbles all the way up. In fact, that’s all this component does.

You can call the event anything you want. It could be a newLocations event. That event is dispatched in the connectedCallback of the component.

Meanwhile in the map component, an event listener listens for any newLocations events on the document. When that event handler is triggered, the map updates.

The web component that lists locations has no idea that there’s a map on the same page. It doesn’t need to. It just needs to dispatch its event, no questions asked.

There’s nothing specific to web components here. Event-driven programming is a tried and tested approach. It’s just a little easier to do thanks to the connectedCallback method.

I’m documenting all this here as a snapshot of my current thinking on HTML web components when it comes to:

  • naming custom elements,
  • naming attributes,
  • the single responsibility principle, and
  • communicating across components.

I may well end up changing my approach again in the future. For now though, these ideas are serving me well.

Read the whole story
Share this story
Delete

With Few Workplace Safety Protections, Latino Worker Deaths Are Surging - In These Times

1 Share

A burst of shouts cascades as three men plunge downward. Other workers reach for them as the scaffold plummets.

But no one can grab hold of them.

Thinking he can still save them, a middle-aged construction worker scampers to aid the three men, one a long-time friend, he had helped get hired on the site. 

I saw everything,” he says and then repeats himself. I saw everything. In a video you can see me removing planks from them because I thought they were alive, but they were dead.”

Jose Canaca, 26, Gilberto Monico Fernández, 54, and Jesus Chuy” Olivares, 43, had been putting up an outer brick wall for a 17-story apartment building in a popular neighborhood in Charlotte, N.C., when they fell from the 10th floor. They hit a patio rooftop on the fourth floor — a 70-foot drop. 

Months after the fatal construction accident in January 2023, the tragedy haunts him. He quit the risky construction work he’d done for about 15 years and has been taking lower-paying jobs.

I don’t wish this on anyone, what happened there,” says Diego Sanchez, the construction worker who tried to rescue the three men. Sanchez, who came to the United States from Honduras, asked to use a pseudonym because he fears retaliation from immigration authorities. 

The deaths of Canaca, Fernández and Olivares added to the increasing numbers of Latino workers killed on the job, a death count that has grown steadily year after year. Latino workers today have the highest workplace fatality rate: The number of on-the-job deaths has declined over time for white people, and slightly increased for Black people over the past few years, but fatalities for Latino workers continue to rise sharply.

While workplace safety is an issue that affects everyone, a disproportionate share of those who will be mourned this Workers Memorial Day — observed on April 28 to honor people injured or killed on the job — were Latino. 

There were 1,248 Latino workers killed on the job in 2022, reflecting a 57% increase over the previous decade, according to the U.S. Bureau of Labor Statistics.

About two-thirds of those Latino workers killed on the job in 2022 were undocumented, and as the fatalities continue to rise, many are trying to understand what drives this death spiral. 

Latino workers predominate in low-wage, risky jobs: in construction, meat processing, landscaping, farmwork and warehousing. They can die in many different ways, including collapsed ditches, falling off roofs, ladders and scaffolds, and because of machines that catch and mangle their bodies. Excessive heat can be overwhelming, especially as water and rest breaks on construction sites or farm fields are often policed or prohibited.

After investigating the scaffold collapse, the North Carolina Department of Labor’s Occupational Safety and Health Division fined two companies involved. 

Friends Masonry Construction was fined for failing to inspect the equipment before the work, for not repairing or replacing damaged equipment and using equipment that was heavily rusted and deteriorated. The company was initially fined $43,506, but that was reduced to $29,004 (for an unspecified reason in the report).

Felipe Estrada Calzada, a company official, declined to discuss the incident.

Workers on a Miami Beach, Fla., construction site upgrading underground utilities infrastructure Photo by Jeffrey Greenberg/Universal Images Group via Getty Images

Old North State Masonry was fined for not inspecting the equipment, failing to re-test older equipment and relying on a scaffold that was incapable of bearing sufficient weight. It was fined $87,012. They did not respond to requests for comment.

When we come to this country, we want to make money, so we get into sketchy situations,” says Sanchez, who worked for about 15 years in the South since coming to the United States. He has worked at places where they asked for papers and where they didn’t. And that has meant taking jobs where he can slip by. When we try to work with [white] Americans, there, they ask for a good Social Security card, and if we don’t have one, we die of hunger,” he says.

So, too, some are teens working in dangerous jobs, like Duvan Tomas Perez, a 16-year-old from a rural Guatemalan village, who died last July, while working on the regular cleaning crew in a Mar-Jac Poultry plant in Hattiesburg, Miss. U.S. law bars youths under 18 years old from working in hazardous workplaces. 

The teen was reportedly using the Social Security information of 32-year-old. Attorney Jim Reeves of Biloxi, Miss., who has filed a lawsuit against Mar-Jac and Ōnin Staffing on behalf of the youth’s family, finds it hard to believe that the company accepted the fraudulent information. My client looked like a 12-year-old,” he says.

Mar-Jac officials did not respond to requests for comment, but the company issued a statement in July 2023, explaining that it uses staffing companies” to hire workers due to an unprecedentedly tight labor market” and relies on them to verify that their hiring is legal.

Adding that the boy’s age and identity were misrepresented on the paperwork,” the company explained in a statement that we are devastated at the loss of life and deeply regret that an underage individual was hired without our knowledge.”

Ōnin Staffing did not respond to requests for comment.

Workers pack bacon in a Chicago meatpacking plant in 1919. Photo by Corbis via Getty Images

Pointing out that the latest incident was their second involvement with the Mississippi plant in recent years, OSHA officials in January fined Mar-Jac Poultry $212,646, and cited 14 serious safety violations at the Hattiesburg facility. It also pointed to a 2021 incident at the plant when a worker was killed in an accident and the company was fined. It was the same violation in each of these cases,” says Reeves.

The company has had other worker safety and hiring problems with the government.

A couple were convicted by a federal jury in Alabama in 2021 for illegally transporting undocumented migrants, including minors, to a Mar-Jac facility in Alabama. And in 2009, the company was fined $380,000 for not having certain safety procedures or performing compliance audits for several years at a plant in Gainesville, Ga.

The death of Perez, the teen who died while working for Mar-Jac, reflects a larger problem.

As a New York Times investigation in February 2023 showed, many migrant youths are snarled in such life-threatening jobs. At about the same time, the U.S. Department of Labor said it was concerned about an increase in child labor and pointed to unaccompanied migrant youths from Latin America. In July 2023, the agency followed up, saying it had concluded 765 child labor cases involving 4,474 children.

At the peak of the Covid crisis three years ago, the United Food and Commercial Workers union complained that thousands of meatpacking workers, most of whom were Latino, were falling sick at facilities because they lacked protections against the virus.

From his previous work with day laborers in Charlotte, Isael Mejia, an Iron Workers union organizer in Charlotte, N.C., recalls workers describing their job safety as a cruel joke.

You are getting picked up at a Home Depot. You have no experience in roofing, and then you fall and then what’s the easiest thing [for whoever hired you] to do, is to leave you there,” he says.

Only one-fourth of the injuries suffered by Latinos working on small construction jobs are regularly reported, according to a 2011 study based on long-term statistics.

Finding solutions is made difficult by the fact that government figures apparently do not capture all the workplace dangers Latino workers face. Only one-fourth of the injuries suffered by Latinos working on small construction jobs are regularly reported, according to a 2011 study based on long-term statistics.

Much of the surge in deaths and injuries for Latino workers’ has taken place in the construction industry. More than 34% of construction workers were Hispanic in 2022, up from 9% in 1995

Hispanics are now more than one-third of the construction workforce and an even bigger share of workers in high-risk trades like roofers and laborers,” says Chris Trahan Cain, director of the Center for Construction Research and Training (CPWR). Latino workers are more likely to work for small companies which have higher fatality rates, he adds.

The CPWR is a Washington D.C.-area nonprofit that focuses on ways to reduce workplace injuries and fatalities. There were more deaths in construction in 2022 than in any other industry, emphasizing the importance of such work.

Deaths among Latino construction workers jumped from 222 in 2012 to 408 in 2022, accounting for more than 32% of all workplace deaths among Latino people in the nation.

In 2017, the fatality rate for Latino construction workers who died in falls was 50% higher than for others. 

Just as Latino workers disproportionately die on construction jobs, they suffer from high injury rates. 

The fatality rate for Latino construction workers was 41.6% higher than others in 2020, and the fatality rate for Latino construction workers increased 46.5% from 2018 to 2020 (8.6 to 12.6), while the rate decreased 6.3% for non-Hispanic workers. 

Driving these numbers, say safety experts, researchers and the workers themselves, are a slew of forces.

Overall, Latino workers tend to be younger and less experienced, lack training in the job, earn lower wages and work for small outfits, researchers say. They often take jobs in sectors that others avoid. For example, Latino workers make up 55.5% of the nation’s roofers, which had the highest fatality rate in the construction industry in 2020. And in 2022, 54% of roofers’ deaths were Latino. 

Texas is one of the most lethal states for Latino workers and recorded 269 deaths in 2022, up from 211 in 2016. Latino people make up 40% of the state’s population, but they accounted for 47% of workers killed on the job in 2022.

These facts should not be surprising since Latino workers have long suffered on-the-job setbacks in Texas, according to news reports, experts and worker advocacy groups.

Texas does not require private employers to have workers’ compensation insurance, and many Latino workers lack health insurance, worker advocates say. So, too, conservative-led politics in Texas have resulted in legislative efforts that often flaunt worker safety issues.

And the latest example of ignoring pleas to protect workers is Gov. Greg Abbott’s signing of H.B. 2127 last June barring communities from setting their own heat regulations, an effort that included wiping out water breaks for construction workers in Dallas and Austin.

Mexican laborers harvest yellow onions in Rio Grande City, Texas. Photo by Robert Nickelsberg/Getty Images

Tagged as the Death Star” law by unions, human rights and worker advocacy groups, the bill is currently snarled in a challenge by the state in the Texas courts. Meanwhile, the law has been implemented.

The Death Star law is the largest transfer of power away from working people and into the hands of a few extreme state lawmakers,” said an official from the Texas AFL-CIO in August. Unions account for 4.5% of Texas’ workers.

Gov. Abbott’s office did not reply to requests for comments. But insight on the law’s support comes from the Texas Public Policy Foundation, a politically influential conservative group that strongly promoted its passage.

The fight over HB 2127 isn’t about water breaks, no matter what the media says. It’s about progressive power and preventing the California-zation of Texas’ local governments,” wrote a staff writer for the foundation in July 2023.

It comes as no surprise that the state of Texas continues to be the most dangerous for workers and that Latinos are especially vulnerable to unsafe work environments in hard labor industries such as construction,” says Christine Bolaños, an official with the Worker Defense Project. Her organization is a leading voice for low-wage immigrant workers in Texas.

From heat-related deaths to serious negligence that can lead to equipment malfunctioning and on-the-job accidents and to wage theft and workplace discrimination,” she adds, Latinos have much stacked against them including language barriers, sometimes a lack of proper legal documentation and a familial obligation to continue working in harsh conditions to keep food on the table and a roof over their head.”

Antonia Catalan, a member of The Farmworker Association of Florida Homestead Office, attends a press conference and vigil in Homestead, Florida, on July 19, 2023, in honor of farm worker Efrain Lopez Garcia, 30, who died from heat complications on July 6, 2023. Photo by GIORGIO VIERA/AFP via Getty Images

Protecting Latino workers has been a major goal for the New York Committee for Occupational Safety and Health, an organization of workers, unions, workers advocates and health-and-safety professionals.

But one of the obstacles to saving Latino workers’ lives, says its executive director, Charlene Obernauer, is that workers do not know their rights. Or they’re warned by employers who tell them, If you say anything we are going to call ICE [Immigration and Customs Enforcement],’ she explains.

A major boost for undocumented workers came when the Biden Administration announced in 2023 a process aimed at protecting noncitizen workers who report labor violations from immigration-based retaliation. The effort is called deferred action for labor enforcement because it allows workers to delay deportation and obtain work permits to assert their legal rights.

By and large, workers are not being informed” that this process exists though, says Obernauer.

After the scaffold collapse in Charlotte, labor and human rights groups scrambled to help the families impacted understand their legal options. 

Carol Brooke, an attorney with the North Carolina Justice Center says many workers would not discuss the accident, fearful that their undocumented status would come up, triggering actions against them by immigration officials.

Mejia, the Iron Workers union organizer, says he knows very well the dangers Latino workers face because of his union work, experience helping day laborers in Charlotte and ties to the Latino community.

And often exploitation defines the world that Latino workers tell him about. 

It is a world, he says, where you work tired or injured because you need money, where you often don’t get paid or don’t speak up because you fear the boss will alert immigration officials and where you not only don’t have safety training or supplies, but your bosses don’t seem to care about your safety.

It’s a world, he adds, where some doubt that they will survive.

I talk to so many people, who don’t see a future,” he says. They are like, I’d be lucky if I see another year.’”

Abel Uribe contributed to this article.

Read the whole story
Share this story
Delete
Next Page of Stories