Stories
Slash Boxes
Comments

SoylentNews is people

posted by martyb on Tuesday July 04 2017, @03:32PM   Printer-friendly
from the ever-decreasing-state-of-workplace-safety dept.

The World Socialist Web Site reports

On Thursday [July 29], two workers at an electrical plant near Tampa, Florida were killed horrifically when a tank spilled molten slag onto them. Four others were hospitalized with life-threatening injuries. The plant is operated by Tampa Electric Company (TECO), the Tampa Bay area's largest electrical utility service. The company was purchased exactly one year ago to the day by Canadian energy company Emera Inc.

Christopher Irvin, 40, and Michael McCory, 60, were both killed, while Gary Marine Jr., 32, Antonio Navarrete, 21, Frank Lee Jones, 55, and Armando J. Perez, 56, all sustained life-threatening injuries. Only one of the men was a TECO employee while the other five were employees of Gaffin Industrial Services who were contracted to work at the plant.

[...] A TECO spokesperson reported that at the time of the incident workers were performing routine maintenance on a slag tank--a container which houses coal waste after it has been burned. Slag is a glass-like substance that forms when hot coal mixes with water; the slag tank catches leftover by-product that drips down from a coal-fired furnace into water.

The crystallized slag is still molten hot when it forms, and it was slag spillover that killed and injured the workers in question. An expert compared the gushing slag to "what comes out of a volcano".

Workers were reportedly trying to unplug a hole in the slag tank when the material spilled out. A spokesperson from TECO stated that slag filled a large part of the floor in the plant, "6 inches deep and 40 feet in diameter".

[...] An OSHA spokesperson stated in response to the incident, "It's the employer's responsibility to provide a safe and healthful workplace." Apparently, OSHA was already investigating a chemical exposure that happened at the same plant on May 24. This incident involved the release of anhydrous ammonia that caused four employees to be hospitalized.

TECO has a long history of similar incidents.

[...] [A statement from the International Brotherhood of Electrical Workers Local 108] notes that the incident was entirely avoidable. "It's time to listen to the employees", it reads. "It's time to stop using contractors to do 'routine maintenance' when the safety of this maintenance has been questioned by employees. It's time to stop putting profit before safety. It's time to truly put safety first."


Original Submission

 
This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 3, Funny) by butthurt on Tuesday July 04 2017, @04:22PM (1 child)

    by butthurt (6141) on Tuesday July 04 2017, @04:22PM (#534822) Journal

    > TECO has a long history of similar incidents.

    [...] the Real Programmer wants a "you asked for it, you got it" text editor-- complicated, cryptic, powerful, unforgiving, dangerous. TECO, to be precise.

    It has been observed that a TECO command sequence more closely resembles transmission line noise than readable text. One of the more entertaining games to play with TECO is to type your name in as a command line and try to guess what it does. Just about any possible typing error while talking with TECO will probably destroy your program, or even worse-- introduce subtle and mysterious bugs in a once working subroutine.

    -- http://www.pbm.com/~lindahl/real.programmers.html [pbm.com]

    Starting Score:    1  point
    Moderation   +1  
       Funny=1, Total=1
    Extra 'Funny' Modifier   0  
    Karma-Bonus Modifier   +1  

    Total Score:   3  
  • (Score: 2) by vux984 on Tuesday July 04 2017, @11:06PM

    by vux984 (5045) on Tuesday July 04 2017, @11:06PM (#534964)

    Thanks for that; I'd never heard of nor used the TECO editor... lol... just wow... from wikipedia.

    Highlights for me:

    "TECO does not really have syntax; each character in a program is an imperative command, dispatched to its corresponding routine. That routine may read further characters from the program stream (giving the effect of string arguments), change the position of the "program counter" (giving the effect of control structures), or push values onto a value stack (giving the effect of nested parentheses). But there is nothing to prevent operations like jumping into the middle of a comment, since there is no syntax and no parsing."

    and

    "TECO was a direct ancestor of Emacs, which was originally implemented in TECO macros."

    The full essay you linked (and excerpted from) was also pretty awesome.